CX-0001 Participant Agent Registration v1.2.1
1. Introduction
This standard solves a requirement towards GAIA-X compliance. It is necessary that each Participant Agent must
provide a Self Description (SD) of type ServiceOffering. This requires a registration of a Participant Agent
at the Core Service Provider B.
1.1 Audience & Scope
This section is non-normative
This standard is relevant for the following roles:
- Data Provider / Consumer
- Core Service Provider B
- Enablement Service Provider
- Application Service Provider
1.2 Conformance
As well as sections marked as non-normative, all authoring guidelines, diagrams, examples, and notes in this specification are non-normative. Everything else in this specification is normative.
The key words MAY, MUST, MUST NOT, OPTIONAL, RECOMMENDED, REQUIRED, SHOULD and SHOULD NOT in this document are to be interpreted as described in BCP 14 RFC2119, RFC8174 when, and only when, they appear in all capitals, as shown here.
1.3 Examples
SD for ServiceOffering
{
"selfDescriptionCredential": {
"@context": [
"https://www.w3.org/2018/credentials/v1",
"https://registry.gaia-x.eu/v2206/api/shape"
],
"type": [
"VerifiableCredential",
"ServiceOfferingExperimental"
],
"id": "https://compliance.gaia-x.eu/.well-known/serviceComplianceService.json",
"issuer": "did:web:delta-dao.com",
"issuanceDate": "2022-09-25T23:23:23.235Z",
"credentialSubject": {
"id": "https://compliance.gaia-x.eu/.well-known/serviceComplianceService.json",
"gx-service-offering:providedBy": "https://compliance.gaia-x.eu/.well-known/participant.json",
"gx-service-offering:name": "Gaia-X Lab Compliance Service",
"gx-service-offering:description": "The Compliance Service will validate the shape and content of Self Descriptions. Required fields and consistency rules are defined in the Gaia-X Trust Framework.",
"gx-service-offering:webAddress": "https://compliance.gaia-x.eu/",
"gx-service-offering:termsAndConditions": [
{
"gx-service-offering:url": "https://compliance.gaia-x.eu/terms",
"gx-service-offering:hash": "myrandomhash"
}
],
"gx-service-offering:gdpr": [
{
"gx-service-offering:imprint": "https://gaia-x.eu/imprint/"
},
{
"gx-service-offering:privacyPolicy": "https://gaia-x.eu/privacy-policy/"
}
],
"gx-service-offering:dataProtectionRegime": [
"GDPR2016"
],
"gx-service-offering:dataExport": [
{
"gx-service-offering:requestType": "email",
"gx-service-offering:accessType": "digital",
"gx-service-offering:formatType": "mime/png"
}
],
"gx-service-offering:dependsOn": [
"https://compliance.gaia-x.eu/.well-known/serviceManagedPostgreSQLOVH.json",
"https://compliance.gaia-x.eu/.well-known/serviceManagedK8sOVH.json"
],
"ctxsd": "connector-url"
},
"proof": {
"type": "JsonWebSignature2020",
"created": "2022-09-25T22:36:50.274Z",
"proofPurpose": "assertionMethod",
"verificationMethod": "did:web:compliance.gaia-x.eu",
"jws": "eyJhbGciOiJQUzI1NiIsImI2NCI6ZmFsc2UsImNyaXQiOlsiYjY0Il19..Chbzpl0-4S3sobkKXyBjfx6pm74xLHInOmruHUmO--3HpMcrfKldeJQPYLrUWsEJ1HIjMUqxE6QymZRxXfuRlAJKy2nwyM3S5sFX9YJ8bepBcf6q-nWGTDX-jh8wuyX3lwrG94aJnTBByKPLCovSiZ9BURR3cwiSHczBlM7iP90ee5roHOtI-eoqSBYrYaynTaK5eQaWfT-2OdXYgqVPSRJAK2KD5AqEM8KU7x6nnP6-shgSNBIEC1fAOTfAEUYkcrK8Tn4BTaH02HnO3B90S1MWyAWwBzrnmS915CFY4BiHsp9Tz7pt016c8HB8HE7gqoXndk7DUhzgNE2mRbHuLg"
}
},
"complianceCredential": {
"@context": [
"https://www.w3.org/2018/credentials/v1"
],
"type": [
"VerifiableCredential",
"ServiceOfferingCredentialExperimental"
],
"id": "https://catalogue.gaia-x.eu/credentials/ServiceOfferingCredentialExperimental/1664145414932",
"issuer": "did:web:compliance.gaia-x.eu",
"issuanceDate": "2022-09-25T22:36:54.932Z",
"credentialSubject": {
"id": "https://compliance.gaia-x.eu/.well-known/serviceComplianceService.json",
"hash": "eeac8a9b5b6750f13fbc548299b22b73d6beea13f19e71856d0027b5cd42069c"
},
"proof": {
"type": "JsonWebSignature2020",
"created": "2022-09-25T22:36:54.932Z",
"proofPurpose": "assertionMethod",
"jws": "eyJhbGciOiJQUzI1NiIsImI2NCI6ZmFsc2UsImNyaXQiOlsiYjY0Il19..SibPFxPtfsKP439SjoKo5VtmU_EpgsfuEjghCt_8sG2fUYT6s9CTY8jyEniGUkk7BIWnIYNsuuKudlNBD27kwzdTy6bZX9Jq0OaAaCpgZAZ9vlp7oFZF3ysLcERmBAixzGUjL0sny06Mu7IRCcDYVhLyd6flOvUGtH2I6T9u6UZL8cN1advRYKd4BSumAp5d4cCG-7cg7DCqPXk_M8cTvU8mDeXvXfciv7sIqvkwqd2L-T4kbxmPTCY3r3wPoVHGBDa3Gnntwkz3_aVInjbztchH-WmlDpCPv1hTv4uZNenNZVw7xsx1_o0voJJLSGtlYNhW4rk2oDxr4qie3S-Zgw",
"verificationMethod": "did:web:compliance.gaia-x.eu"
}
}
}
1.5 Terminology
This section is non-normative
The following terms are especially relevant for the understanding of the standard:
Business Partner Number (BPNBPN A BPN is the unique identifier of a partner within Catena-X.)
A BPNBPN A BPN is the unique identifier of a partner within Catena-X. is the unique identifier of a partner within Catena-X, see CX-0010.
Self Description (SD)
Gaia-X requires all providers to describe themselves and their service offerings using standardized, machine-readable metadata called Self-Descriptions. Such Self-Descriptions will for example include information like the address of a company, a specific service description or certificates and labels.
Participant Agent
A Participant Agent is a service that fulfills the requirements of the CX-0018 standard
Additional terminology used in this standard can be looked up in the glossary on the association homepage.
2 Participant Agent Registration
This section is normative
-
The Core Service Provider B MUST offer a process/workflow to register Participant Agents; Enablement Service Provider as well as Application Service Provider (if they bundle a Participant Agent with their offer) MUST run the Participant Agent registration for their service customersCustomer In the context of OSim, the receiver of produced goods from a supplier.. The provided url endpoint for the Participant Agent service must be in accordance to CX-0018.
-
SD documents MUST be created for every Participant Agent registered by the Participants. The Core Service Provider B make them available.
-
The SD documents used as data source MUST be GAIA-X compliant, i.e. adhering to the GAIA-X Trustframework in the currently supported version in Catena-X. It MUST provide a compliance credential issued from GAIA-X AISBL.
-
In addition, these SD documents MUST be registered at an SD storage like SD-Hub.
3.0 Backward Compatibility
This section is normative, it is not part of the backward compatibility requirement for this standard version.
The EDC Discovery API service MUST be offered as central available endpoint by the Core Service Provider B.
The Core Service Provider B MUST offer each registered Participant Agent via the EDC Discovery API.
The EDC Discovery API can get triggered via technical as well as real users, if relevant roles are available.
For technical user, a company can request the user creation with the technical user creation feature inside the portal.
3.1 APIAPI An API is a way for two or more computer programs to communicate with each other. Endpoints & resources
The EDC Discovery API MUST be implemented as specified here:
Endpoint: POST: /api/administration/connectors/discovery
Request body
the request body can be kept empty (to retrieve a complete list of registered Participant Agents) or be filled with one or multiple BPNsBPNS The unique identifier of a partner site within Catena-X (e.g., a specific factory). to retrieve a list of registered Participant Agent endpoints for the giving BPNsBPNS The unique identifier of a partner site within Catena-X (e.g., a specific factory)..
[
"BPNL....",
"BPNL...."
]
Response structure
[
{
"bpn": "BPNL......",
"connectorEndpoint": [
"http://some.example.url",
"http://some.other-example.url"
]
},
{
"bpn": "BPNL......",
"connectorEndpoint": "http://some.example.url"
}
]
For each BPNBPN A BPN is the unique identifier of a partner within Catena-X. an own response object is provided. In case of multiple Participant Agent instances for one BPNBPN A BPN is the unique identifier of a partner within Catena-X. an array is returned (first result set) otherwise a single value (second result set)
3.2 Available Data Types
The APIAPI An API is a way for two or more computer programs to communicate with each other. MUST use JSON as the payload transported via HTTPHTTP HTTP is an application-layer protocol for transmitting hypermedia documents (such as HTML). It was designed for communication between web browsers and web servers, but can also be used for other purposes..
3.3 Data AssetAsset On the Data Provider side, an Asset describes the data set which will be shared or can be consumed by a Data Consumer. Structure
This APIAPI An API is a way for two or more computer programs to communicate with each other. is not accessed via a Participant Agent but can be queried from any authorized participant or service directly.
3.4 Error Handling
HTTPHTTP HTTP is an application-layer protocol for transmitting hypermedia documents (such as HTML). It was designed for communication between web browsers and web servers, but can also be used for other purposes. standard response codes that MUST be used as described in the following table.
| Code | Description |
|---|---|
| 200 | Discovery request finished successfully |
| 400 | Request body was malformed |
| 401 | Not authorized |
| 403 | Forbidden |
| 405 | Method not allowed |
4 REFERENCES
4.1 Normative References
Following Standards are used within this standard:
CX-0006 Registration and initial onboarding
CX-0010 Business Partner Number
CX-0018 Dataspace Connectivity
Data Space Protocol
GAIA-X Trustframework
Legal
Copyright © 2026 Catena-X Automotive Network e.V. All rights reserved. For more information, please see Catena-X Copyright Notice.