Platform
ThatMgmt is a domain API platform that actually executes. One control plane serves HTTP, MCP, and CLI clients alike. Approved, funded orders run: registration, renewal, transfer. Nothing executes blind.
Real execution, gated writes
This is not a quote generator. Dry-runs show the full plan first — itemized pricing, readiness checklist, what is still gated — and the locked total binds approvals, budget reservation, and spend checks. Once approved and funded, the order executes. Nothing executes blind.
Crypto checkout
Every order gets a unique deposit address. Send USDC, ETH, or SOL from any wallet you already hold. No card, no bank account, no signup.
Locked quotes
Every spend-effect action starts with a locked quote. The quote carries totalPayableCents and a fee fingerprint. The total you approve is the total that executes. Try it with no signup: GET /v1/public/quote?domain=example.com&period=1.
Discovery, built in
Capabilities are discoverable at runtime — clients don't need out-of-band documentation to know what's available:
GET /v1/capabilities— the live discovery endpoint describing the API's capabilities.GET /v1/offerings— the offering coverage matrix: the eight offering ids and what each covers.
The OpenAPI spec documents the full route surface. See the docs hub for the route table and the raw spec.
Entitlement-gated reads
Reads are gated on entitlement evidence. Evidence is caller-supplied: the platform reports what it can verify and marks anything unverifiable as "unknown" rather than guessing. When entitlement can't be verified for an offering, the corresponding read routes return 409.
Rate limiting
Authenticated routes share one per-tenant rate budget, checked after authentication and before dispatch. When the budget is exhausted the API returns 429 with a Retry-After header naming the wait in seconds; the error envelope is marked retryable (rate_limited). Unauthenticated health probes are exempt.
Errors
Failures return a neutral error envelope: code, message, retryable, and details.
White-label posture
Your customers see you, not the platform. Public ids, error messages, OpenAPI descriptions, and notifications use neutral, customer-facing naming — no supplier brands appear anywhere a customer can see.