> ## Documentation Index
> Fetch the complete documentation index at: https://docs.crakseo.com/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> For SEO data and indexing, start with /seo-mcp/overview.md and /seo-mcp/connect.md, then read the focused server reference.
> The documentation search MCP at https://docs.crakseo.com/mcp searches documentation only. Product tools use https://crakseo.com/mcp/<server>.
> Check tool availability and API credit balance before paid calls. Request owner approval for paid indexing. Never invent prices, indexing guarantees or directory approval.

# Data tables

> Built-in typed tables that agents read and write with explicit grants.

> [!NOTE]
>
> Available on legacy plans. New workspaces don't include agents; workspaces created before the CrakSEO launch keep them.

**Data** (`/app/data`) gives each project lightweight typed tables, similar to a simple Airtable. Agents use structured tools, not the UI, to query and write rows.

## Columns and limits

Column types: text, long text, number, boolean, date, datetime, URL and select.

| Limit | Value |
| - | - |
| Tables per project | 20 (archived tables count) |
| Columns per table | 50 |
| Rows per table | 10,000 |
| Row size | 256 KiB |
| Project size | 50 MiB |
| CSV import | 512 KiB and 100 rows per import |
| CSV export | 2 MiB |

Columns can be archived but not deleted, and changing a column's type is not allowed. Rows are archived, never permanently deleted. Do not store secrets in tables.

## Giving profiles access

The quickest way is the profile's **Data** page: **Add data source** → **Create a new table** or **Use an existing table** grants the table to that profile and selects it in one step (choose **Allow writes** for read and write). The same picker links to Airtable and remote MCP servers in Integrations. **Remove** on a table's row stops the profile using it; the table and rows stay.

Under the hood, access needs two things:

1. A **grant** for that table (read, or read and write), also available in **Data > Profile access**.
2. The profile's data selection ("What it reads and writes" on its Data page) including that table. For external MCP keys, the key must also have the `data:read` or `data:write` scope.

Neither a scope nor a selection creates a grant on its own. Writes use versions and idempotency keys, so a retried write never applies twice.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.