Coda vs Craft for AI agents
As of 6 Oct 2026, both reach L3 · Does the work. Our agent got further with Craft: with Craft it got in on its own and did 78% of the work, with Coda it got in and met its first wall at delete (blocked).
- 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.
Got in; first wall at delete (blocked). Next: do 80% of the core work (now 70%)
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.
Driven 6 Oct 2026 · The drive and its evidence- Find: Docs for agents: llms.txt, an OpenAPI and an MCP server.
- Access: Sign-up in a browser.
- Use: 78% of the work.
- Pay: Reaches the checkout: Stopped at the card form.
- Leave: Leaves on its own: Nothing to cancel, deletes its account.
In on its own; 78% of the work done. Next: do 80% of the core work (now 78%)
Gets in on its own and does the work: L3 · Does the work. Our agent passed every checkpoint it tried headless, with no step blocking it outright. Sign-up used an email-code web form behind an invisible challenge that let it through, and credentials needed one browser approval for MCP; from there it created a document through the API and read it back. Through the API it drove documents, folders, tasks, daily notes, collections and whiteboards, with publishing, sharing and the Assistant reachable only in the browser. Upgrading opens a hosted card form a human has to complete, and deleting the account is a browser-only step with no matching API route, though it fully revoked the agent's access afterward.
Gets furtherDriven 6 Oct 2026 · The drive and its evidenceThe two summaries: written and checked by our agents from each product's drive. How we write.
Where each one stops.
CodaGot in; first wall at delete (blocked)
CraftIn on its own; 78% of the work done
| Checkpoint | Coda | Craft |
|---|---|---|
| Docs | Headless | Headless |
| Sign up | In a browser | In a browser |
| Verify | In a browser | In a browser |
| Key | In a browser | In a browser |
| First call | Headless | Headless |
| First action | Headless | Headless |
| Pay | In a browser | In a browser |
| Cancel | Not needed | Not needed |
| Delete | Blocked | In a browser |
Headless or in a browser.
How our agent passed each checkpoint, and what each product offers an agent.
Checkpoints by route, API, MCP, CLI and SDK
| Coda | Craft | |
|---|---|---|
| Headless (checkpoints) | 3 | 3 |
| In a browser (checkpoints) | 4 | 5 |
| Needs a human (checkpoints) | 0 | 0 |
| Blocked (checkpoints) | 1 | 0 |
| Not tested (checkpoints) | 0 | 0 |
| Work done | 70% of the core | 78% of the core |
| API | Yes | Yes |
| OpenAPI | Yes | Yes |
| MCP server | Yes (official) | Yes (official) |
| CLI | Yes | No |
| SDK | Yes | No |
| llms.txt | No | Yes |
Bot checks, and where a person was needed.
| Coda | Craft | |
|---|---|---|
| Bot check | Account deletion stuck behind invisible reCAPTCHA re-auth; it got in another way | reCAPTCHA (invisible) let it through at sign up |
| Wall type | A challenge on the form | No bot-check wall |
| First wall | Got in; first wall at delete (blocked) | None |
| A person helped | No | No |
A challenge on the form: It asks every visitor to prove they are human. It stops every agent on any network, and a signature doesn't help: a person does this step, or the owner opens it for agents. Where we drive from.
Level and part scores.
| Coda | Craft | |
|---|---|---|
| Level | L3 · Does the work | L3 · Does the work |
| Agent-ready setup | 80 of 100, fair | 90 of 100, good |
| Standards | MCP spec of 25 Nov 2025 (1 version behind) · MCP client registration (behind) · OpenAPI 3.0.0 (2 versions behind) | MCP spec of 25 Nov 2025 (1 version behind) · MCP discovery (behind) · MCP client registration (behind) · OpenAPI 3.1.1 (1 version behind) |
| Security | No review in this drive | Reported privately to the owner |
Holds up: not measured in these drives. Docs match is measured in an Audit. What the scores mean.
Pay, cancel and delete.
| Coda | Craft | |
|---|---|---|
| Pay | Card checkout | Reaches the checkout |
| Free plan or trial | Free plan | Free plan |
| Cancel | Not needed | Not needed |
| Delete the account | Blocked | In a browser |
How each one takes payment
- Coda: Card checkout.
- Craft: Reaches the checkout: stopped at the card form.
Coda vs Craft: the short answers.
Which can an AI agent use, Coda or Craft?
Both reach L3 · Does the work. Our agent got further with Craft: with Craft it got in on its own and did 78% of the work, with Coda it got in and met its first wall at delete (blocked). Both driven 6 Oct 2026.
Can an AI agent sign up for Coda and Craft on its own?
Coda: yes, in a browser. Craft: yes, in a browser.
Do Coda and Craft have an MCP server?
Coda: yes (official). Craft: yes (official).
Can an AI agent delete its Coda or Craft account?
Coda: blocked. Craft: yes, in a browser.
The drives and the category.
Put your own shortlist side by side.
A Stack check drives the tools you're choosing between and shows which ones your agents can use. $490 for three tools, ready in 24 hours.