folk vs Pipedrive for AI agents
As of 6 Oct 2026, Pipedrive 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.
- Access: Can't verify its account.
- Use: Work not reached.
- Pay: Payment not reached.
- Leave: Leaving not reached.
Stopped at verify: blocked. Next: let an agent verify its account on its own
Gets in only with a person: L1 · Needs a person. Our agent started sign-up itself at app.folk.app, but the emailed magic link runs Stytch Device Fingerprinting, and both links landed on a "Login Error" page instead of a session. Without that session, API keys stay locked in Settings, and MCP OAuth's authorize step sends an agent back to the same blocked magic link, so no key or token was ever issued. No CRM work was done through API, MCP or CLI. Docs are thorough: llms.txt, Markdown pages, OpenAPI, MCP guides. Paying and deleting the account both need a browser login our agent never reached, so neither was tested.
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: 71% of the work.
- Pay: Payment not reached.
- Leave: Nothing to cancel: Can't delete its account.
Got in; payment not reached. Next: do 80% of the core work (now 71%)
Our agent gets in on its own: L3 · Does the work, through the free developer sandbox form in a browser, no bot check met along the way. Deletion stopped it first: it deleted every record it created through the API, but found no account or company delete, only "Leave company," with inactive sandboxes purged later. Through the API and the official MCP server it created, moved, converted, searched, filtered and deleted CRM data end to end. Paying needs a human too: the pricing page returned a Cloudflare block, and the regular trial sign-up gave a generic error, so a person has to start the trial and checkout.
Gets furtherDriven 2 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.
folkStopped at verify: blocked
PipedriveGot in; payment not reached
| Checkpoint | folk | Pipedrive |
|---|---|---|
| Docs | Headless | Headless |
| Sign up | In a browser | In a browser |
| Verify | Blocked | Not needed |
| Key | Not reached | In a browser |
| First call | Not reached | Headless |
| First action | Not reached | Headless |
| Pay | Not reached | Not reached |
| Cancel | Not reached | Not needed |
| Delete | Not reached | Blocked |
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
| folk | Pipedrive | |
|---|---|---|
| Headless (checkpoints) | 1 | 3 |
| In a browser (checkpoints) | 1 | 2 |
| Needs a human (checkpoints) | 0 | 0 |
| Blocked (checkpoints) | 1 | 1 |
| Not tested (checkpoints) | 6 | 1 |
| Work done | Not measured | 71% of the core |
| API | Yes | Yes |
| OpenAPI | Yes | Yes |
| MCP server | Yes (official) | Yes (official) |
| CLI | No | No |
| SDK | No | Yes |
| llms.txt | Yes | Yes |
Bot checks, and where a person was needed.
| folk | Pipedrive | |
|---|---|---|
| Bot check | Stytch Device Fingerprinting (magic-link redirect) stopped it at verify, without a visible challenge | None met |
| Wall type | A check of our network and browser | No bot-check wall |
| First wall | Stytch fingerprint check blocks magic-link login | Got in; payment not reached |
| 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.
| folk | Pipedrive | |
|---|---|---|
| Level | L1 · Needs a person | L3 · Does the work |
| Agent-ready setup | 90 of 100, good | 100 of 100, good |
| Standards | MCP client registration (current) · OpenAPI 3.1.0 (1 version behind) | None recorded |
Holds up: not measured in these drives. Docs match is measured in an Audit. What the scores mean.
Pay, cancel and delete.
| folk | Pipedrive | |
|---|---|---|
| Pay | Payment not reached | Payment not reached |
| Free plan or trial | Trial, no card | Trial, no card |
| Cancel | Not reached | Not needed |
| Delete the account | Not reached | Blocked |
How each one takes payment
- folk: Payment not reached.
- Pipedrive: Payment not reached.
folk vs Pipedrive: the short answers.
Which can an AI agent use, folk or Pipedrive?
Pipedrive gets an AI agent further: L3 · Does the work against L1 · Needs a person. With folk our agent was stopped at verify (blocked); with Pipedrive it got in (payment not reached). Driven 6 Oct 2026 (folk) and 2 Oct 2026 (Pipedrive).
Can an AI agent sign up for folk and Pipedrive on its own?
folk: yes, in a browser, but a later step stopped it. Pipedrive: yes, in a browser.
Do folk and Pipedrive have an MCP server?
folk: yes (official). Pipedrive: yes (official).
Can an AI agent delete its folk or Pipedrive account?
folk: not reached. Pipedrive: blocked.
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.