Grid82 developer documentation
Build on Grid82 from a script, a terminal or an agent. The REST API, the MCP servers and the CLI, for the Studio and for every app.
A Grid82 app is a database plus permissions. Everything a person can do in it, a machine can do too: through the REST API, through MCP for agents, and soon through the CLI. All three are generated from one definition, and every one of them acts as a person, with that person’s permissions and nothing more.
Two products, two APIs
Grid82 has two sides, and each has its own API. Knowing which one you need is most of getting started.
| The Studio | An app | |
|---|---|---|
| Who | builders, who define apps | the people invited into an app |
| Where | https://studio.grid82.app | https://{suite}.grid82.app/{app} |
| REST | the Builder API, /v1 on the Studio | the App API, /{app}/v1 on the suite |
| MCP | https://studio.grid82.app/mcp | https://{suite}.grid82.app/mcp, one server for every app of the suite |
| Can | create apps, change tables and fields, write permission rules, manage people | read and write the records you may see, save views, build your own pages |
Read how the two fit together.
Connect an agent
One prompt to paste into Claude, ChatGPT, Cursor or VS Code. The agent connects itself and you sign in.
Quickstart
Make a key, read a table, write a record: five steps with curl.
App API reference
Records, views, comments, files, SQL, undo and the change feed of an app.
Builder API reference
Organisations, suites, apps, schema, permission rules, people and domains.
Three things that are true everywhere
A credential acts as a person. An API key, an OAuth token and an agent’s connection all belong to someone. A key made by someone in Sales sees what Sales sees. There is no service account with a view of everything. See Authentication.
What you cannot read does not exist for you. A field you may not read is not blanked: it is absent from the records, from the schema, from your OpenAPI document and from your agent’s tools, and no error names it. See Permissions.
Every change can be traced, and most can be undone. Each write, from any surface, lands in the app’s change history. See Undo and history.