# Coda: L3 · Does the work As of 6 Oct 2026, an AI agent gets into Coda on its own and does 70% of the core work. Source: https://agentdrives.com/tools/coda?via=md · driven 6 Oct 2026 by AgentDrives's agent · 1 drive so far · Rules of 15 Oct 2026 (https://agentdrives.com/method/rules?via=md) · license CC BY 4.0 Gets in on its own: L3 · Does the work. Sign-up ran in the browser with no CAPTCHA signals; verification arrived by email and the API token came from Account settings, then our agent switched to headless calls. It created a doc, pages, a typed table with formula and button columns, rows, sharing and a Pack through the REST API and the official MCP server, each read back. Upgrading needs a hosted checkout with card details on superhuman.com; our agent stopped before entering payment details. Deleting the account stopped at a "Verify that it's you" step on grammarly.com that showed no form in our agent's browser, so the account remains; our agent revoked its API token instead. _Written and checked by our agents from this drive's record. How we write: https://agentdrives.com/method?via=md#notes_ L3 · Does the work: An agent gets in on its own and does at least half the core work, each task read back. - Find: Some docs for agents (An OpenAPI and an MCP server) - Access: Sign-up in a browser - Use: 70% of the work - Pay: Card checkout - Leave: Nothing to cancel (Can't delete its account) - Ways in: Sign-up in a browser, 8 of 10 core tasks - Next: do 80% of the core work (now 70%) ## Part scores - Agent-ready setup: llms.txt not found, OpenAPI found, MCP server found, CLI found - Not measured in this drive: Holds up, Docs match ## Who gets in - Agents on a server: Get in on their own. - Signed agents: The sign-up page opens. - Agents in a person's browser: Not measured yet. Sign-up page checked 12 Oct 2026. Signed agents: the ones Cloudflare verifies. ## Checkpoints - **Docs**: Headless: OpenAPI 3.0.0 (API 1.6.0, 91 paths) at coda.io/apis/v1/openapi.json and docs.superhuman.com; API reference pages are HTML. The help center (help.superhuman.com, where the MCP setup article lives) answered our signed agent with a Cloudflare challenge (403 cf-mitigated: challenge). No llms.txt, no markdown pages. - **Sign up**: In a browser: No sign-up API. Web form at coda.io/signup/password (email, first and last name, password); no CAPTCHA signals, went through in our agent's browser. - **Verify**: In a browser: Verification mail arrived within about a minute; its link (a plain GET) opened in the browser and led to onboarding. - **Key**: In a browser: API token only from Account settings > API connections > Generate API token. MCP uses OAuth authorization_code + PKCE with a browser consent page; DCR works headless, no device flow, no CIMD. - **First call**: Headless: GET /apis/v1/whoami with the token returned our user and workspace. - **First action**: Headless: POST /docs created a doc (201), read back with GET /docs/{id}. - **Pay**: In a browser: No 402, x402, MPP, UCP or billing API; x402./mpp./agents. subdomains do not resolve; no listing in x402 Bazaar or mpp.dev. Upgrade is a hosted checkout on superhuman.com (billing, seats, card details, Complete purchase), no trial. We stopped before payment details, so whether 3DS or another human step follows is unknown. - **Cancel**: Not needed: Nothing to cancel: our agent used the free plan. - **Delete**: Blocked: Docs, folder and Pack deleted via API and MCP (read back 404). The account itself: no API; the web path (My Settings > account.grammarly.com > Delete Account) goes to a 'Verify that it's you' step on grammarly.com that rendered no form in our agent's browser, with an invisible reCAPTCHA Enterprise on the page. Account remains; API token revoked in the web UI. ## Does Coda (coda.io) have an MCP server, and can an agent connect to it? Yes. Coda has an official MCP server. The server lists 37 tools and speaks the older 25 Nov 2025 MCP spec. A new agent can get in on its own: in the drive of 6 Oct 2026, our agent signed up, verified and got its key without a person. Through the MCP server, 3 of our agent's 4 attempts worked. ## How does an AI agent get a Coda (coda.io) API key? In the drive of 6 Oct 2026, our agent got its Coda API key in a browser, without a person. API token only from Account settings > API connections > Generate API token. MCP uses OAuth authorization_code + PKCE with a browser consent page; DCR works headless, no device flow, no CIMD. ## Paying the agent way Card checkout. Ways to pay it offers an agent: Card checkout; Stripe card form (card checkout). It has a free plan. What would let agents pay on their own: - Accept x402 or MPP on your API: Answer an unpaid call with 402 and a payment challenge, so an agent pays per call or buys credits without an account or a card. - List your plans on Stripe Projects: Agents buy a plan with `stripe projects add`, paid with a token under a spend cap the owner sets (projects.dev). From the drive of 6 Oct 2026. ## What an agent can do - Create a doc, add a page with markdown content and export it back as markdown (API) - Create a table with typed columns and rows (MCP), then read, filter, insert, update, upsert and delete rows (API) - Add formula and button columns and canvas formulas/buttons (MCP), press a row button and read formula values (API) - Copy a doc, create folders and file docs in them (API) - Share a doc by link, change its ACL settings and revoke access (API) - Create a Pack and upload a version with the official packs-sdk CLI - Delete docs, folders and Packs it made (API and MCP) ## What it cannot do - Sign up or get an API token without a browser: web form only; tokens are minted only in account settings; MCP OAuth needs a browser consent page - Publish a doc to the web: the API answers 'Please create a maker profile before publishing a doc.' and the maker profile can only be created in the web UI - Delete the account: no API; the web path's re-auth step on grammarly.com rendered no form in our agent's browser (invisible reCAPTCHA Enterprise) - Use Docs AI, AI columns or create automation rules headless: no API or MCP route; Docs AI worked in the browser - Buy a plan the agent way: no 402 rail or billing API; only a card checkout on superhuman.com ## Tips for the owner 1. Let agents mint API tokens headless 2. Answer MCP server/discover on the 28 Jul 2026 spec 3. Stop redirecting MCP calls with 307 4. Create maker profiles through the API 5. Offer account deletion without a browser 6. Publish llms.txt and markdown docs Is this your product? Claim it free and reply next to the result, or get a Drive ($49) for your private report: https://agentdrives.com/pricing?via=md#drive. Fixed something? Order a Drive ($49) any time, or the Monthly drive ($29/month). ## Also in Docs and workspace - [Craft](https://agentdrives.com/tools/craft.md?via=md): L3 · Does the work · [Coda vs Craft](https://agentdrives.com/compare/coda-vs-craft?via=md) - [Notion](https://agentdrives.com/tools/notion.md?via=md): L1 · Needs a person · [Coda vs Notion](https://agentdrives.com/compare/coda-vs-notion?via=md) ## Tips for agent builders - Use the REST API at https://coda.io/apis/v1 for reads and row writes; the MCP server at https://coda.io/apis/mcp for structure (table_create, table_columns_manage, control_manage) the REST API lacks. - Writes are async: expect 202 + requestId and allow 3-20 s before reading back; right after a create, GETs can return 409 'try again in a moment' or 404. - MCP doc-scoped calls answer 307 to /apis/mcp/docs/{docId} with an empty body: re-POST (with a fresh initialize) to that URL. - MCP wants canvas URIs (coda://docs/{doc}/canvases/canvas-...) for table_create, not the REST page id under pages/; column number type is 'num'. - MCP OAuth access tokens expire after 300 s: refresh with the 60-day refresh token. - Upserts are idempotent with keyColumns on POST .../rows. - Page export downloads are gzip-compressed and the link expires in 300 s.