IMPLEMENTATIONS

An open registry, not a product hierarchy.

Projects register with a precise profile, ACC version, dated self-assessment, evidence, and known limitations. The same criteria apply to every implementation.

REGISTERED IMPLEMENTATIONS

Evidence before affiliation.

Listing is not certification, a security audit, production-readiness endorsement, partnership, or commercial recommendation.

BailingHub Runtime Profile · ACC v1 · Self-declared

First public implementation used to validate the initial contract. Its control-plane architecture, storage, transport, UI, and product features do not define ACC semantics or receive privileged registry status.

ACC parser

Reads and validates x-agent-capability.

ACC generator

Produces ACC-compatible OpenAPI declarations.

ACC runtime

Enforces scope, risk, subject, approval intent, audit, and execution hints.

ACC policy component

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

REGISTER YOUR PROJECT

Self-assess and publish verifiable evidence.

Choose a profile, publish a dated assessment tied to a release or commit, disclose limitations, and submit a pull request to the registry. Maintainers verify claim completeness and neutral wording, not production safety.

claim example

Implements the ACC v1 Runtime Profile.

Status: Self-declared
Evidence: public assessment + tests
Certification: none

IMPLEMENTATION TYPES

Compatible does not mean identical.

01

Control planes

Turn declarations into routed, audited, governable agent operations.

02

API gateways

Use ACC as policy metadata next to existing API contracts.

03

SDK generators

Produce ACC metadata from framework annotations or source code.

04

Policy engines

Validate risk, subject, approval, and audit declarations before runtime.