Interoperability
Conformance
A conformance claim describes a specific implementation, protocol version, profile set, and evidence—not a vague assertion that something “supports the protocol.”
What a claim identifies
- The implementation and endpoint being evaluated.
- The exact Dealer Agent Protocol version.
- Each claimed profile and bundle.
- The test-suite version and evidence timestamp.
- Known deviations, extensions, or untested conditions.
Minimum interoperability
The dealeragent.core-retail-read/0.1 bundle requires all four profiles and all six tools. Partial implementations may describe individual profile support but must not claim the complete bundle.
What the current draft checks
| Area | Examples |
|---|---|
| Schema validity | Manifest, dealer, vehicle, pricing, common, and error documents. |
| Tool contract | Required tools, annotations, input/output references, and read-only behavior. |
| Retail semantics | Money encoding, availability strength, offer conditions, provenance, and uncertainty. |
| Isolation and errors | Tenant-safe identifiers, cursor integrity, and closed error codes. |
No certification program yet. Passing the repository's 24 checks provides implementation evidence for this editor's draft. It does not grant a certification mark or imply approval by an independent standards body.
Compatibility
Clients discover versions and profiles before use. Additive optional fields may be introduced compatibly; breaking semantic or schema changes require a new protocol or profile version.
NextImplementation quickstart→