● Reference
v3 migration
v3 reduces the surface to 45 operations across 11 resources. Every operation is system-of-record.
§ What changed
1. Capabilities are verbs. Long-running work is dispatched through POST /v1/jobs. See the verb catalog.
2. Zero synthesis. Every operation is system-of-record. Unknown ids return 404. Objects contain what you sent, plus system fields.
3. Workflow products leave the protocol. Claw and Actions move to Mandate.
§ What replaced what
| v2 | v3 |
|---|---|
| Claimants, Debtors, Relationships (3 resources) | Parties: one noun, role field (claimant / debtor / counterparty) |
| 11 packet-creator endpoints | POST /v1/packets with a type enum |
| Enforcement profile + plan | POST /v1/judgments/{id}/enforcement |
| Attribution graph endpoints | crypto.attribute verb (planned) |
| Sanctions screening endpoints | crypto.screen verb (planned) |
| Monitoring resource | crypto.monitor verb (planned) |
| Reports resource | report.exhibit verb (planned) |
| Audit resource | Events + GET /v1/events/verify-chain |
| Organizations list/get | GET /v1/organization (one org per key) |
| Claw, Actions | Mandate product features |
| API keys, users admin | Dashboard concerns, off the protocol |
§ Migration
v2 paths keep answering until October 3, 2026 through the compatibility alias, with Deprecation and Sunset headers pointing at the successor operation. Retired operations return 410 endpoint_retired with a doc_url. Scope names follow the new resource groups; sandbox keys re-mint in one click at kineticanvil.com/sandbox.