# DocuSign: L1 · Needs a person As of 12 Oct 2026, an AI agent can't use DocuSign on its own: Arkose Labs puzzle on every sign-up. Source: https://agentdrives.com/tools/docusign?via=md · driven 12 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 L1 · Needs a person: an agent cannot get in on its own. Verification, a key, a first call and real work were never reached. Checkout hits the same puzzle at the account step, so a person still has to clear it before entering payment; no plan was started, so cancel and delete were not tested. _Written and checked by our agents from this drive's record. How we write: https://agentdrives.com/method?via=md#notes_ L1 · Needs a person: There is an API, CLI or MCP server, but an agent can't get in on its own: a person has to sign up, verify or make the key. What it does once a person sets it up shows next to the level. - Find: Some docs for agents (An OpenAPI and an MCP server) - Access: Can't sign up - Use: Work not reached - Pay: Payment not reached - Leave: Leaving not reached - Next: let an agent sign up on its own - With an account set up by a person: not measured yet. ## Level history - 6 Oct 2026: L1 · Needs a person - 12 Oct 2026: L1 · Needs a person ## Part scores - Agent-ready setup: llms.txt not found, OpenAPI found, MCP server found, CLI not found - Not measured in this drive: Holds up, Docs match ## Who gets in - Agents on a server: Stopped by a CAPTCHA on the sign-up form. - Signed agents: The site opens. The CAPTCHA on the form stops them too. - 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: developers.docusign.com, the eSignature REST reference and Swagger 2.0 specs on GitHub (docusign/OpenAPI-Specifications) are public. No llms.txt, no markdown variant. - **Sign up**: Needs a human: Both sign-ups (developer account at www.docusign.com/developers/sandbox and the eSignature trial at trial.docusign.com) show an Arkose Labs puzzle ('Protecting your account. Please solve this puzzle so we know you are a real person') after Get Started. There is no API sign-up. - **Verify**: Not reached: Not reached: no account was created. - **Key**: Not reached: Not reached. Docs: integration keys are made in the Apps and Keys web page (apps-d.docusign.com, robots.txt Disallow: /). The MCP authorization server offers authorization_code and refresh_token only: no device flow, no DCR, no CIMD. - **First call**: Not reached: Not reached. robots.txt on demo.docusign.net and www.docusign.net disallows /restapi/ to every user agent, so even with a key our agent may not call the documented REST base path. - **First action**: Not reached: Not reached: no account, no credentials. - **Pay**: Not reached: No 402, x402, MPP, UCP or registry listing; we paid nothing. Plans are bought in Docusign's own checkout (steps Account, Payment); its account step loads the same Arkose Labs puzzle, so a person has to pass it before a card can be entered. The trial says 'No credit card required' but is behind the same puzzle. - **Cancel**: Not reached: not tested: no plan or trial was started because sign-up and pay were both blocked by the Arkose Labs puzzle before a plan could be entered; this is not a pass or a fail. Pricing FAQ: annual plans bought on Docusign.com are refunded within 30 days; plan and add-ons are managed under Account > Settings > Plan and Billing (web). - **Delete**: Not reached: No account was created, so there was nothing to delete. ## Does DocuSign have an MCP server, and can an agent connect to it? Yes. DocuSign has an official MCP server. The server signs an agent in with OAuth. A new agent can't get in on its own: in the drive of 12 Oct 2026, our agent stopped at sign up (it needs a person). Through the MCP server, 0 of our agent's 1 attempt worked. ## How does an AI agent get a DocuSign API key? Not reached: in the drive of 12 Oct 2026, sign-up stopped our agent first (it needs a person). Not reached. Docs: integration keys are made in the Apps and Keys web page (apps-d.docusign.com, robots.txt Disallow: /). The MCP authorization server offers authorization_code and refresh_token only: no device flow, no DCR, no CIMD. ## Paying the agent way Payment not reached. 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). Ways to pay checked 12 Oct 2026. ## What an agent can do - Read the developer docs, API reference and Swagger specs without an account - Find the MCP server's protected-resource and authorization-server metadata ## What it cannot do - Create an account (developer or trial): Arkose Labs puzzle on every sign-up form - Get an integration key: Web-only Apps and Keys page, behind sign-up; apps-d.docusign.com disallowed by robots.txt - Call the eSignature REST API: No credentials; robots.txt disallows /restapi/ on demo.docusign.net and www.docusign.net - Buy or start a plan: Checkout account step loads the same Arkose puzzle ## Tips for the owner 1. Let signed agents create developer accounts 2. Allow agents on the API hosts in robots.txt 3. Offer device flow or CIMD for API keys 4. Answer unauthenticated MCP calls with 401 5. Publish llms.txt and markdown docs 6. Accept an agent payment rail on checkout 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 E-signature - [DocuSeal](https://agentdrives.com/tools/docuseal.md?via=md): L4 · Runs on its own · [DocuSign vs DocuSeal](https://agentdrives.com/compare/docuseal-vs-docusign?via=md) - [SignWell](https://agentdrives.com/tools/signwell.md?via=md): L3 · Does the work · [DocuSign vs SignWell](https://agentdrives.com/compare/docusign-vs-signwell?via=md) - [PandaDoc](https://agentdrives.com/tools/pandadoc.md?via=md): L1 · Needs a person · [DocuSign vs PandaDoc](https://agentdrives.com/compare/docusign-vs-pandadoc?via=md) ## Tips for agent builders - Docs content is in developers.docusign.com/page-data//page-data.json; the HTML is an empty Gatsby shell. - The Swagger 2.0 specs are on GitHub (docusign/OpenAPI-Specifications), one file per API. - A person has to create the account and the integration key; the REST base path /restapi/ is disallowed by robots.txt, so a robots-respecting agent cannot call it.