Start for free. Sign up without a card and you'll get a test project and a test key right away. Once your company (or, for a personal account, you) is verified, you can create a live key in the portal.
Hypamoon docs
The infrastructure your chat or agent builds on for a business. Sites and apps, data and forms, media, domains, email, payments, phone, SMS and chat, and agents, through MCP or REST.
Hypamoon is the infrastructure your chat or agent builds on for a business: sites and apps, data and forms, media, domains, email, payments, a phone that answers, and agents. You ask in Claude, ChatGPT or Grok, your chat builds it, and it runs on Hypamoon, on a real address or your own domain.
The guardrails are built into the product and can't be switched off: every key has a rate limit, every project has a spending cap, an AI assistant always says it's an AI, recordings are announced to callers and deleted under the retention policy, and project data is stored in Europe.
Get started
From your chat. Connect Hypamoon once at hypamoon.com/connect: pick Claude, ChatGPT, Grok or another chat and follow the clicks. You sign in, or create a free account, as you connect; no card is required. Then ask for what you need. The Quickstart walks through a first session.
From code or a coding agent. Sign up at https://app.hypamoon.com and you get a project and an API key right away; your code sends the key as a bearer token to the REST API (see Authentication). Claude Code, Cursor and other coding agents add the MCP server instead (see MCP).
Everything starts in test mode: sites, data and apps are real, while calls, SMS, email to other people and payments are simulated and nothing is charged. Each of those goes live on its own in the portal at https://app.hypamoon.com/go-live, after the verification it needs.
What's in it
Each part works on its own, and they share one project: a form on your site lands in your data, a missed call becomes a text, a paid order becomes a webhook.
| Part | What it is | Read |
|---|---|---|
| Sites & apps | Pages at https://<slug>.hypamoon.app or on your own domain, with versions, previews, rollback, a password or a secret link. An app adds server code under /api, sign-in, uploads and its own database. |
Sites, Build a full app |
| Data and forms | Collections of JSON documents, public forms with a bot check, and an email or webhook for every new entry. | Data and forms, reference |
| Media | A library for the project's photos and files, uploaded in the portal or from a phone, and put on any site. | Media, reference |
| Domains | Check a name or connect a domain you own. Existing records are copied first, so email keeps working. | Your own domains, reference |
| Email from your domain | Email from a verified sending domain to people the project already knows, never bulk. A module the owner turns on. | Email, reference |
| Payments | Products, a checkout and a cart on your own site, orders, refunds, gift cards and paid access, paid into your own account. | Payments |
| Phone, SMS and chat | A number that rings your team first and lets an AI receptionist answer, SMS, calls to people who expect them, and a chat on your site. Numbers and calls work in the Netherlands today; other countries follow (waitlist). | Phone, SMS and chat, Calls |
| Agents | Instructions that run on an event or a schedule, and ask before they contact anyone. | Agents, reference |
| Agencies | For an agency that builds for clients: a project per client, built before the client has an account and taken over by the client later, who then decides what the agency may do. Usage, who pays and payment links per client. | Agencies, reference |
| Webhooks | A signed event for a finished call, a new document, a paid order or a low balance. | Webhooks |
The API is also an MCP server, so a chat or coding agent can do all of the above and write the integration.
Base URL
https://api.hypamoon.com/api/v1Every request is HTTPS and authenticated with an API key (or, from a chat app,
an OAuth token) in the Authorization header. See
Authentication.
Conventions
| Format | JSON in and out, UTF-8. Errors are application/problem+json. |
| Field names | English, snake_case. |
| Timestamps | ISO 8601 in UTC, for example 2026-09-21T14:10:02.118Z. |
| Phone numbers | E.164, for example +447700900123. Examples in these docs use that fictional range; a real Hypamoon number is shown masked, like +•••••••••42. |
| IDs | Most objects have UUIDs; events start with evt_, request IDs with req_. |
| Missing values | null, never an empty string. Lists are [], never null. |
For agents and code generators
Two files describe the entire API:
/docs/openapi.json: the OpenAPI 3.1 description, for a client generator, Postman or your agent. The API reference is generated from it./docs/llms-full.txt: every endpoint, object, event and error as plain text, to paste into a prompt or give to an agent.
GET /openapi.json on the base URL returns the same document.
Versioning
The path carries the version (/v1). Within a version, we only add things: a
new field, a new endpoint, a new event type. Renaming or removing a field means
a new version. Write your code to ignore unknown fields and event types rather
than treat them as errors.
Where to go next
- Quickstart: from your chat or from code to a site with a working form.
- Build a full app: sign-in, data per user, uploads.
- Payments: sell on your own site.
- Phone, SMS and chat: a number that answers, SMS and chat.
- Test mode: test keys, test numbers and simulated calls.
- Authentication: keys, scopes, rate limits, errors.
- Webhooks: events, signatures and retries.
- MCP: connect Hypamoon to your chat or coding agent.
- Errors: every error type and how to fix it.
- API reference: every endpoint.