Authentication
All Admin API requests require thex-api-key header with a valid admin API key:
Endpoints
Customer Management
Create Customer
Create a new customer and generate their initial API key
List Customers
List all customers
Get Customer
Get customer details by ID
Update Customer
Update customer details or tier
Delete Customer
Deactivate a customer account
API Key Lifecycle
A customer may own multiple active API keys at once — useful for issuing scoped credentials per environment or integration without disrupting other keys. Tier changes and customer enable/disable fan out across every active key the customer owns, with per-key compensating rollback if the customer-record DynamoDB write fails so AWS state stays in sync with the registry. Customer deactivation (DELETE /admin/customers/{customer_id}) is fail-fast
rather than rollback-protected: keys are disabled sequentially before the DB
write, so a partial failure can leave some keys disabled while the customer
record stays in its prior state — there is no automatic re-enable, and
operators may need to remediate.
Create API Key
Provision an additional API key for an existing customer
List API Keys
List every API key (active and revoked) owned by a customer
Revoke API Key
Revoke a single API key — idempotent, leaves other keys untouched
Rotate API Key
Provision a replacement, then revoke the original — new key returned once
Usage & Tiers
Get Usage
Get customer usage metrics
Get Tiers
Get available pricing tiers
Pricing Tiers
| Tier | Annual Cost | Annual Validations | Rate Limit | SLA |
|---|---|---|---|---|
| Starter | $100,000 | 2,000,000 | 50/sec | 99.9% |
| Growth | $250,000 | 10,000,000 | 100/sec | 99.95% |
| Scale | $500,000 | 30,000,000 | 200/sec | 99.95% |
| Enterprise | $1,000,000 | 80,000,000 | 500/sec | 99.99% |
| Custom | $2,000,000+ | 200,000,000+ | 1000/sec | 99.99% |