Airtable: the 360 agent-readiness check

Airtable scores 57 of 100 on Ora's agent-readiness scan, a C, read 9 November 2026. Of the five surfaces an agent acts on, Ora found 1: a command line. One verified MCP endpoint, and an API that answers nothing without a key.

On 9 November 2026 the public site at airtable.com scored 57 of 100 on Ora's agent-readiness scan, a C, in Ora's Productivity category. Ora probes a site the way an agent would: it requests pages with the agents' own user agents, reads robots.txt, looks for the files agents read, and tries the API, MCP and payment surfaces. This check reads the act layer first, because that is what the directory records, then the door, what an agent can read, and whether the company is found and recommended. Ora's one-line summary: Airtable provides official SDK packages and MCP registry listings, but lacks a published OpenAPI specification.

The score

What an agent can do

The surfaces an agent acts on: an API it can find and call, an MCP server, an agent card, OAuth metadata, a command line. This is the layer the directory records, so it comes first. 2 checks in this group do not apply to this site and are left out.

In the directory, Airtable sign-in required, tools not seen, not counted; the connector run of 4 November 2026 is on the entry page. Ora's MCP server check for the same domain reads partial; the two look for different things, the directory for a server that answers a handshake and lists tools, Ora for a server it can find from the site.

At the door

What the site answers when a request arrives with an agent's user agent, and what robots.txt says to agents.

What an agent can read

Whether the text is in the first response, what the site publishes for agents, and how it describes itself to them. One check in this group does not apply to this site and is left out.

Found and recommended

Whether an assistant can find the company by name, confirm what it is, and see it in the registries agents read.

Payments

The agent payment protocols Ora probes for. A site that sells nothing has nothing here, and Ora scores the layer out of zero when none applies. None of the 6 payment checks applied to airtable.com.

The fixes worth most points

Ora attaches an estimate to each failing or partial check: how many points the site would gain by passing it. These are the 5 with the largest estimates for Airtable, with what Ora observed. The wording of each fix is Ora's; the 28 checks it runs on an MCP server are listed with their layer and tier.

• Public API with reachable endpoints: fail, 0 of 7, about 5.2 points to gain. Ora saw: No publicly reachable API surface detected (REST and GraphQL both absent or auth-gated)
• OpenAPI spec published: fail, 0 of 7, about 4 points to gain. Ora saw: No OpenAPI/Swagger specification found
• OAuth 2.0 support: fail, 0 of 5, about 3.7 points to gain. Ora saw: No OAuth 2.0 or OpenID Connect support detected
• Scoped permissions: fail, 0 of 5, about 3.7 points to gain. Ora saw: No declared OAuth scopes, security schemes, or scoped-permission documentation found
• WebMCP support: fail, 0 of 5, about 3.7 points to gain. Ora saw: No WebMCP support detected - no document.modelContext / navigator.modelContext usage found (scanned 34 of 34 same-origin script bundle(s) for modelContext registrations)

Our read

Airtable's MCP server answers at mcp.airtable.com/mcp and requires authentication, and that is the one act-layer surface Ora could verify. The public API check scored 0 of 7 because neither REST nor GraphQL was reachable without a key, the OAuth check found no OAuth 2.0 or OpenID Connect discovery, there is no OpenAPI specification and no declared scopes, and the only SDK is on npm. The developer documentation exists at airtable.com/developers and @airtable/blocks-cli is on npm, so the pieces an agent would use are there and the files that would let it find them are not. The reading side is thinner than most: no llms.txt at either location, no JSON-LD on the home page, a brand search that places the domain eighth, though the door is open and five of five sampled pages read. For a database product that every automation tool connects to, the act layer reads as private by default.

Test your own surfaces

The scan above is free and needs no account: enter a domain at ora.ai and read the same four layers for your own site. For an MCP server, Ora scans the server URL itself and runs 28 of its 132 public checks on it, which is why it is the check this directory recommends; the reasons, the limits and the alternatives are on their own page. The command below runs the same audit from a terminal and exits with 1 under the score you set, so it can gate a deploy.

npx ax@0.10 audit https://example.com --min-score 70

All 360 checks, one company a day. Corrections to the corrections page.