● Reference

Versioning

The protocol versions by date, pinned per key. Send MD-Version: 2026-06-11 on every request; omit it and your key is pinned to the version current at first call.

Stable + additive

The surface is stable and grows additively: new operations, fields, and events ship anytime with a changelog entry. Breaking changes — renames, removals, shape changes — ship only under a new date version with a migration note.

How the pieces fit

The /v1 path prefix never changes — it is the protocol, not a version you migrate across. The date version (MD-Version) is what gates payload shapes: two keys on different dates can call the same path and get differently shaped responses. Keys pin to a date version at first call and stay pinned until you move them, so an upgrade is a deliberate act, never a surprise.

Machine-readable spec

The full surface ships as a validated OpenAPI 3.1 document: openapi.yaml (108 operations, 32 webhooks, 62 scopes).