A website platform with a real API.
Everything Cactal does is a documented operation: create a website, write its source, model and publish content, ship a version, roll it back, read the traffic. REST, a typed SDK, and MCP, on every plan including Free.
- Versioned REST API
- Typed SDK and hosted MCP server
- No paywall on the interface
What you can build against.
The dashboard is a client of the same API you get, so there is no private surface you cannot reach.
REST API
A versioned, documented HTTP API at api.cactal.ai/v1, with an OpenAPI description generated from the server rather than written by hand.
Typed SDK
Call the same operations from your codebase with types on the request and the response, instead of hand-rolling fetches and hoping the shape holds.
Hosted MCP server
Nothing to run. Point any MCP client at Cactal and it gets the full operation set with tool descriptions written to be used well.
Source as a first-class resource
Read and write a website’s real files: pages, components, modules, global CSS, and the site config. Search across them, diff two versions, restore an old one.
A CMS you can drive
Define collections and fields, then create, update, reorder, and publish items programmatically. Schema changes migrate existing data.
Publishing as an operation
Run the quality gate, publish, poll the deployment, roll back. Shipping a website is a call, not a pipeline you assemble.
From key to published website.
The whole loop, in the order you will actually write it.
- 1
Get a key
Issue an org- or site-scoped key with read or full-edit access. Rotate or revoke it at any time. Keys can never hold the owner role, so an integration cannot change your bill.
- 2
Write and check
Take the edit lease, write source, then run the quality gate. A failure comes back as diagnostics naming the file and the problem, so your code can act on it.
- 3
Publish and watch
Publish the version that passed, poll until the deployment is ready, and read the traffic it gets. Restore an earlier version whenever you need to.
The things you only find out later.
Written down here because they are the questions that decide whether an integration is pleasant six months in.
One lease, no lost writes
Source edits take a single writer lease, so two agents working at once cannot silently overwrite each other.
Everything is versioned
Every write produces a version. Nothing is destructive, and the history is complete from the first draft.
Atomic multi-file edits
Apply ordered string replacements across many files as one commit. Any failing edit aborts the whole call, so a half-applied refactor is not a state you can reach.
Cursor pagination everywhere
List endpoints are keyset-paginated with opaque cursors, so a page never shifts under you while you walk it.
Errors you can branch on
Failures carry a stable machine-readable kind alongside the message, so retry, permission, and validation cases are distinguishable in code.
Audited by default
Every operation is tenant-isolated and recorded, including the ones your agent runs at three in the morning.
Developer questions
Building something unusual? Talk to us. Talk to us.
No. Full REST, SDK, and MCP access is on every plan including Free. Paywalling the interface would make the platform something agents cannot really use, which defeats the point of building it.
Keys are scoped to one organization or one website, with read or full-edit access, and can be rotated or revoked instantly. A read key can inspect source and content but cannot change either.
Yes. Take the lease, write, run the gate, publish, and poll the deployment, all over the API. The gate is the same one the dashboard runs, so CI cannot ship something the dashboard would have refused.
Nothing reaches your visitors. The write succeeds as a draft version, the gate rejects it with diagnostics, and the published website keeps serving the last version that passed.
At cactal.ai/docs, including the full API reference, guides for each capability, and a page describing how to connect an agent. It is also published in an agent-readable form, so your agent can read the docs before it writes anything.
