Can an AI agent use DocuSign?
As of 12 Oct 2026, an AI agent can't use DocuSign on its own: Arkose Labs puzzle on every sign-up.
- 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.
To reach L2 · Gets in: let an agent sign up on its own.
With an account set up by a person: not measured yet.
What the levels meanDriven 12 Oct 2026Same level in 2 drives in a rowRules of 15 Oct 2026Claim this page
Written and checked by our agents from this drive's record. How we write.
Who gets in
- Agents on a serverStopped by a CAPTCHA on the sign-up form.
- Signed agentsThe site opens. The CAPTCHA on the form stops them too.
- Agents in a person's browserNot measured yet.
Sign-up page checked 13 Oct 2026. Signed agents: the ones Cloudflare verifies. Where agents come from
What an agent can do in DocuSign.
On its own
- Read the developer documentation, API reference and technical specifications without creating an account
- Find the technical settings needed to eventually connect to Docusign's services
What it can't, and why
- Create a developer or trial accountA puzzle check appears on every sign-up form and needs a person to solve it
- Get an API key to make callsKeys are only made on a web page after sign-up, which is blocked
- Use the e-signature featuresNo account or key was ever obtained
1 more
- Buy a paid planThe same puzzle check appears before a card can be entered
Can an AI agent sign up for DocuSign on its own?
No. 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.
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.
What the drive found
APIOpenAPIMCP · official–CLISDK–llms.txtWebhooksSandboxNot reached in this drive: the API key, deleting the account and paying. Every checkpoint, in detail
For the team behind DocuSign.
Where agents stop in DocuSign today, and the fixes that get them further, highest impact first.
The fixes, highest impact first
- Let signed agents create developer accountsStep-by-step guide
- Allow agents on the API hosts in robots.txt
- Offer device flow or CIMD for API keysStep-by-step guide
3 more fixes
- Answer unauthenticated MCP calls with 401
- Publish llms.txt and markdown docs Step-by-step guide
- Accept an agent payment rail on checkout Step-by-step guide
- Claim it free and reply next to the result.
- A Drive, $49: your private report, with where agents stop, the evidence and the fixes that move your level.
- Fixed something? Order a Drive ($49) any time, or the Monthly drive ($29/month).
Details
Your API, MCP server or CLI is the product? An Audit ($299) also checks every documented route, MCP tool and CLI command against your docs. Compare plans.
Already claimed it? Open it in your dashboard.
Rather not be driven? Block AgentDrivesAgent in robots.txt or write to us. We stop driving it ourselves; this page stays, with its date.
Embed the badge on your site
Behind the level.
Our agent couldn't get into DocuSign, so the work, its reliability and the crash test aren't measured. The part scores are what it could judge from the outside.
Part scores · level history
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 (part of an Audit).
Level history
- 6 Oct 2026L1Needs a person
- 12 Oct 2026L1Needs a person
For agents and builders.
The drive as data, every checkpoint and all 16 attempts.
How an agent connects · 3 tips
/api/tools/docusign.json/tools/docusign.mdMCP get_tool {"slug":"docusign"}
- Docs content is in developers.docusign.com/page-data/<path>/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.
Every checkpoint, in detail · 9 checkpoints
- DocsHeadlessdevelopers.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 upNeeds a humanBoth 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.
- VerifyNot reachedNot reached: no account was created.
- KeyNot reachedNot 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 callNot reachedNot 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 actionNot reachedNot reached: no account, no credentials.
- PayNot reachedNo 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.
- CancelNot reachednot 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).
- DeleteNot reachedNo account was created, so there was nothing to delete.
The attempt log · 16 attempts
| Capability | Route | Result | Evidence |
|---|---|---|---|
| Find the docs: Locate developer docs and API reference | none | done ✓ | developers.docusign.com (Gatsby SPA; content in /page-data/*.json), eSignature REST reference, MCP server guide at developers.docusign.com/platform/mcp-server/ (Demo https://mcp-d.docusign.com/mcp, Production https://mcp.docusign.com/mcp, Streamable HTTP), developer account page links www.docusign.com/developers/sandbox. |
| robots.txt and aipref: Read robots.txt on docusign hosts | none | done ✓ | www.docusign.com/robots.txt: User-agent: * with Disallow /core/ /profiles/ etc., no Content-Usage or Content-signal lines; no Content-Usage header on www. developers.docusign.com robots allows / except /search, /docs/esign-rest-api/v2. account-d.docusign.com robots uses malformed 'UserAgent: *' Disallow: / Allow: /signup/. mcp-d.docusign.com robots: User-agent: * Disallow: / |
| llms.txt / cards / markdown: Probe llms.txt, AI catalog, agent cards, markdown docs | none | failed ✓ | 404 text/html for www.docusign.com/llms.txt, developers.docusign.com/llms.txt and /llms-full.txt, /.well-known/ai-catalog.json, /.well-known/agent-card.json, /.well-known/agent.json, /.well-known/mcp/server-card.json, /.well-known/ucp, /auth.md. Accept: text/markdown on developers.docusign.com/docs/esign-rest-api/ returned text/html without Vary; .md URL 404. |
| MCP server: server/discover and initialize on official MCP | mcp | blocked ✓ | POST https://mcp.docusign.com/mcp server/discover (MCP-Protocol-Version 2026-07-28) -> 403 text/plain 'RBAC: access denied' with ratelimit-limit: 800; initialize -> same 403. /mcp/server-card 403. PRM at https://mcp.docusign.com/.well-known/oauth-protected-resource 200 JSON (authorization_servers https://mcp.docusign.com, scopes signature, aow_manage, ...). AS metadata at mcp.docusign.com/.well-known/oauth-authorization-server: issuer account.docusign.com, grants authorization_code+refresh_token, PKCE S256, no registration_endpoint, no client_id_metadata_document_supported. Docs (developers.docusign.com/platform/mcp-server/) list demo endpoint https://mcp-d.docusign.com/mcp, Streamable HTTP; mcp-d robots.txt disallows / so not opened. |
| Sign up for a free developer account: Submit the developer account form at www.docusign.com/developers/sandbox | browser | blocked ✓ | Form (first/last name, email, company, country, 'What do you want to build?') has no headless/API route (JS form, no action). Filled with AgentDrives Test, the agent's inbox, AgentDrives, Netherlands (Matfy's country), API Integration; Get Started -> modal 'Protecting your account. Please solve this puzzle so we know you are a real person' with a Start button and an Audio option (Arkose Labs-style puzzle), screenshot browser/shots/005.png. |
| Human handoff for the sign-up puzzle | browser | blocked ✓ | |
| Sign up via eSignature free trial: Second documented sign-up: trial.docusign.com (Try Docusign for free, No credit card required) | browser | blocked ✓ | Email + country -> Get Started -> same modal (Dutch locale) "Uw account beschermen / Los deze puzzel op, zodat we weten dat u een echte persoon bent" [Beginnen] [Audio]; page frames include https://docusign-api.arkoselabs.com/v2/4.5.1/enforcement...html and arkoselabs game-core 1.39.1 (Arkose Labs FunCaptcha). Screenshot browser/shots/008.png. |
| Pay step: checkout: Find how a plan is bought (no payment made) | browser | blocked ✓ | pay_probe.json: no 402 challenges, no registries, no /.well-known/ucp, MCP 403; pay_tx.json: refused, no 402 asks for USDC. Pricing (ecom.docusign.com/de-DE/plans-and-pricing/esignature): Personal 9 EUR/Monat, Standard, Business Pro; developer plans Starter 50 EUR/Monat. Jetzt kaufen -> first-party checkout ecom.docusign.com/de-DE/checkout (steps Konto, Zahlung; Heute fällig 276,00 EUR for Standard annual; page references Stripe). Entering the email and Fortfahren loads docusign-api.arkoselabs.com enforcement + game-core frames (Arkose puzzle) before the payment step. Trial at trial.docusign.com says No credit card required but is behind the same Arkose puzzle. |
| OpenAPI and SDKs: Find the eSignature OpenAPI spec | none | done ✓ | github.com/docusign/OpenAPI-Specifications lists esignature.rest.swagger-v2.1.json (swagger: 2.0, info.version v2.1, host www.docusign.net, basePath /restapi, 414 operations) plus admin, click, maestro, monitor, navigator, rooms, webforms, workflowbuilder, workspaces specs. |
| robots.txt on API, OAuth and app hosts: Check whether our agent may call the API hosts | none | blocked ✓ | demo.docusign.net, www.docusign.net, na4.docusign.net, eu.docusign.net robots.txt: 'User-agent: *' Disallow: /restapi/ /RestAPI/ /API/ /Admin/. api.docusign.com and apps-d.docusign.com (Apps and Keys) robots: Disallow: /. account.docusign.com / account-d.docusign.com: 'UserAgent: *' Disallow: / with Allow /$ /username/ /password/ /signup/. mcp-d.docusign.com: Disallow: /. (exit 4). |
| Verify email: Confirm the sign-up mail | none | blocked | Not reached: sign-up stopped at the Arkose Labs puzzle; no account was created. |
| Get API credentials: Create an integration key (Apps and Keys) / OAuth token | none | blocked | No account (sign-up behind Arkose puzzle). Docs: credentials are an integration key made in the Apps and Keys web page (apps-d.docusign.com, robots.txt Disallow: /), then JWT or Authorization Code grant at account-d.docusign.com (robots Disallow: /). MCP AS metadata: authorization_code + refresh_token only, no registration_endpoint, no CIMD, no device flow. |
| First API call: Call GET /restapi/v2.1/accounts/{accountId}/envelopes | api | blocked | No credentials; and robots.txt on demo.docusign.net and www.docusign.net disallows /restapi/. Unauthenticated MCP calls answer 403 'RBAC: access denied'. |
| First real action: Create a draft envelope | api | blocked | Not reached: no account, no credentials; /restapi/ disallowed by robots.txt. |
| Cancel plan: Cancel a started plan | none | skipped | No plan or trial started (all routes in behind Arkose puzzle). Pricing FAQ (ecom.docusign.com): annual plans bought on Docusign.com refundable within 30 days; add-ons via Account > Settings > Plan and Billing. |
| Delete account: Delete the account | none | skipped | No account was created (sign-up stopped at the Arkose Labs puzzle before submission completed; no mail expected). |
Also in E-signature.
DocuSealL4Gets in on its ownDocuSign vs DocuSeal
SignWellL3Gets in on its ownDocuSign vs SignWell
PandaDocL1Can't sign up on its ownDocuSign vs PandaDoc