thin.host / domains

The domain layer
for the agent era

MCP-native custom domains. Your agent provisions. Your user pays. You keep the relationship.

Try the MCP Server Platform Dashboard
# Your agent provisions a domain in one call
result = await mcp.call("provision_domain", {
  "domain": "mysite.com",
  "origin_url": "https://app.vercel.app",
  "user_email": "user@example.com"
})
# → { claim_url, dns_instructions, provision_id }

The problem

Agents ship code, content, and entire apps. But they can't ship domains.

Agents can't close the loop

Your agent deploys a site but hands the user a markdown checklist for DNS. Conversion dies at the handoff.

APIs assume a human integrator

Existing custom domain APIs were built for a developer reading docs, not an agent making tool calls.

No billing topology

Your platform eats the domain cost or sends users to configure Cloudflare. Neither scales.

The solution

One API call. User pays. You profit.

MCP server, day one

5 tools your agent calls directly. Provision, check, update, release, list. Designed for agent reasoning.

Hosted claim & payment

End users complete Stripe checkout + DNS setup on a page you never have to build. White-labelable.

Built-in rev-share

Default: user pays $8/mo, you keep $4. Set your own retail price. Custom splits on platform tier.

How it works

Three steps from agent call to live domain.

1

Agent provisions

Your agent calls thin.host via MCP or REST. Gets a claim URL and DNS instructions.

2

User claims & pays

End user visits the claim page, pays via Stripe, and sees registrar-specific DNS instructions.

3

Domain goes live

DNS propagates, SSL auto-provisions, and the agent gets a webhook confirmation. Done.

Pricing

Start free. Scale when your agents do.

Free
$0
  • 3 domains
  • 100 API calls/day
  • MCP server access
  • Community support
Indie
$29/mo
  • 25 domains
  • 10K API calls/day
  • Custom claim domain
  • Email support
Platform
$199/mo
  • Unlimited domains ($1/ea after 50)
  • White-label claim pages
  • Webhooks & SLA
  • Priority support
Enterprise
Custom
  • Dedicated infrastructure
  • Self-hosted option
  • Custom contracts
  • Dedicated IP

How we compare

thin.host Approximated Cloudflare for SaaS
Designed forAgentsHuman devsHuman devs
MCP serverDay 1NoNo
End-user billingHostedDIYDIY
Apex domainsYesYesEnterprise
White-labelYesLimitedNo
Rev-share built inYesNoNo

FAQ

What's MCP?

Model Context Protocol is an open standard that lets AI agents call external tools. thin.host ships an MCP server so Claude, GPT, and other agents can provision domains directly.

How is this different from Approximated?

Approximated is excellent infrastructure — we use it under the hood. thin.host adds the agent-native interface (MCP + structured API), the end-user billing flow, and the platform rev-share layer that Approximated doesn't ship.

Can I self-host?

Enterprise tier includes a self-hosted option. For most use cases, the managed service is simpler and cheaper.

What happens if a user doesn't pay?

The domain stays in pending_payment status. The claim link expires after 24 hours. The agent can re-provision to generate a fresh link.

Do you support subdomains?

Yes. Both apex domains (mysite.com) and subdomains (app.mysite.com) are supported. Free *.thin.host subdomains are coming in a future release.