Wire Contracts
Caracal publishes schema files under docs/public/schemas/ and test fixtures under tests/shared/fixtures/interoperability/.
Schema Files
Section titled “Schema Files”| Contract | Schema |
|---|---|
| Agent connector manifest | caracal-agent-connector-manifest-2026-05-21.schema.json |
| Audit event | caracal-audit-event-2026-05-21.schema.json |
| Audit exporter manifest | caracal-audit-exporter-manifest-2026-05-21.schema.json |
| Gateway upstream manifest | caracal-gateway-upstream-manifest-2026-05-21.schema.json |
| JWT claims | caracal-jwt-claims-2026-05-21.schema.json |
| Policy input | caracal-policy-input-2026-05-20.schema.json |
| Policy pack manifest | caracal-policy-pack-manifest-2026-05-21.schema.json |
| Policy result | caracal-policy-result-2026-05-20.schema.json |
| Provider credential plugin manifest | caracal-provider-credential-plugin-manifest-2026-05-21.schema.json |
| Resource verifier manifest | caracal-resource-verifier-manifest-2026-05-21.schema.json |
| Revocation event | caracal-revocation-event-2026-05-21.schema.json |
| Token response | caracal-token-response-2026-05-21.schema.json |
| W3C baggage | caracal-w3c-baggage-2026-05-21.schema.json |
Fixture Files
Section titled “Fixture Files”Fixtures include valid examples for audit events, audit exporter manifests, Gateway upstream manifests, JWT claims, policy input/results, policy pack manifests, provider credential plugins, resource verifier manifests, revocation events, token responses, W3C baggage, trace context headers, and stream signature canonicalization vectors.
- Use schemas when building connectors, exporters, or provider plugins.
- Use fixtures when adding SDK or interoperability tests.
- Preserve schema filenames when documenting versioned contracts.
Next Step
Section titled “Next Step”Use Compare Editions when deciding between self-hosted Community Edition and managed Enterprise Edition.