A2A Agent Card bridge
An A2A Agent Card, served at /.well-known/agent-card.json, tells other agents what an agent can do and how to call it. An OCC Agent Record says who operates it, who answers for it, what it is allowed to do and how to report harm. The two answer different questions. This bridge lets each point to the other, so operators do not have to type the same facts twice.
Start a record from an Agent Card
Paste a card to see which OCC fields it fills. The same import is on step 1 of the record workflow in the portal. Anything the card does not say stays empty; nothing is invented.
Runs in your browser. Nothing is sent or stored.
| Agent Card field | OCC Agent Record field |
|---|---|
| name | Agent name |
| url, or the first supportedInterfaces[].url | Agent identifier (a DID, SPIFFE ID or signed key reference is stronger) |
| version | Version |
| provider.organization / provider.url | Operator / operator contact |
| description + skills[].name | Purpose |
| skills[] | Declared authority, as a starting point only |
| securitySchemes, signatures | Not copied. Shown as notes |
| (not on a card) | Principal, accountable person, redress, limits, mandate expiry, effective authority, classification, revocation |
Point your Agent Card at your OCC record
A2A lets a card declare extensions under capabilities.extensions. Every listed public record offers a ready-made block at /occ/records/<ref>/a2a-extension.json. It is never required, adds no methods or headers, and carries the record URL, its SHA-256 digest and the key IDs that signed it. The extension URI https://openconformance.org/occ/ext/agent-record/v1 resolves to its description.
{
"capabilities": {
"extensions": [
{
"uri": "https://openconformance.org/occ/ext/agent-record/v1",
"description": "Points to this agent's public OCC Agent Record: who operates it, who answers for it, and how to report harm. A pointer to a public record; it does not show the agent is safe or compliant.",
"required": false,
"params": {
"record_ref": "OCC-EXAMPLE",
"record_url": "https://openconformance.org/occ/records/OCC-EXAMPLE/record.json",
"record_sha256": "0000000000000000000000000000000000000000000000000000000000000000",
"register_jwks": "https://openconformance.org/occ/jwks.json",
"key_ids": [
"<ed25519-key-id>",
"<ml-dsa-65-key-id>"
],
"log_entries": "https://openconformance.org/occ/log/entries.json?ref=OCC-EXAMPLE"
}
}
]
}
}Illustrative values. If you amend the record, the digest changes; fetch the block again.
Discovery from your own domain: /.well-known/occ-record.json
We propose that an operator may serve the same pointer from its own domain, so anyone holding only a hostname can find the record. This is a proposal open for comment. It is not registered with IANA and nothing depends on it.
{
"type": "occ.record-pointer/v1",
"status": "proposal",
"records": [
{
"record_ref": "OCC-EXAMPLE",
"record_url": "https://openconformance.org/occ/records/OCC-EXAMPLE/record.json",
"record_sha256": "0000000000000000000000000000000000000000000000000000000000000000",
"register_jwks": "https://openconformance.org/occ/jwks.json",
"key_ids": [
"<ed25519-key-id>",
"<ml-dsa-65-key-id>"
],
"log_entries": "https://openconformance.org/occ/log/entries.json?ref=OCC-EXAMPLE"
}
]
}What the bridge does not do
The bridge does not verify Agent Card signatures, does not check that the card and the record describe the same running system, and does not grant, scope, delegate or revoke authority. A matching digest shows the record has not changed since the block was issued. It does not show the agent is safe or compliant, and OCC does not certify. Check record signatures at Verify a record and publication at the transparency log.
Comments on the extension and the well-known proposal are welcome through the open review.