Docs

Everything a developer — or an AI assistant — needs to work with ThatMgmt.

MCP server

The fastest way in for an agent. On npm and the official MCP registry:

npx @thatmgmt/mcp

Public availability and quote tools need no key; tenant tools use your API key. Source: https://github.com/Thingscorp/thatmgmt-mcp

Try it free, no signup

Two public endpoints on https://api.thatmgmt.com, rate-limited per IP:

• GET /v1/public/availability?domain=example.com — is the name free?
• GET /v1/public/quote?domain=example.com&period=1 — the locked price: wholesale, the 0.15% line, the total.

Resources

• Interactive API reference — browsable OpenAPI viewer (Redoc).
• openapi.json — the raw machine-readable spec.
• llms.txt — concise AI-assistant index of this site.
• llms-full.txt — the full AI-assistant reference: purchase flow, offering matrix, route surface.

New here? Start with GET /v1/capabilities for live discovery and GET /v1/offerings for the offering coverage matrix. How the platform fits together is on the Platform page.

Getting access

Every /v1/… route needs a bearer token. Tokens are provisioned by the platform operator during tenant onboarding: each tenant gets a scoped token that only permits its granted actions. There is no self-service signup yet — tokens are provisioned by the platform operator during tenant onboarding.

Response codes

• 401 — missing or invalid bearer token. Every /v1/… route requires authentication; the /health/… probes do not.
• 405 — wrong HTTP method on a known route; the response carries an Allow header naming the supported method.
• 409 — an entitlement-gated portfolio read whose supplier category is unverified.
• 429 — the per-tenant rate budget is exhausted. Error code rate_limited ("Too many requests", retryable) with a Retry-After header naming the wait in seconds; health probes are exempt.

Errors use a neutral envelope: {code, message, retryable, details}.