AgentFacts Spec

Canonical specification for AgentFacts, the universal identity layer for AI agents. This repo is the single source of truth so SDKs and implementations do not drift.

Why This Exists

Teams ship agents across different frameworks and SDKs. Without a shared identity standard:

• Provenance is unclear and signatures cover different payloads.
• Compliance checks vary by team and tool.
• The same agent passes in one system and fails in another.

What AgentFacts Defines

• A canonical AgentFacts Card (identity + metadata).
• A signing model for integrity and provenance.
• Transparency log inclusion proofs for auditability.
• A verification pipeline that is consistent across environments.
• Extensions for third-party attestations without breaking identity.

Status

• Current spec version: v0.1 (draft).
• Spec versions are independent from SDK versions.

Quick Start for Implementers

1. Read the spec entrypoint: spec/v0.1/overview.md.
2. Implement the card format: spec/v0.1/agent-card.md.
3. Implement verification: spec/v0.1/verification.md.
4. Add log proofs: spec/v0.1/transparency-log.md.
5. Support extensions: spec/v0.1/extensions.md.

Versioning

• Each spec version lives under spec/v{N.N} and schemas/v{N.N}.
• Cards MUST include specVersion with the same v{N.N} value.
• Changes MUST update the spec, schema, and relevant examples together.
• Normative terms follow RFC 2119 (MUST, SHOULD, MAY).

Repo Layout

• spec/v0.1/ - normative specification documents for v0.1.
• schemas/v0.1/ - machine-readable schemas aligned to the spec.
• examples/v0.1/ - non-normative example AgentFacts cards.
• rfcs/ - proposals for spec changes.

Interoperability

AgentFacts is canonical. Other standards are supported through exporters/adapters.

• A2A compatibility guidance: spec/v0.1/interop.md.

Governance

Spec changes should be proposed in rfcs/ with rationale and compatibility impact.

Contact

For spec questions or contributions, open an issue or proposal in this repo.