SDKs & clients
First-party language SDKs are not required. Generate a typed client from the published OpenAPI 3.1 document, or attach an agent via MCP.
Maturity: OpenAPI artifacts are Live; generated clients inherit whatever maturity the called surface has (Integration Surfaces). Prefer product vocabulary from Records and Lifecycle over inventing field synonyms.
OpenAPI typed clients
| Artifact | Use |
|---|---|
/openapi.yaml | REST and Partner Read /v1 |
/partner-events.openapi.yaml | Webhook / inbound remediation contract |
# Example: openapi-typescript
npx openapi-typescript https://docs.arbiter.blockskunk.com/openapi.yaml -o arbiter.ts
Browse the interactive reference (copy/paste curl — live try-it is disabled by design): API reference.
REST vs MCP
| Concern | REST | MCP |
|---|---|---|
| Surface area | Partner + customer REST (OpenAPI-covered) | ~30 tools across core domains |
| Write coverage | Full covered write paths | Risks, controls, assets, policies, incidents, evidence, suppliers, CAPAs |
| Schema discovery | OpenAPI 3.1 | tools/list JSON Schemas at runtime |
| Best fit | Scripts, ETL, partner OS sync | AI agents, conversational workflows |
One arb_ key authenticates both. See MCP and Authentication.