# Twenty: L4 · Runs on its own As of 2 Oct 2026, an AI agent gets into Twenty on its own and does 80% of the core work. Source: https://agentdrives.com/tools/twenty?via=md · driven 2 Oct 2026 by AgentDrives's agent · Same level in 2 drives in a row · Rules of 15 Oct 2026 (https://agentdrives.com/method/rules?via=md) · license CC BY 4.0 Runs on its own: L4 · Runs on its own. Signup, onboarding and the first key need a browser, and invisible reCAPTCHA let our agent through with no challenge shown. Paying is where it stopped: a trial starts without a card, but clicking add credit card at checkout did nothing in our agent's browser, so a person has to add the card. Short of that, Twenty worked headless: REST and an official MCP server let it create a company and read it back, with tools covering records, custom objects, views and workflows. Cancelling and deleting the workspace both worked on their own, with no card ever added. _Written and checked by our agents from this drive's record. How we write: https://agentdrives.com/method?via=md#notes_ L4 · Runs on its own: An agent gets in on its own, does at least 80% of the core work and can stop paying on its own: it cancels any plan it started, or there is nothing to cancel. Whether it can also remove what it made shows next to the level. - Find: Docs for agents (llms.txt, an OpenAPI and an MCP server) - Access: Sign-up in a browser - Use: 80% of the work - Pay: Payment not reached - Leave: Leaves on its own (Cancels on its own, deletes its account) - Ways in: Sign-up in a browser, 8 of 10 core tasks - Next: pay without a person ## Level history - 1 Oct 2026: L4 · Runs on its own - 2 Oct 2026: L4 · Runs on its own ## Part scores - Agent-ready setup: llms.txt 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 site opens. - Agents in a person's browser: Not measured yet. Sign-up page checked 13 Oct 2026. Signed agents: the ones Cloudflare verifies. ## Checkpoints - **Docs**: Headless: twenty.com/llms.txt and docs.twenty.com/llms.txt (plain text), MCP server card at /.well-known/mcp/server-card.json, RFC 9727 API catalog at /.well-known/api-catalog. llms.txt explicitly allows agent-driven sign-up (ToS section 10). - **Sign up**: In a browser: Email + password on app.twenty.com in our agent's browser. Invisible reCAPTCHA let our signed agent through, no visible challenge. There is no headless sign-up API; llms.txt says this is deliberate. Onboarding (workspace name/subdomain, skip mailbox sync, apps, invites, choose plan) is browser only. - **Verify**: In a browser: The verification mail arrived within a minute. Opening the link showed 'Email Verification Failed: You must be authenticated' anyway, but signing in afterwards went straight on to workspace creation, so the address had been accepted. - **Key**: In a browser: API key created under Settings > MCP & APIs > API (Admin role, never expires). It is shown once; to capture it we had to regenerate it. OAuth 2.1 with dynamic client registration also works headless, apart from one consent click in a logged-in browser. - **First call**: Headless: GET /rest/companies with Bearer key -> 200; per-workspace OpenAPI (322 core + 27 metadata paths); MCP initialize + tools/list over streamable HTTP. - **First action**: Headless: Created a company through MCP execute_tool create_one_company and read it back through REST. - **Pay**: Not reached: No agent payment rail: x402./mpp./agents. subdomains 404, no 402 anywhere, no /.well-known/ucp, no billing API in docs. A 7-day Pro trial starts without a card (a 30-day trial needs billing details). The only purchase path is in the web app: Settings > Billing > Subscribe Now > 'Add credit card'. Clicking that in our agent's browser did nothing: no page change, no popup, no Stripe request (an hCaptcha script was on the page). So a person has to add the card. - **Cancel**: In a browser: 'Cancel Plan' button under Settings > Billing; deleting the workspace also ended the trial. No billing API. Nothing recurring was ever started (no card). - **Delete**: In a browser: Settings > General > Delete workspace, type your email to confirm. Afterwards the API returned 401 WORKSPACE_NOT_FOUND. No documented API route for deleting the workspace or account. ## Does Twenty (twenty.com) have an MCP server, and can an agent connect to it? Yes. Twenty has an official MCP server. The server is hosted, lists 324 tools and signs an agent in with OAuth. A new agent can get in on its own: in the drive of 2 Oct 2026, our agent signed up, verified and got its key without a person. Through the MCP server, 7 of our agent's 12 attempts worked. ## How does an AI agent get a Twenty (twenty.com) API key? In the drive of 2 Oct 2026, our agent got its Twenty API key in a browser, without a person. API key created under Settings > MCP & APIs > API (Admin role, never expires). It is shown once; to capture it we had to regenerate it. OAuth 2.1 with dynamic client registration also works headless, apart from one consent click in a logged-in browser. ## Paying the agent way Payment not reached. No card needed to start. 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 2 Oct 2026. ## What an agent can do - Create, update, relate and delete companies, people, opportunities, notes and tasks through MCP or REST - Define a custom object with number and relation fields and use it right away over REST and GraphQL - Build a saved kanban view with a filter and a sort through MCP - Build, activate and trigger a two-step workflow and read its run log - Put an AI agent step into a workflow and get its answer written back as a note - Build a dashboard with a count chart through MCP - Register an OAuth client (dynamic registration) and call the API with the token after one consent click - Batch-create records in one REST call ## What it cannot do - Sign up, verify and create a workspace without a browser: Sign-up is web-only and protected by reCAPTCHA, by design according to llms.txt - Mint the first API key headless: The key is created in Settings in the web app; the OAuth route needs a consent click in a logged-in browser - Buy a plan: No billing API or agent payment rail; 'Add credit card' in the web app opened nothing in our agent's browser - Delete the workspace or account through the API: Only Settings > General > Delete workspace in the web app - Connect a mailbox and calendar: Google or Microsoft OAuth only; we had no such account ## Tips for the owner 1. Let an MCP OAuth login create the workspace 2. Fix trigger variable syntax in workflow tool docs 3. Make workflow step creation atomic and validated 4. Offer a billing link or API for agents 5. Fix the misleading email verification error page 6. Add an API route to delete a workspace 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 CRM - [Attio](https://agentdrives.com/tools/attio.md?via=md): L4 · Runs on its own · [Twenty vs Attio](https://agentdrives.com/compare/attio-vs-twenty?via=md) - [Pipedrive](https://agentdrives.com/tools/pipedrive.md?via=md): L3 · Does the work · [Twenty vs Pipedrive](https://agentdrives.com/compare/pipedrive-vs-twenty?via=md) - [Copper](https://agentdrives.com/tools/copper.md?via=md): L1 · Needs a person · [Twenty vs Copper](https://agentdrives.com/compare/copper-vs-twenty?via=md) - [Close](https://agentdrives.com/tools/close.md?via=md): L1 · Needs a person · [Twenty vs Close](https://agentdrives.com/compare/close-vs-twenty?via=md) - [folk](https://agentdrives.com/tools/folk.md?via=md): L1 · Needs a person · [Twenty vs folk](https://agentdrives.com/compare/folk-vs-twenty?via=md) - [HubSpot](https://agentdrives.com/tools/hubspot.md?via=md): L1 · Needs a person · [Twenty vs HubSpot](https://agentdrives.com/compare/hubspot-vs-twenty?via=md) - [Salesforce](https://agentdrives.com/tools/salesforce.md?via=md): L1 · Needs a person · [Twenty vs Salesforce](https://agentdrives.com/compare/salesforce-vs-twenty?via=md) ## Tips for agent builders - Use the MCP server at https://{workspace}.twenty.com/mcp with 'Authorization: Bearer '. tools/list only shows 7 meta-tools: call get_tool_catalog once, then learn_tools for schemas and execute_tool to run. - MCP find_many_* needs an explicit select parameter. - Workflow step ids must be UUIDs. In database-event triggers, read fields as {{trigger.properties.after.}}, not {{trigger.object.}}. - AI_AGENT steps: create_workflow_version_step, then update_agent, then update_workflow_version_step. Active versions are read-only, so use create_draft_from_workflow_version. - After create_workflow_version_step, check the step's settings: CREATE_RECORD defaulted to company, which can loop on a company.created trigger. - company.domainName is unique per workspace; a duplicate returns 400 with a constraint name. - The API key is shown once; copy it at creation or you will have to regenerate it.