Agent Capability Contract Open contract for A2B systems

IMPLEMENTER PATH

Implement the contract, not a product architecture.

ACC defines portable capability semantics. Your parser, generator, gateway, policy component, or runtime remains free to choose its language, storage, transport, model, approval system, and deployment topology.

CHOOSE A PROFILE

Make only the compatibility claim you can prove.

ACC parser

Read, validate, preserve, and diagnose ACC declarations.

ACC generator

Produce schema-valid declarations without duplicating OpenAPI parameters.

ACC runtime

Apply exposure, governance, authority-boundary, and traceability semantics.

ACC policy component

Enforce a named subset of ACC semantics for another runtime or gateway.

REFERENCE LIFECYCLE

A portable path from declaration to business execution.

Ingest the contract, filter exposed capabilities, validate typed arguments, evaluate governance, carry a trusted acting subject, let the business system authorize the operation, then preserve a redacted result or failure trace.

An LLM loop, approval product, database, queue, signature algorithm, console, and cost system are optional implementation choices rather than ACC requirements.

reference sequence
declaration
  -> exposure policy
  -> typed arguments
  -> governance check
  -> trusted subject
  -> business authorization
  -> execution
  -> redacted trace

OPEN REGISTRATION

Self-assess, publish evidence, and register.

ACC has no certification program. Implementations publish a dated self-assessment, declare known limitations, and submit evidence under the same neutral criteria.