Developers
Let Claude Code, Cursor, Claude.ai or ChatGPT work in your Cheqq workspace, or script it over the REST API.
Your Wapps, records, automations, documents and Apps can be reached from outside Cheqq: by the AI assistant you already work in, or by your own code. Whatever you connect acts as you, in one workspace, and only does what you allowed it to.
What people use it for
- Change a Wapp from your editor. Ask Claude Code to add a Channel field to your Content Studio's ideas and group the board view by it. It reads the collection, adds the field, updates the view, and the change shows up in the Wapp's history, where you can undo it.
- Keep records in step with another system. A nightly script adds the day's orders as records, or marks invoices paid when your bank export says so. Automations that run on new records run for these too.
- Ask about your data in Claude.ai or ChatGPT. "How many leads came in this month, and which ones haven't been contacted?" The assistant counts and filters your records instead of you exporting them.
- Run an automation from anywhere. Start your weekly report from a deploy script, wait for it to finish, and approve its email from the terminal when it asks.
- Edit a document or an App's code with the assistant you prefer. Update the pricing page of your published site, check it builds, and publish it, with a checkpoint before every edit.
Two ways in
Connect an AI assistant
Claude Code, Cursor, Claude.ai and ChatGPT talk to Cheqq over MCP: they see tools for your records, automations, documents and Apps.
Use the REST API
Plain HTTPS and JSON at https://cheqq.ai/api/platform/v1, for scripts, back ends and anything else that speaks HTTP.
Both reach the same things with the same permissions, so a script and an assistant behave the same way.
Start here
Quickstart
Create a key and read your first records in a few minutes.
API keys
Create, scope, expire and revoke keys.
Scopes
What each permission lets a key or an app do.
MCP tools
The tools an assistant sees, and how to choose which.
The Cheqq skill
Teach Claude Code, Claude.ai and other assistants to work in Cheqq the way you would.
What stays the same
- It acts as you. Records it creates, changes it makes and runs it starts are yours, and never go beyond what you can do yourself in Cheqq. If you can only view a workspace, a key for it can only look.
- Everything is undoable where it is in Cheqq. Changes to a Wapp land in its history, deleted records go to the Trash, documents keep every version and Apps keep a checkpoint before every edit.
- You can cut it off at any time. Revoke a key or disconnect an app in Settings → Developer and it stops working on its next request.
For AI assistants
These docs are written to be read by assistants as well as people:
- llms.txt lists every page, grouped by section, with what each covers.
- llms-full.txt is every page in one file.
- Any page is Markdown at its address plus
.md, and Copy page at the top of each page copies it, or opens it in ChatGPT, Claude or Perplexity. - The Cheqq skill teaches an assistant how to work in your workspace.