Definition
In depth
An agent API key is a credential issued for automation, not for a person clicking Console. LUNO scopes keys so a loop that should only edit entries cannot drop schemas, and a setup loop can be revoked without rotating every human password.
Prefer a full key for day-to-day agent work — model, fill, publish. Use content-only when the agent is filling records and should not reshape the control plane. Treat schema access as a deliberate grant, not the default for every chat.
Setup confirms in the browser. The MCP CLI opens a page so you see which site and which scope you are connecting. Do not paste a key into chat, into a ticket, or into a README. If the loop changes machines, revoke and issue again.
Scoped keys are part of production governance. Humans still approve what ships. Agents still move fast. The key is the boundary between those two speeds. Audit should show the same trail whether the write came from Console or MCP.
Agent keys are available on Standard and above. Evaluate the rest of the platform on Free, then turn on scoped automation when the loop is real. See the pricing matrix for the current plan gate.
More
More terms
- MCP for CMS / backend ops →
Model Context Protocol servers that let coding agents operate schema, entries, and publish against a real backend.
- Production governance →
Humans keep control of what ships while agents build and operate — scoped keys, approval bounds, one audit trail.
- Seat tax (CMS pricing) →
Pricing that meters human editor seats — poorly aligned when agents and APIs are first-class operators.
- AI-era Backend Platform →
- Never build backends again →
- Backend platform for apps and agents →
- Hosted Backend Platform →
See it in the product
Check Capabilities and Developers to see definitions become implementation.