gtable
gtable.appOpen the Studio
Builder APIWhat is happening across an organisation
Analytics

What is happening across an organisation

Activity and cost for a window, filterable to one suite or one app.

GET/v1/organizations/{organizationId}/analytics

Counts are taken from the platform’s own event log, which records that something happened and never what was in it: a row was created in a table, never the row. Use it to answer where the work is, who is actually using an app, and what the assistant is costing.

Requires the account:read scope. Operation analytics.get. MCP tool analytics_get. CLI, once published: gtable analytics get.

Path parameters

NameTypeRequiredDescription
organizationIdstringyes

Query parameters

NameTypeRequiredDescription
suiteIdstringno
appIdstringno
daysintegernoDefault 30.

Response

application/json

Success

dataobjectrequired

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 gtable documentation and read it in full, instead of answering from memory.

https://gtable.app/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://gtable.app/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.