Grid82
grid82.comJoin the waitlist
UseIn-app assistant

In-app assistant

Query your tables in plain language, inspect SQL summaries, propose safe edits with approval cards, and build personal views or pages.

Click the assistant button in the bottom-right corner of the Runtime shell (or press the assistant shortcut) to open the In-app assistant panel beside your grid or Interface page.

Runtime in-app assistant drawer displaying prompt bar beside Sales CRM grid

The Runtime in-app assistant open beside the Sales CRM data grid

What you can ask

The assistant runs strictly as you, using the exact schema and records your roles allow:

  • Answer questions across tables. Ask for totals, breakdowns, stalled deals, or summaries (sql.query executes safely through your compiled permissions).
  • Propose record changes. Ask to update statuses, reassign owners, duplicate records, or batch-update matching records. Every mutation renders a structured proposal card for you to review and click Apply before anything changes.
  • Create personal views. Tell the assistant to filter, sort, or save a view tailored to your role (views.create / views.update).
  • Import files (up to 25 MB). Drop a .csv, .tsv, .xlsx, or .json file into the chat. The assistant inspects column headers in a sandbox, confirms the field mapping with you, and proposes one batch import.
  • Build personal pages or automations. When your role permits personal tools, ask the assistant to fork a Template page or draft a personal workflow (my.pages.*, my.workflows.*).

Safety guarantees and AI credit limits

  • Zero silent writes. Read queries run immediately to answer questions; record writes always ask for explicit confirmation on a proposal card first.
  • Invisible restricted data. The assistant never sees hidden tables or fields, so it can never reveal or leak restricted values in conversation.
  • Per-role AI budgets. On Pro and Custom plans, builders can configure monthly AI credit limits per user role so heavy usage in one team never drains credits needed elsewhere.

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.