Developers
Build with a very small world
Guides to the API, the MCP server and the permissions that keep every workspace separate.
- Quickstart: your first API calls Create a connection, make a draft casa, edit it safely and publish it, all with a handful of requests.
- Authentication and scopes One workspace per token, only the permissions you tick, and nothing more than your own role allows.
- Connect an agent over MCP Point an MCP client at your workspace with a scoped token, and let it use the same operations as the API.
- API reference and conventions The OpenAPI contract, plus the few rules every client follows: idempotency keys, ETags, jobs and problem details.
- Webhooks Signed HTTPS requests when jobs, domains, publications or approvals change, delivered at least once.
- Bulk operations for domain portfolios Import, dry-run, approve the exact plan, then run it in batches you can pause, retry and roll back.
Some features still run against simulated providers. Your workspace’s capabilities list says which ones are live, so read it before you plan work that depends on them.