Grid82
grid82.comJoin the waitlist
Get startedWelcome

Welcome to Grid82

What Grid82 is, who it is built for, and which guide to open first based on what you want to do.

Grid82 turns relational data and strict permissions into internal tools, client portals, and agent-ready APIs. Each app combines an Airtable-style data grid, custom TypeScript interfaces, durable workflows, and an AI assistant that proposes edits safely before you apply them.

Pick your starting path

What you read first depends on your role in a workspace:

  • Building apps in the Studio. Start with Key concepts to learn the Studio and Runtime split, then follow the UI quickstart to create a suite, define tables, configure permissions, and open your app in Runtime.
  • Using an app you were invited to. Jump to App shell to learn navigation across the Data grid, Interface pages, approvals, and the assistant.
  • Automating with an agent, CLI, or script. Read Developer quickstart to run your first API and CLI calls, or go straight to Set up your agent.

What comes out of the box for every app

When you create a table and set permissions in the Studio, Grid82 generates five surfaces automatically from that single definition:

  1. Data grid: A fast relational table editor with filtering, sorting, grouping, inline record creation, comments, and record history.
  2. Interface pages: Custom TypeScript + React screens built with Grid82’s UI kit, sandboxed on a separate origin (pages.grid82.app) for cross-origin safety.
  3. Workflows: Event-driven, scheduled, webhook, and manual TypeScript automations with built-in waits, human approvals, and AI decision steps.
  4. REST API and CLI: A per-caller OpenAPI spec (/{app}/v1/openapi.json) and matching grid82 CLI commands that mask hidden tables and fields automatically.
  5. MCP server: One Streamable HTTP server per suite (https://{suite}.grid82.app/mcp) with OAuth 2.1 consent per app.

Use these docs with your AI tools

An AI agent can read this documentation directly. You do not need an account or an API key. Everything here is public and read-only.

Query these docs via MCP

Recommended

Add this server to Claude, Claude Code, Cursor, Mistral, or any tool that supports MCP. Your agent can then search Grid82 documentation and read it in full, instead of answering from memory.

https://grid82.com/docs/mcp
  • searchFind the passages that answer a question.
  • fetchRead one page in full, as Markdown.
  • list_pagesSee every page in this documentation.

Query these docs over HTTP

The same tools also work as plain web requests. Use this for scripts, or for any tool that does not support MCP. There is one endpoint per tool. Arguments go in the query string, and the answer comes back as JSON.

https://grid82.com/docs/api/docs/search?query=custom+domain

Read the OpenAPI description. It is built from the same definitions as the tools, so it always matches what the endpoints do.

Read these docs as Markdown

Add .md to any page URL to get its Markdown source. You can also send the headerAccept: text/markdown to the page URL itself.

To read the whole documentation in one file, open llms-full.txt. For a short index of every page, open llms.txt.