# NocoDB vs Teable > NocoDB scores 75.7 (BB) on agent readiness against Teable's 61 (C), and leads in 6 of 7 scored categories. Both do sheets records. Category scores, facts, verdicts and agent notes side by side. - Canonical: https://www.anchorterminal.com/compare/nocodb-vs-teable - Markdown: https://www.anchorterminal.com/compare/nocodb-vs-teable.md (~2,350 tokens) - Slim: https://www.anchorterminal.com/compare/nocodb-vs-teable.min.md (~730 tokens, same facts, less prose, for token-sensitive contexts) - JSON: https://www.anchorterminal.com/compare/nocodb-vs-teable.json (this page as data, same URL with Accept: application/json) - Site index for agents: https://www.anchorterminal.com/llms.txt (full text: https://www.anchorterminal.com/llms-full.txt) - API: https://www.anchorterminal.com/api/v1/index.json - Updated: 2026-10-08 NocoDB scores 75.7 (BB) on agent readiness against Teable's 61 (C), and leads in 6 of 7 scored categories. Both do sheets records. - NocoDB: grade BB, 75.7/100, rank #37 of 722. Markdown https://www.anchorterminal.com/tools/nocodb.md · JSON https://www.anchorterminal.com/api/v1/tools/nocodb.json - Teable: grade C, 61/100, rank #379 of 722. Markdown https://www.anchorterminal.com/tools/teable.md · JSON https://www.anchorterminal.com/api/v1/tools/teable.json ## Which one, for what ### NocoDB (BB) Good for: Teams that want Airtable-style typed records with the option to self-host, and an agent that reads, filters and writes records or builds schema through MCP with a narrow allowlist. Ahead on: - Reliability, 97 against 72 - Schema & documentation, 85 against 75 - Agent ergonomics, 74 against 65 - Security & auth, 71 against 62 - Maintenance & community, 87 against 76 - Transparency & trust, 76 against 64 Also in its favour: - Agent-ready, a grade of BB or better - No incidents deducted, where Teable loses 3 points for them Watch for: 5 requests a second per user on every plan, shared by all of that user's tokens, with a 30-second block after a 429 ### Teable (C) Good for: Teams that want Airtable-style typed tables on PostgreSQL that they can also self-host, with an agent reading and writing records through tokens limited by scope and project, or through the vendor's CLI and skill. Also in its favour: - Open source Watch for: The OpenAPI file documents only 200 and 201 responses for nearly every operation, and the error page lists HTTP statuses without a table of error codes ## Score by category | Category | Weight | NocoDB | Teable | Edge | | --- | --- | --- | --- | --- | | Reliability | 16% (20 this run) | 97 | 72 | NocoDB +25 | | Performance | 10%, pending | pending | pending | not scored in this run | | Schema & documentation | 13% (16.2 this run) | 85 | 75 | NocoDB +10 | | Agent ergonomics | 13% (16.2 this run) | 74 | 65 | NocoDB +9 | | Security & auth | 14% (17.5 this run) | 71 | 62 | NocoDB +9 | | Payments & pricing | 10% (12.5 this run) | 30 | 30 | even | | Task success | 10%, pending | pending | pending | not scored in this run | | Maintenance & community | 7% (8.8 this run) | 87 | 76 | NocoDB +11 | | Transparency & trust | 7% (8.8 this run) | 76 | 64 | NocoDB +12 | | Negative events | ≤15 | 0 | -3 | | | **Total** | | **75.7 · BB** | **61 · C** | | ## Facts side by side | Fact | NocoDB | Teable | | --- | --- | --- | | Kind | HTTP API | HTTP API | | Vendor | NocoDB Inc | Teable AI, Inc. | | Hosted endpoint | `https://app.nocodb.com` | `https://app.teable.ai/api` | | Transports | HTTP, Streamable HTTP | HTTP | | Auth | OAuth or key | OAuth or key | | Pricing | Freemium | Freemium | | x402 | no | no | | Licence | Sustainable Use License 1.0 since January 2026 (source-available, not OSI-approved; AGPL-3.0 before). NocoDB Cloud is a proprietary service under NocoDB's Terms of Service | AGPL-3.0 with additional brand terms for the backend and web app, MIT for the packages directory. Enterprise functions and the `@teable/cli` package (ISC on npm) are built in a private repository | | Tools exposed | 199 | none | | Read-only variant documented | no | no | | llms.txt | yes | yes | | Last release | 2026-09-29 | 2026-10-06 | | Terms last updated | 2025-10-14 | 2026-05-25 | | Privacy policy last updated | 2026-03-20 | 2026-10-01 | | Customer content may train models | not found in the text | not found in the text | | Terms restrict automated access | not found in the text | yes | | Terms restrict benchmarking | not found in the text | yes | | Terms or service can change without notice | not found in the text | yes | | Arbitration or class-action waiver | yes | yes | | Popularity | 65k stars, 6.3k npm/wk | 22k stars, 179 npm/wk | ## Verdicts **NocoDB.** API tokens and MCP connections are limited by permission category and by base, and an MCP connection registers only the tools it is allowed. The v3 REST API has a public OpenAPI file. Requests are capped at 5 a second per user, REST writes take 10 records a call, and the Free plan stops at 1,000 API calls a month. **Teable.** Personal access tokens and OAuth tokens carry per-action scopes, and tokens can be limited to chosen spaces and projects. The public OpenAPI file covers 841 operations. Error responses beyond 200 and 201 are missing from that file, no idempotency keys were found, and the cloud allows 10 requests a second on every plan. ## Before you call either ### NocoDB 1. Create a fine-grained token limited to the bases and categories the task needs. Send it as `xc-token` or as a Bearer token 2. Stay under 5 requests a second across all tokens of one user. After a 429, honour `Retry-After` or wait 30 seconds 3. Send REST writes in batches of 10 records. The MCP record tools take up to 100, counted as one API call per 10 records 4. Write date filters with a sub-operator, such as `(due_date,eq,exactDate,2026-06-01)`, and put no space after `~and` or `~or` 5. Use `/records/upsert` with a merge key so a repeated write updates the record instead of adding a duplicate ### Teable 1. Send `Authorization: Bearer ` to `https://app.teable.ai/api`. A 403 with code `restricted_resource` usually means a missing scope or a project outside the token's list 2. Page records with `take` of 100 at most. Personal keys created on Teable Cloud since 10 September 2026 are capped at 100 a request 3. Ask for totals from `/api/table/{tableId}/aggregation/row-count`. Record lists stopped returning them by default on 2 September 2026 4. Keep to 10 requests a second, back off on 429, and check before retrying a failed write because no idempotency key exists 5. Pass `fieldKeyType=id` so renamed fields don't break writes, and leave `typecast` off unless values need converting ## Questions ### Which is better for AI agents, NocoDB or Teable? NocoDB scores 75.7 (BB) on agent readiness against Teable's 61 (C), and leads in 6 of 7 scored categories. ### Do NocoDB and Teable need an API key? Both take an API key or an OAuth sign-in. ### Can an agent call NocoDB and Teable without installing anything? Yes. NocoDB has a hosted endpoint at https://app.nocodb.com and Teable at https://app.teable.ai/api. ### Are NocoDB and Teable open source? No open-source release is listed for NocoDB. Teable is open source (AGPL-3.0 with additional brand terms for the backend and web app, MIT for the packages directory. Enterprise functions and the `@teable/cli` package (ISC on npm) are built in a private repository). ## For agents - This comparison as JSON: https://www.anchorterminal.com/compare/nocodb-vs-teable.json, and with the fewest tokens: https://www.anchorterminal.com/compare/nocodb-vs-teable.min.md - Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {"a": "nocodb", "b": "teable"}`. From a terminal: `anchor compare nocodb teable` - Each listing in full: https://www.anchorterminal.com/api/v1/tools/nocodb.json and https://www.anchorterminal.com/api/v1/tools/teable.json ## Other comparisons with NocoDB or Teable - [Coda (Superhuman Docs) vs NocoDB](https://www.anchorterminal.com/compare/coda-vs-nocodb.md) - [Coda (Superhuman Docs) vs Teable](https://www.anchorterminal.com/compare/coda-vs-teable.md) - [Google Sheets API vs NocoDB](https://www.anchorterminal.com/compare/google-sheets-api-vs-nocodb.md) - [Google Sheets API vs Teable](https://www.anchorterminal.com/compare/google-sheets-api-vs-teable.md) - [Microsoft Excel (Microsoft Graph workbook API) vs NocoDB](https://www.anchorterminal.com/compare/microsoft-excel-graph-vs-nocodb.md) - [Microsoft Excel (Microsoft Graph workbook API) vs Teable](https://www.anchorterminal.com/compare/microsoft-excel-graph-vs-teable.md) - [Smartsheet API + MCP vs Teable](https://www.anchorterminal.com/compare/smartsheet-vs-teable.md) - [Airtable vs NocoDB](https://www.anchorterminal.com/compare/airtable-vs-nocodb.md) - [Airtable vs Teable](https://www.anchorterminal.com/compare/airtable-vs-teable.md) - [Baserow vs NocoDB](https://www.anchorterminal.com/compare/baserow-vs-nocodb.md) - [Baserow vs Teable](https://www.anchorterminal.com/compare/baserow-vs-teable.md) - [Grist vs NocoDB](https://www.anchorterminal.com/compare/grist-vs-nocodb.md) - [Grist vs Teable](https://www.anchorterminal.com/compare/grist-vs-teable.md) - [NocoDB vs SeaTable](https://www.anchorterminal.com/compare/nocodb-vs-seatable.md) - [NocoDB vs Smartsheet API + MCP](https://www.anchorterminal.com/compare/nocodb-vs-smartsheet.md) - [SeaTable vs Teable](https://www.anchorterminal.com/compare/seatable-vs-teable.md)