📄️ Authentication
A project API key looks like proj... The middle segment identifies the key; the last is the secret, which is hashed on our side and never recoverable after creation.
📄️ Errors
Failures are reported with a standard status code:
📄️ Getting started
Every endpoint is scoped to a single project. You authenticate with a project API key, and the key decides both which project you reach and what you may do inside it — there is no credential that spans projects.
📄️ Workflows as MCP tools
Any workflow can present itself to an AI agent as an MCP tool server. The workflow describes its own tools, and each tool call runs the workflow again with the tool name as the event.
📄️ Permissions
A key carries an explicit list of permissions, and nothing is granted by default. A request with a valid key but the wrong permission is rejected with 403, distinct from the 401 you get for a missing or invalid key.
📄️ Running workflows
There are two ways to run a workflow, and the right choice depends on how long it takes.
📄️ Working with databases
Each project can hold Postgres databases, and the API reaches them at three levels: the database, its tables and columns, and the rows inside them. Start with List databases — every other endpoint takes a database id.