Integration Surfaces
Living maturity for every Arbiter surface. Do not assume write capability beyond what this matrix marks live.
Surfaces map to verification layers (Verification): operational day-to-day work, hash-chained integrity on evidence/packages, and optional on-chain Seal.
Matrix
| Surface | Purpose | Verification layer | Maturity | Access |
|---|---|---|---|---|
| Developer Docs (this site) | Contract — states, shapes, boundaries | — | Live | Public |
| Dashboard | System of record UI | Operational | Live | Provisioned users |
| REST API | Programmatic read/write | Operational (+ hashes on evidence) | Live / Early Access | Authenticated + RBAC |
Partner Read /api/v1 | Metadata-only sync envelopes | Hash-chained fields when present | Live / Early Access | arb_ or ID token |
| MCP (authenticated) | Agent tools over the same data | Operational | Live / Early Access | Scoped API key (Bearer arb_…) |
| Product Concierge MCP | Public product Q&A for agents (Cursor) | — | Live | No API key — see Install |
| MCP tool-call runtime guard (OdinGard Cerberus) | Lethal-trifecta hardening on Concierge + authenticated MCP tool handlers | — | Early Access (observe/log; partner: OdinGard) | Automatic on MCP hosts — not Arbiter SoT |
| OpenAPI artifacts (public) | Typed clients for Partner Read + declared early-access slice | — | Live | Public (/openapi.yaml) — not full customer catalog; see API reference |
| Bruno OpenCollection (git) | Executable API contract smoke (host + arb_ + Partner envelopes) | Operational signal only — not audit evidence | Available today (private beta for bru-cli CI) | Clone docs/api/bruno — see Disclosure Boundary |
| Partner sync webhooks | Push/ack governance events | Hash-chained (payload_hash) | Contract published | Partner HMAC |
| Stratum sealing | Seal digests; badge Verified on-chain | On-chain | Available by arrangement | Entitled |
Guidance
- Start with these docs for vocabulary (Lifecycle, Records, Access Model).
- Use the dashboard for human authority on state and release.
- Use REST or MCP within RBAC for programmatic work.
- Use Partner Read for external OS sync — not UI scrape paths.
- Use hash checks by default; use Seal / Verified on-chain only when Stratum is entitled.
- Coordinate before assuming write on non-public surfaces.
Update this matrix whenever a release changes surface availability.