Contact Message form
Write to us.
You do not need this form to start. The console is open. Use this to reach us about an evaluation, a question the docs do not answer, or a seat when none are free. The operator reads it in the admin view of the console, and the record of it stays with the API.
Seats are limited. Seats are bounded by review capacity, not by infrastructure.
Hosted surface Live
The hosted API is live.
These gates held before launch. Each row names the check you can run yourself. Read the limits page in the docs before relying on any of them.
| Launch gate | Why it matters | The check | State |
|---|---|---|---|
| Durable production storage | The service must refuse to start rather than accept records into memory that can disappear. | GET /v1/health reports storage: postgres. | Live |
| Usage counting | Account limits and usage statements need a real counter that can be read back later. | GET /v1/usage/summary counts calls per key and capability. Counted, not billed. | Live |
| Notification delivery | Security and usage notices need real producers, delivery, and retry handling. | GET /v1/notifications shows delivery status per channel; webhooks drain every two minutes with bounded retry. | Live |
| Matching verification results | A signature check and a chain-position check are different questions and must be answered separately. | The offline verifier and POST /v1/delegations/verify give the same reason for the same token. | Live |
| Public wording review | The source, the rendered site, and the current evidence must say the same thing. | The docs are regenerated from the API description, and a docs-current gate diffs them. | Ongoing |
There is no client library to install and no evidence file to download. A private client for one integration can be discussed.
Sign in to the console Read the docs