PandaDoc vs SignWell for AI agents
As of 15 Oct 2026, SignWell gets an AI agent further: L3 · Does the work against L1 · Needs a person.
- Find: Docs for agents: llms.txt, an OpenAPI and an MCP server; a docs page for each core task.
- Access: Can't sign up.
- Use: Work not reached.
- Pay: Payment not reached.
- Leave: Leaving not reached.
Stopped at sign up: blocked. Next: let an agent sign up on its own
Needs a person to get in: PandaDoc sits at L1, stopped before any work could start. Sign-up passes both steps of the free trial form, then the final submit answers "Captcha is not valid": an invisible reCAPTCHA refuses our agent's browser without showing a challenge, so there is no step a human could clear either. The docs open without an account: llms.txt, markdown pages, a full OpenAPI spec and the docs MCP all load headless. Only the key page, the official OAuth MCP login and every API call sit behind the account the captcha refused, so none of the core capabilities could be tried. Paying and cancelling were never reached: no account was created.
Driven 15 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: 100% of the work.
- Pay: Reaches the checkout: Stopped at the card form.
- Leave: Cancels via support: Cancels only through a retention flow or support.
In on its own; 100% of the work done. Next: cancel the plan on its own
Gets in on its own: L3 · Does the work. Signup and email verification ran headless with no challenge shown. It stopped at credentials: the API key lives in Settings > API behind a mandatory onboarding wizard, and the headless session did not carry over, so no key could be minted without a browser. Once a key was in hand, the API drafted a document in test mode, with the documented reference covering fields, signing order, send, tracking and templates. Paying stayed untested since no card was entered, and leaving meant a web-only Cancel Plan flow with a retention offer before the account and key were deleted.
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.
PandaDocStopped at sign up: blocked
SignWellIn on its own; 100% of the work done
| Checkpoint | PandaDoc | SignWell |
|---|---|---|
| Docs | Headless | Headless |
| Sign up | Blocked | Headless |
| Verify | Not reached | Headless |
| Key | Not reached | In a browser |
| First call | Not reached | Headless |
| First action | Not reached | Headless |
| Pay | Not reached | In a browser |
| Cancel | Not reached | In a browser |
| Delete | Not reached | 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
| PandaDoc | SignWell | |
|---|---|---|
| Headless (checkpoints) | 1 | 5 |
| In a browser (checkpoints) | 0 | 4 |
| Needs a human (checkpoints) | 0 | 0 |
| Blocked (checkpoints) | 1 | 0 |
| Not tested (checkpoints) | 7 | 0 |
| Work done | Not measured | 100% of the core |
| API | Yes | Yes |
| OpenAPI | Yes | Yes |
| MCP server | Yes (official) | Yes (official) |
| CLI | No | Yes |
| SDK | – | No |
| llms.txt | Yes | Yes |
Bot checks, and where a person was needed.
| PandaDoc | SignWell | |
|---|---|---|
| Bot check | Google reCAPTCHA (invisible, score) stopped it at sign up, without a visible challenge | First-party honeypot fields on the sign-up form (field1, status) let it through at sign up |
| Wall type | A check of our network and browser | No bot-check wall |
| First wall | Invisible reCAPTCHA refuses sign-up | None |
| A person helped | No | No |
A check of our network and browser: It judged where our agent connects from and its browser, not a person. An agent that works on its own from a data center doesn't get through unless the owner lets signed agents in. How agents in a person's own browser fare isn't measured yet. Where we drive from.
Level and part scores.
| PandaDoc | SignWell | |
|---|---|---|
| Level | L1 · Needs a person | L3 · Does the work |
| Agent-ready setup | 100 of 100, good | 100 of 100, good |
| Standards | MCP client registration (behind) · OpenAPI 3.0.3 (2 versions behind) | MCP spec of 25 Nov 2025 (1 version behind) · MCP discovery (behind) · OpenAPI 3.0.1 (2 versions behind) |
Holds up: not measured in these drives. Docs match is measured in an Audit. What the scores mean.
Pay, cancel and delete.
| PandaDoc | SignWell | |
|---|---|---|
| Pay | Payment not reached | Reaches the checkout |
| Free plan or trial | Trial, no card | Trial, no card |
| Cancel | Not reached | In a browser |
| Delete the account | Not reached | In a browser |
How each one takes payment
- PandaDoc: Payment not reached.
- SignWell: Reaches the checkout: stopped at the card form.
PandaDoc vs SignWell: the short answers.
Which can an AI agent use, PandaDoc or SignWell?
SignWell gets an AI agent further: L3 · Does the work against L1 · Needs a person. With PandaDoc our agent was stopped at sign up (blocked); with SignWell it got in on its own and did 100% of the work. Driven 15 Oct 2026 (PandaDoc) and 6 Oct 2026 (SignWell).
Can an AI agent sign up for PandaDoc and SignWell on its own?
PandaDoc: no, blocked. SignWell: yes, headless.
Do PandaDoc and SignWell have an MCP server?
PandaDoc: yes (official). SignWell: yes (official).
Can an AI agent delete its PandaDoc or SignWell account?
PandaDoc: not reached. SignWell: 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.