Airtable through Squiid

What Airtable is

Airtable is a database with a spreadsheet interface. Bases hold tables with typed fields including attachments, links between tables, formulas and rollups, and views filter and group the same data differently for different people. Its API reads and writes records, and automations and interfaces let non-developers build workflows on top without involving engineering. Personal access tokens replaced the old API keys and are scoped per base, which is closer to what a connection should grant.

For AI-coded products Airtable is usually the system of record that already exists. An operations team keeps inventory, clients, content or applications in a base, and the product needs to read from or write to it: importing rows into the app, writing enriched data back, or letting a model summarise records nightly. Replacing it is usually a worse idea than connecting to it, because the people maintaining it are not going to switch to a database table. Scripts and automations in Airtable can also call your endpoints, so the integration can run in either direction.

Why connect it through Squiid

Airtable is on the Squiid roadmap as a connect service. When it is available, you will link the workspace you already have and grant access to specific bases, and Squiid will issue scoped access through https://api.squiid.io/v1/airtable/... with Authorization: Bearer $SQUIID_API_KEY, with clients working by base URL swap (gateway convention). Your Airtable plan stays billed by Airtable at the provider's listed price, and the connection is revocable without disturbing anyone's workflow. Field types are strict, so writing a value the column does not accept fails loudly rather than silently corrupting a record.

• One account, one key, one bill, one dashboard. Airtable sits beside every other service your project uses, on the same invoice and the same credit balance.
• Key custody. Squiid holds the Airtable credentials. Your code carries SQUIID_API_KEY, so AIRTABLE_API_KEY, AIRTABLE_BASE_ID, AIRTABLE_TABLE_NAME never land in a repository, a preview deployment or an agent’s context.
• Metering you can see. Every call is counted per service and per day, so you know what Airtable costs before the month ends.
• Pause on zero. When prepaid credits run out the gateway stops authorizing usage instead of running up a bill you did not fund.
• One rotation. Rotating the Squiid key cuts off every agent, worker and deployment at once, with no provider key to hunt down.

What you get

• Your existing Airtable workspace connected, not replaced
• Record read and write access per base
• Attachments, linked records and views
• Scoped, revocable access for agents
• Airtable seats stay billed by Airtable

How to connect Airtable

One variable replaces the provider credentials this service would normally need. Requests go to the gateway and the official SDKs work by pointing their base URL at it (gateway convention).

# .env
# replaces AIRTABLE_API_KEY, AIRTABLE_BASE_ID, AIRTABLE_TABLE_NAME
SQUIID_API_KEY=sq_live_xxxxxxxxxxxxxxxxxxxxxxxx

# every request: https://api.squiid.io/v1/airtable/...
# header:       Authorization: Bearer $SQUIID_API_KEY

Pricing through Squiid

Airtable bills your workspace plan directly at the provider's listed price, with no Squiid margin. Squiid passes that through at par: one dollar of prepaid credit is one dollar of Airtable usage, with no markup and no per-request margin.

Airtable has no subscription attached on Squiid today. If a plan is required for a feature you need, it passes through at the provider’s listed price with no Squiid fee.

Squiid adds no markup to provider prices. There is a free plan at $0 a month with a 15% fee when you top up credits, Solo at $19.97 a month with a top-up fee that starts at 8% and falls to 3.5% as your spend grows, Team from $29.97 a seat a month with the same ladder one point lower, and Custom with a rate of 3% or less. Credits are prepaid, so Airtable usage stops when the balance reaches zero rather than producing an invoice you did not fund. Auto top-up with a cap keeps production running without handing anyone an open-ended card.

If you leave

Your own account: the Airtable account was always yours and Squiid only holds an authorised connection, so revoking it leaves nothing behind. Squiid never owns your code, your schema or your domain, and the gateway speaks Airtable's own API, so the client change is a base URL. The handover page lists what happens for every provider in the catalogue.

Works with every coding agent

Airtable through Squiid is just an HTTP call with a bearer token, so every agentic coding tool can use it with the single key already in your environment:

• Claude Code
• Cursor
• ChatGPT
• Codex
• Grok
• Gemini CLI
• GitHub Copilot
• Windsurf
• Perplexity
• Devin
• Replit
• v0
• Lovable
• Cline

Vibe coding a feature on Airtable usually means asking for it in plain language and letting the agent write the integration. Because the key is Squiid’s rather than the provider’s, it can do that without ever holding a credential that could be leaked, logged or committed.