Guide
From a key to a decision your code can act on, in the order you will actually do it.
Step 1 Get a key
Keys are issued in the key page of this panel. A key belongs to one consumer and one product; it is shown once, and a lost key is replaced rather than recovered.
Step 2 Call it, and read the decision
The reference — endpoints, parameters, the shape of the answer and the error codes — is on the product documentation page, which is generated from the same catalogue this panel reads.
Step 3 Quota, and what happens at the edge of it
Usage is metered per call against your balance. When the balance will not cover the next call the answer says so explicitly, with its own code, so your software can top up or degrade on purpose instead of guessing from a failure.
Step 4 Webhooks are signed and retried
A result that arrives later is delivered to your endpoint with a signature, and retried with backoff if your endpoint is down. Verify the signature before you act on the body: an unsigned callback is somebody else talking.