Agents as colleagues, not loose API keys
Give an agent a name, its own token and the bases it may use. Everything it changes is credited to it, and in review mode its changes wait beside the table until a person accepts them.
In Airtable: AI agents and API tokens
Its own identity
A name, a token shown once, and read or change access per base. Table rules and record rules apply to it as to a person.
Review before writing
Each change shows the record, the field, the old and new value and the agent's reason. Accept or reject one, or a batch.
Safe by construction
An accepted change is written only if the cell still holds what the agent saw; otherwise nothing is overwritten.
Undo an agent
Take back everything one agent wrote in the last day, keeping any cell a person changed after it.
How it is doing
Changes it made this week, and the share of its proposals people accepted.
One token everywhere
The data API, the Airtable-compatible API and the AI connector all take the agent's token.
Start with a base you already have
Bring it from Airtable with every record, link and formula, checked against Airtable. Free, and Airtable stays as it is.