# Baserow > Baserow is an open-source database of typed rows in tables, sold as a hosted cloud and as software to self-host. Agents reach it through a REST API with database tokens and a built-in MCP server. - Canonical: https://www.anchorterminal.com/tools/baserow - Markdown: https://www.anchorterminal.com/tools/baserow.md (~7,700 tokens) - Slim: https://www.anchorterminal.com/tools/baserow.min.md (~1,830 tokens, same facts, less prose, for token-sensitive contexts) - JSON: https://www.anchorterminal.com/tools/baserow.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 ## Overview **Grade B · 63.6/100 · rank #306 of 722 · #7 in Spreadsheets & operational tables · not agent-ready · confidence medium** ## Assessment Database tokens are limited to chosen tables and to create, read, update or delete, and the REST API has a public OpenAPI description with batch calls of 200 rows. The MCP server authenticates with a key in its URL, runs over SSE only and has no read-only mode. Cloud requests are capped at 10 at a time. ## Facts | Field | Value | | --- | --- | | Vendor | Baserow B.V. (https://baserow.io) | | Kind | HTTP API | | Category | Spreadsheets & operational tables (https://www.anchorterminal.com/categories/spreadsheets) | | Transport | HTTP, SSE (legacy) | | Endpoint | `https://api.baserow.io` | | Auth | API key · Self-serve. A signed-in user creates a database token in the workspace settings, choosing the tables it can reach and whether it may create, read, update or delete rows. Tokens don't expire and can be regenerated or deleted. They cover rows only, so changing tables or fields needs a JWT from `/api/user/token-auth/` with the account's email and password, which carries the user's full access. The MCP server has no token header or OAuth. Each endpoint is a URL holding a 32-character key that carries the creating user's access across one workspace, and deleting the endpoint revokes it. On Enterprise licences only workspace admins and builders can create database tokens. | | Pricing | Freemium ($10 / seat-mo) · Free cloud plan with 3,000 rows and 2 GB of storage per workspace, so an agent can start without a contract. Premium is $10 a user a month billed yearly ($12 monthly) and Advanced $18 ($22 monthly), Enterprise through sales. API calls aren't priced, the MCP server is on every plan, and there's no separate sandbox. The self-hosted core is free with no row or request limits (checked 2026-10-08). | | x402 | No · No x402, MPP or L402 in the API docs, the OpenAPI description, the MCP docs or the pricing page (checked 2026-10-08). | | Licence | MIT for the core, including the REST API and the MCP server. Code under premium/ and enterprise/ is source-available under Baserow's own licences and needs a paid subscription in production. Docs are CC BY-SA 4.0 | | Tools exposed | 7 | | Source | https://github.com/baserow/baserow | | Docs | https://baserow.io/user-docs/database-api | | llms.txt | https://baserow.io/llms.txt | | Last release | 2026-09-29 | | GitHub stars | 6,098 (as of 2026-10-08) | | Surfaces graded | Baserow Cloud's REST API at https://api.baserow.io and the built-in MCP server at https://api.baserow.io/mcp//sse. The same code can be self-hosted | | Free tier | Free cloud plan with 3,000 rows and 2 GB of storage per workspace, and the MCP server included. Self-hosted core is free with no row limit | | Rate limits | 10 concurrent API requests on Baserow Cloud under a fair-use policy, no limit when self-hosted (vendor's figures) | | Batch size | Up to 200 rows per batch create, update or delete, and 200 rows per list page (default 100) | | Auth and scopes | Database token (`Authorization: Token`), permanent, one workspace, chosen tables, with create, read, update and delete set separately. JWT (`Authorization: JWT`) from email and password for everything else. MCP by a key in the endpoint URL | | Read and write | With a database token, rows (list, get, create, update, move, delete, batch), field list, table list and file upload. With a JWT, tables, fields, views, webhooks, snapshots and the rest of the 424 operations | | Filtering | `filters` (a JSON filter tree), `filter__{field}__{filter}`, `filter_type`, `search`, `order_by`, `include`, `exclude`, `view_id`, `page` and `size` on list rows | | MCP server | Built in, SSE transport, 7 tools (list_databases, list_tables, get_table_schema, list_table_rows, create_rows, update_rows, delete_rows). Seven more tools for tables and fields are in the source but switched off | | Change events | Webhooks per table for rows, fields and views created, updated or deleted, with conditional row updates and row-enters-view events. Cloud holds at most 5,000 pending calls per webhook | | Plan gates | Role-based permissions and audit logs from Advanced. Row change history kept 14 days on Free, 90 on Premium, 180 on Advanced and Enterprise | | SDKs | No official client library found. The `baserow` package on PyPI is by a third party and dates from 2022 | | Deprecations | A deprecations page that lists only PostgreSQL versions. Breaking API changes are listed in each release's changelog | | Certifications | The FAQ says SOC 2 Type II, HIPAA and GDPR compliant (vendor's statement). No bug bounty or security.txt found | | SLA | None found. The terms describe a best-efforts service with no guarantee against interruptions | | Open source | Yes for the core under MIT, including the REST API and MCP server. The premium and enterprise directories carry their own paid licences | | Capabilities | sheets.records, sheets.read, sheets.write, sheets.tables, sheets.formulas | | Tags | official, hosted, self-hosted, open-source, mcp, free-tier, api-key, openapi, llms-txt, webhooks, status-page, soc2 | | JSON | https://www.anchorterminal.com/api/v1/tools/baserow.json | ## Score breakdown (methodology v0.4, October 2026 research run) Assessed 2026-10-08 from public evidence against the published checklist (https://www.anchorterminal.com/benchmark/#checklist). Confidence: medium. Performance and Task success pending (no score, not in the total); the total is Σ(score × weight) ÷ 80 over the 7 assessed categories. "This run" is each category's share of the 100 points. | Category | Weight | This run | Score (0–100) | Points | | --- | --- | --- | --- | --- | | Reliability | 16% | 20 | 65 | 13.0 | | Performance | 10% | pending | pending | n/a | | Schema & documentation | 13% | 16.2 | 77 | 12.5 | | Agent ergonomics | 13% | 16.2 | 72 | 11.7 | | Security & auth | 14% | 17.5 | 54 | 9.4 | | Payments & pricing | 10% | 12.5 | 40 | 5.0 | | Task success | 10% | pending | pending | n/a | | Maintenance & community | 7% | 8.8 | 72 | 6.3 | | Transparency & trust (editorial 49, provenance 80) | 7% | 8.8 | 65 | 5.7 | | Negative events | up to −15 | up to −15 | none recorded | 0 | | **Total** | | | | **63.6 → B** | ### Why each score - Reliability 65: Graded on Baserow Cloud's REST API and built-in MCP server, with the hosted lines. Better Stack status page at status.baserow.org with five components and 90 days of history (20). Backend API at 99.981 per cent over 90 days, with 6 minutes down on 1 October 2026, degraded real-time and MCP performance on 8 September and an error on public views on 23 September, all minor (20). The only published limit is 10 concurrent requests under a fair-use policy, with no per-second or per-day figure (10 of 15). The docs ask for retries with exponential backoff, but no Retry-After header or idempotency key is documented and the OpenAPI description has no 429 response for row calls (5 of 15). No SLA found, and the terms describe a best-efforts service (0). The REST API is generally available and the MCP docs carry no beta label (10). - Performance: Pending. Latency is measured per call by our probes, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until the first probe window closes. - Schema & documentation 77: Public OpenAPI 3.0.3 description with 312 paths and 424 operations, and every MCP tool has a JSON Schema generated from a typed model (25). llms.txt exists but links to HTML marketing and docs pages, with no Markdown docs found (5 of 10). Endpoint descriptions are long and specific, and MCP tool descriptions say which tool to call first (15 of 20). Parameters are typed, but `filters` is a JSON string, row bodies depend on the table, and MCP rows are untyped objects keyed by field name (8 of 15). Curl examples in the docs and an enum of error codes on each response, 260 distinct codes in all (12 of 15). The description carries the release version and the changelog has Breaking API changes sections, with no API version in the path (12 of 15). - Agent ergonomics 72: The MCP server has 7 compact tools (25). List rows pages by `page` and `size` up to 200, with `filters`, `search`, `order_by`, `include`, `exclude` and `view_id` (20). Errors return a machine-readable code and a detail, such as ERROR_NO_PERMISSION_TO_TABLE (16 of 20). No idempotency keys or upsert on the row endpoints were found, and the MCP tools are built without readOnlyHint or destructiveHint annotations. Batch calls of 200 rows reduce the number of writes to retry (5 of 20). Few required parameters, but no official client library in any language was found (6 of 15). - Security & auth 54: Database tokens are limited to one workspace, chosen tables and create, read, update or delete, and can be regenerated or deleted, which would earn 30. The MCP endpoint instead holds its key in the URL path with the user's full workspace access, and schema changes over REST need a JWT from the account's email and password. We took 10 off for the secret in the URL, a judgement call because the checklist names the query string (20). Read-only tokens per table on REST. MCP has no read-only mode or approval step, though its table and field tools are switched off (12 of 20). Rows can hold text written by others, and the only guidance found is to verify bulk updates and deletions (3 of 15). Audit logs start at the Advanced plan, row history is kept 14 to 180 days, and the docs say token usage isn't logged in detail (8 of 15). SECURITY.md gives a reporting email, and the FAQ claims SOC 2 Type II and HIPAA. No security.txt, bug bounty or published advisory found (11 of 20). - Payments & pricing 40: Graded on the hosted cloud. No x402, MPP or L402 found (0). Plan prices are public, Premium at $10 and Advanced at $18 a user a month billed yearly, with no per-call price (10). A Free plan with 3,000 rows per workspace. The FAQ mentions cards only for subscriptions, and we didn't complete a signup (20). The repository docs show account creation by POST to `/api/user/` and a JWT from `/api/user/token-auth/` with no browser, but the software supports a captcha on signup and we didn't test whether Baserow Cloud enforces it, so half credit as a judgement call (10 of 20). - Task success: Pending. Task success needs the category task suites run through each tool, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until then. A data provider's data-quality score is published on its listing now and becomes half of this category when it's scored. - Maintenance & community 72: Release 2.4.0 on 29 September 2026, 9 days before the check (30). Four releases in the last 90 days, 2.3.2, 2.3.3, 2.3.4 and 2.4.0 (20). The community forum shows staff replies within a day or two on recent threads. The GitHub issues page counted 1,199 open issues, and we didn't read reply times there (15 of 25). No official client library, and the only Baserow entry in the official MCP registry is a third party's (0 of 15). The repository has CI and daily backend test workflows and the changelog records dependency upgrades for security fixes. We didn't read the current CI result (7 of 10). - Transparency & trust 65: The core, including the REST API and MCP server, is MIT. Code under premium/ and enterprise/ is source-available under Baserow's own licences (27 of 30). The privacy policy is written for website visitors, carries no date and names no retention periods. The terms incorporate a DPA that we couldn't find in public, and the FAQ places servers in Germany in one answer and data in Amsterdam in another (8 of 30). A deprecations page exists but lists only PostgreSQL versions. Breaking API changes are listed in the changelog at release, as with the endpoint removed in 2.4.0, and the terms end support for a previous version after three months (8 of 20). Hosting in Germany is stated, with the inconsistency above, and no sub-processor list was found (6 of 20). Fix list for a coding agent, everything this grade says the listing lacks, the biggest gain first (21 items): https://www.anchorterminal.com/fixes/baserow.md (JSON https://www.anchorterminal.com/fixes/baserow.json) ### What we couldn't check - unchecked: whether signup on Baserow Cloud asks for a card, an email confirmation or a captcha. We didn't create an account, and the half credit for onboarding without a browser rests on the repository's API docs - unchecked: the MCP server's live tool list on Baserow Cloud. The 7 tools come from the docs page and from the source at commit 0af9be4, which may be ahead of the cloud - unchecked: reply times on GitHub issues and the current CI result. The GitHub API refused us, and the count of 1,199 open issues is read from the issues page - unchecked: a SOC 2 report or HIPAA attestation. The FAQ states them and no report or auditor was named on the pages read - No SLA, security.txt, bug bounty, sub-processor list, public DPA text, retention period, Retry-After header, idempotency key or official client library was found in the reviewed pages - The privacy policy is written for website visitors and has no date. It's recorded in provenance because it is the only one and covers account registration - The FAQ says servers are in Germany and also that all user data is stored in Amsterdam, Netherlands - Release 2.4.0 removed `/api/workspaces/{id}/settings/generative-ai/` with notice only in that release's changelog. No deduction was taken because the endpoint is outside the row API and MCP server graded here - The MCP key travels in the URL path, not the query string the checklist names. The 10-point deduction is a judgement call - The lead was right on vendor, URL and interface, with one correction. Tokens are limited per workspace and table, not per database ### Sources - MCP server docs: (seen 2026-10-08) - Claude MCP setup: (seen 2026-10-08) - database API docs: (seen 2026-10-08) - database tokens: (seen 2026-10-08) - OpenAPI description: (seen 2026-10-08) - llms.txt: (seen 2026-10-08) - pricing: (seen 2026-10-08) - FAQ (rate limit, hosting, certifications, payment): (seen 2026-10-08) - webhooks: (seen 2026-10-08) - audit log: (seen 2026-10-08) - row change history: (seen 2026-10-08) - trust centre: (seen 2026-10-08) - terms and conditions: (seen 2026-10-08) - privacy policy: (seen 2026-10-08) - status page: (seen 2026-10-08) - repository (cloned at commit 0af9be4, 8 October 2026): (seen 2026-10-08) - MCP tool definitions in source: (seen 2026-10-08) - changelog: (seen 2026-10-08) - release dates: (seen 2026-10-08) - licence: (seen 2026-10-08) - security policy: (seen 2026-10-08) - security advisories: (seen 2026-10-08) - API deprecations: (seen 2026-10-08) - backend API docs (account creation, JWT): (seen 2026-10-08) - configuration (captcha, PostHog): (seen 2026-10-08) - official MCP registry search: (seen 2026-10-08) - community forum, latest topics: (seen 2026-10-08) - forum thread on the SSE connector: (seen 2026-10-08) - PyPI package named baserow: (seen 2026-10-08) - security.txt (404): (seen 2026-10-08) - RDAP for baserow.io: (seen 2026-10-08) ## Who's behind it (provenance 80/100, checked 2026-10-08) | Check | Finding | Points | | --- | --- | --- | | Legal entity named | Baserow B.V. | 20/20 | | Domain age | baserow.io, registered 2019-01-19 (7 years) | 11/15 | | Endpoint on the vendor's domain | api.baserow.io | 15/15 | | Terms of service | read, states 3 of the 7 things a reader expects | 6.6/10 | | Privacy policy | read, states 5 of the 8 things a reader expects | 7.8/10 | | Status page | status.baserow.org | 10/10 | | Changelog | published | 10/10 | | security.txt | not found | 0/10 | The General Terms and Conditions name Baserow B.V., a Dutch private company with its registered office at Keurenplein 4, Amsterdam, trade register number 81129254. The page carries no date. The privacy policy is the only one found. It is written for visitors to baserow.io, mentions account registration, carries no date and names no retention periods. The terms incorporate a Data Processing Agreement by reference, and no public copy was found. The REST API and the MCP server answer at api.baserow.io, a baserow.io subdomain. The status page is on a separate domain, status.baserow.org, hosted by Better Stack. baserow.io/.well-known/security.txt and api.baserow.io/.well-known/security.txt return 404. SECURITY.md in the repository gives an email address for vulnerability reports. RDAP for baserow.io gives a registration date of 2019-01-19. ### Terms and privacy, as read A reading by a fixed set of rules, each answered with the vendor's own sentence. Not legal advice. **Terms of service** (https://baserow.io/terms-and-conditions), read 2026-10-08, gives no date, states 3 of the 7 things a reader expects. - Not found in the text. Gives the date it was last updated. - Names the governing law or courts. Disputes go to the courts of Amsterdam. - States a limit on its liability. Capped at the fees paid in the 12 months before the claim. - Not found in the text. Says how changes to the terms are announced. - Not found in the text. Lists what users may not do. - Not found in the text. Refers to a service level or uptime commitment. - Also in the text (2026-10-08). Baserow may use without restriction the designs, algorithms, documentation, works and other information it learns of during the agreement. "Baserow is entitled to use and/or exploit without any restriction, the parts, designs, algorithms, documentation, works, protocols, standards and other information that Baserow get knowledge of during the term of the agreement." - Also in the text (2026-10-08). Baserow states it is never obliged to recover corrupted or lost data. "Baserow is never obliged to recover corrupted or lost data." - Also in the text (2026-10-08). No fees are refunded if the client stops using a subscription before its end date. "No fees will be refunded if client stops using its subscription before the end date." **Privacy policy** (https://baserow.io/privacy-policy), read 2026-10-08, gives no date, states 5 of the 8 things a reader expects. - Not found in the text. Gives the date it was last updated. - Not found in the text. Says how long data is kept. - Says whether personal data is sold or shared for advertising. Says it does not sell personal data. - Not found in the text. Says where data is transferred or stored. - Also in the text (2026-10-08). The policy applies only to visitors to the Baserow website and not to information collected through other channels. "This policy is not applicable to any information collected offline or via channels other than this website." ## Live (updated 2026-10-08 19:52 UTC) - Right now: up, HTTP 404, 114 ms, checked 2026-10-08 19:52 UTC (get on `https://api.baserow.io`) - Uptime 24h 100.0% (27 probes) · 30 days 100.0% (27 probes) · p50 99 ms · p95 143 ms - Vendor status page: unknown, no machine-readable status found - Watching changelog - Watching privacy - Watching terms - Always current: https://www.anchorterminal.com/api/v1/live/baserow.json ## Probe metrics Not measured yet. Our benchmark probes haven't run, so there's no availability, latency or error rate from a run and Performance is pending. Live uptime, where we poll the endpoint, is under Live and doesn't change the score. ## Prices | Item | Price | Unit | Note | | --- | --- | --- | --- | | Premium (cloud) | $10 | per seat per month | billed yearly, $12 billed monthly, 50,000 rows per workspace | | Advanced (cloud) | $18 | per seat per month | billed yearly, $22 billed monthly, 250,000 rows per workspace | Across all listings: https://www.anchorterminal.com/prices/index.md ## Strengths - Database tokens are limited to one workspace, to chosen tables and to create, read, update or delete, and can be regenerated or deleted - Public OpenAPI 3.0.3 description at api.baserow.io/api/schema.json with 424 operations and an enum of error codes on each response - The MCP server exposes 7 tools with typed inputs, and its descriptions tell the caller to read the table schema before writing - List rows takes `include`, `exclude`, `size`, `filters`, `search`, `order_by` and `view_id`, so responses can be sized - The core, including the REST API and the MCP server, is MIT-licensed and can be self-hosted with no row or request limits ## Weaknesses - The MCP endpoint's key sits in the URL path, and the docs say it grants full access to modify data in the workspace - The MCP server speaks only the older SSE transport, with no OAuth, no read-only mode and no tool annotations - Table and field changes over REST need a JWT obtained with the account's email and password, since database tokens cover rows only - No SLA, security.txt, sub-processor list or published DPA text was found, and the privacy policy carries no date or retention periods - No official client library was found, and Baserow isn't in the official MCP registry under its own namespace ## Before you call it (notes for agents) 1. Create a database token with only the tables and operations needed. It can't change tables or fields, which need a JWT from `/api/user/token-auth/` 2. Send `Authorization: Token YOUR_DATABASE_TOKEN`, and add `user_field_names=true` or rows come back keyed as `field_123` 3. Use the `/batch/` endpoints for up to 200 rows a call, and keep to 10 requests in flight on Baserow Cloud 4. Treat the MCP URL as a password. Keep it out of logs and version control, and delete the endpoint to revoke it 5. Over MCP, call `get_table_schema` before `create_rows` or `update_rows`, and page `list_table_rows` with `page` and `size` ## Connect First request: ```bash curl \ -X GET \ -H "Authorization: Token YOUR_DATABASE_TOKEN" \ "https://api.baserow.io/api/database/fields/table/TABLE_ID/" ``` MCP client configuration: ```json { "mcpServers": { "Baserow MCP": { "url": "YOUR_MCP_URL_HERE" } } } ``` Through letme (picks today, calling later): https://letme.dev/baserow. letme answers with the pick and how to call it direct; calling through letme (one key, the vendor's own price) comes later. How it works: https://www.anchorterminal.com/letme/index.md ## Similar tools Ranked by shared capabilities, then score. Same-category tools with no shared capability key are listed last. | Tool | Grade | Score | Rank | Shared capabilities | x402 | Markdown | | --- | --- | --- | --- | --- | --- | --- | | NocoDB | BB | 75.7 | 37 | sheets.records, sheets.read, sheets.write, sheets.tables, sheets.formulas | no | https://www.anchorterminal.com/tools/nocodb.md | | Airtable | BB | 70.9 | 124 | sheets.records, sheets.read, sheets.write, sheets.tables, sheets.formulas | no | https://www.anchorterminal.com/tools/airtable.md | | SeaTable | B | 66.3 | 241 | sheets.records, sheets.read, sheets.write, sheets.tables, sheets.formulas | no | https://www.anchorterminal.com/tools/seatable.md | | Coda (Superhuman Docs) | B | 64.8 | 270 | sheets.read, sheets.write, sheets.tables, sheets.records, sheets.formulas | no | https://www.anchorterminal.com/tools/coda.md | | Teable | C | 61 | 379 | sheets.read, sheets.write, sheets.records, sheets.tables, sheets.formulas | no | https://www.anchorterminal.com/tools/teable.md | | Grist | D | 50.1 | 597 | sheets.records, sheets.read, sheets.write, sheets.tables, sheets.formulas | no | https://www.anchorterminal.com/tools/grist.md | ## Panel reviews (0) Reviewed by the Anchor panel (https://www.anchorterminal.com/reviewers/index.md): . Desk reviews, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made. For a desk review, the outcome says whether the reviewer's questions could be answered from public material: success, partial or failure. How reviews work: https://www.anchorterminal.com/reviews/how-it-works.md ## Notable - The MCP server is built into the product on every plan and lists 7 capabilities, create rows, delete rows, get table schema, list databases, list table rows, list tables and update rows (source: ) - Each MCP endpoint is a URL of the form https://api.baserow.io/mcp//sse, and the docs say to treat it as a password because it grants full access to modify workspace data (source: ) - Database tokens never expire, are limited to one workspace and to chosen tables, and carry create, read, update and delete permissions set separately (source: ) - Baserow Cloud allows 10 concurrent API requests under a fair-use policy, and the self-hosted version has no limit (source: ) - The OpenAPI description (version 2.4.0) has 312 paths and 424 operations, of which 17 accept a database token (source: ) - Release 2.4.0 is dated 29 September 2026, the fourth release in 90 days, and its changelog has a section headed Breaking API changes (source: ) - The status page shows 99.981 per cent uptime for the backend API over 90 days, with 6 minutes down on 1 October 2026 and degraded MCP performance on 8 September (source: ) - On 5 October 2026 a forum user reported that Claude flags the SSE connector as deprecated, and staff said the report went to the developers (source: ) ## Compare - [Baserow vs Google Sheets API](https://www.anchorterminal.com/compare/baserow-vs-google-sheets-api.md): B 63.6 vs BB 76.3 - [Baserow vs Microsoft Excel (Microsoft Graph workbook API)](https://www.anchorterminal.com/compare/baserow-vs-microsoft-excel-graph.md): B 63.6 vs C 58.5 - [Airtable vs Baserow](https://www.anchorterminal.com/compare/airtable-vs-baserow.md): BB 70.9 vs B 63.6 - [Baserow vs Coda (Superhuman Docs)](https://www.anchorterminal.com/compare/baserow-vs-coda.md): B 63.6 vs B 64.8 - [Baserow vs Grist](https://www.anchorterminal.com/compare/baserow-vs-grist.md): B 63.6 vs D 50.1 - [Baserow vs NocoDB](https://www.anchorterminal.com/compare/baserow-vs-nocodb.md): B 63.6 vs BB 75.7 - [Baserow vs SeaTable](https://www.anchorterminal.com/compare/baserow-vs-seatable.md): B 63.6 vs B 66.3 - [Baserow vs Smartsheet API + MCP](https://www.anchorterminal.com/compare/baserow-vs-smartsheet.md): B 63.6 vs B 67.6 - [Baserow vs Teable](https://www.anchorterminal.com/compare/baserow-vs-teable.md): B 63.6 vs C 61 ## Verify this listing For the vendor. The badge or a plain link to this page verifies the listing, from a page on baserow.io or one of its subdomains, or the README of github.com/baserow/baserow. It shows the listing is the vendor's and that the vendor knows it's here, and it never changes a grade, rank or review. The vendor sends the page's address to `POST https://www.anchorterminal.com/api/v1/verify` as `{"slug": "baserow", "url": "…"}`, or calls the `verify_listing` tool at https://www.anchorterminal.com/mcp. We fetch the page once, then again every week; two failed checks in a row and the verification lapses, and a later pass restores it. What we check: https://www.anchorterminal.com/builders/index.md#verify HTML badge: ```html Baserow on Anchor Terminal ``` Markdown badge, for a README: ```markdown [![Baserow on Anchor Terminal](https://www.anchorterminal.com/badges/baserow.svg)](https://www.anchorterminal.com/tools/baserow) ``` Plain link: ```html Baserow on Anchor Terminal ``` ## Share this listing For the vendor. Sharing assets for social media, two PNGs of 1200 × 630 that say Baserow is listed on Anchor Terminal, with the vendor's logo and this page's address and no grade or score. - Dark: https://www.anchorterminal.com/assets/share/baserow-dark.png - Light: https://www.anchorterminal.com/assets/share/baserow-light.png