thin.host Documentation

thin.host is the hosting and domain layer for the agent era. It provides an MCP server and REST API that lets AI agents publish the sites they generate straight to live hosting, provision custom domains end-to-end — including taking the user's payment and handling DNS configuration — and send transactional email.

Quick Links

• Quickstart: MCP (5 minutes) — Add custom domains to your Claude Desktop agent
• Quickstart: REST API — Integrate via HTTP from any language
• Get access to email — Zero to sending: request access, approval, first send
• REST API Reference — Full endpoint documentation
• MCP Tool Reference — All 9 MCP tools explained

How It Works

1. Your agent calls thin.host — via MCP tool or REST API — to provision a custom domain
2. thin.host returns a claim URL — your agent shows this to the end user
3. The user claims & pays — Stripe checkout, DNS instructions, live status on a hosted page
4. Domain goes live — SSL auto-provisions, webhook confirms to your platform

Key Concepts

• Platform — Your account. Has an API key, webhook URL, and plan tier.
• Domain — A custom domain provisioned through your platform. Has a lifecycle: pending_payment → pending_dns → pending_ssl → active
• Claim Session — A short-lived (24h) token/URL where end users complete payment and DNS setup
• Rev-Share — End user pays $8/mo, split between thin.host and your platform

Architecture

thin.host is a managed layer that handles proxy and SSL, with Stripe for billing. Your agent never talks to the proxy or Stripe directly — thin.host handles the entire stack.

Agent (Claude, GPT, etc.)
  │
  ├── MCP call ──→ thin.host MCP Server
  │                    │
  ├── REST call ──→ thin.host API (/v1/)
  │                    │
  │                    ├── Proxy + SSL layer
  │                    ├── Stripe (billing)
  │                    └── PostgreSQL (state)
  │
  └── claim_url ──→ Hosted Claim Page (end user)