<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"><channel><title>AgentDrives: agent test drives</title><link>https://agentdrives.com</link><description>Make sure AI agents can find your product, run it and pay you.</description>
<item><title>Tavily: L3 Does the work</title><link>https://agentdrives.com/tools/tavily</link><guid>https://agentdrives.com/tools/tavily#2026-10-16</guid><pubDate>Fri, 16 Oct 2026 12:00:00 GMT</pubDate><description>Tavily is easy for an agent to start with: keyless Search and Extract work on REST, a modern 28 Jul 2026 MCP server and the CLI with no account, and covered 4 of 8 core tasks. Getting further fails: email sign-up shows a Cloudflare Turnstile checkbox and GitHub/OAuth sign-in is refused by Auth0 as a 'Suspicious User Agent', so Crawl, Map and Research (free with a key) were out of reach. The first-party x402 rail sells only search, and our signed payments came back settlement_failed.</description></item>
<item><title>Vercel: L2 Gets in</title><link>https://agentdrives.com/tools/vercel</link><guid>https://agentdrives.com/tools/vercel#2026-10-16</guid><pubDate>Fri, 16 Oct 2026 12:00:00 GMT</pubDate><description>Vercel's docs are very agent-ready (llms.txt, Markdown pages, OpenAPI, AI Catalog, official MCP with OAuth and a CLI device login), but an agent cannot get in: the email sign-up was refused with no reason, and the GitHub sign-up created the account and then asked for a phone number for an SMS code on every login. Only keyless reads (AI Gateway model list, domain search) worked; the account it made could not be deleted.</description></item>
<item><title>Supabase: L1 Needs a person</title><link>https://agentdrives.com/tools/supabase</link><guid>https://agentdrives.com/tools/supabase#2026-10-16</guid><pubDate>Fri, 16 Oct 2026 12:00:00 GMT</pubDate><description>Once in, an agent can do nearly all of Supabase headless: all 10 core capabilities passed create-read-update-delete through the Management API, MCP (the 28 Jul 2026 spec) and CLI, with repeats passing except a third user signup that hit the built-in mailer's rate limit (GraphQL first needed pg_graphql enabled). Getting in needs a browser: email sign-up shows an hCaptcha puzzle, so the drive came in with GitHub, and the first organization and token were made in the dashboard. Paying is a dashboard card checkout behind a visible hCaptcha, and the account itself cannot be deleted.</description></item>
<item><title>Apify: L1 Needs a person</title><link>https://agentdrives.com/tools/apify</link><guid>https://agentdrives.com/tools/apify#2026-10-16</guid><pubDate>Fri, 16 Oct 2026 12:00:00 GMT</pubDate><description>An agent with a wallet gets into Apify with no account and no human: we paid $1 over x402 at agi.apify.com and the token ran every core task headless (Actors, storage, own Actor build and deploy, proxy from an Actor), 8 of 9 core capabilities, each repeated three times. The email sign-up shows a reCAPTCHA puzzle, but GitHub sign-in, the device flow and MCP OAuth all work; monetization, token revocation and account deletion are Console-only.</description></item>
<item><title>Canva: L1 Needs a person</title><link>https://agentdrives.com/tools/canva</link><guid>https://agentdrives.com/tools/canva#2026-10-16</guid><pubDate>Fri, 16 Oct 2026 12:00:00 GMT</pubDate><description>An agent cannot get into Canva: every www.canva.com page, including sign-up and the OAuth consent page that REST, MCP and the CLI all need, shows a Cloudflare interstitial that never cleared for our agent's browser. The developer surface around it is strong (Markdown docs, OpenAPI 3.0.0, an official MCP server with PRM, CIMD and DCR, a CLI wrapping the API), but none of it works without that token.</description></item>
<item><title>ClickUp: L1 Needs a person</title><link>https://agentdrives.com/tools/clickup</link><guid>https://agentdrives.com/tools/clickup#2026-10-16</guid><pubDate>Fri, 16 Oct 2026 12:00:00 GMT</pubDate><description>ClickUp has strong agent-facing docs (llms.txt, markdown pages, OpenAPI v2 and v3) and an official remote MCP server with OAuth discovery, but an agent cannot get in on its own: the only email sign-up shows a visible reCAPTCHA v2 checkbox. With no account there was no token, so none of the map's capabilities could be tried.</description></item>
<item><title>Figma: L1 Needs a person</title><link>https://agentdrives.com/tools/figma</link><guid>https://agentdrives.com/tools/figma#2026-10-16</guid><pubDate>Fri, 16 Oct 2026 12:00:00 GMT</pubDate><description>An agent cannot get into Figma on its own: robots.txt disallows /signup, /login and the MCP consent page for AI agents that act for a user, and the MCP server's client registration answers 403 to clients outside Figma's catalog. The docs are strong (llms.txt, an OpenAPI 3.1 spec, a documented MCP server), but no capability could be driven without an account.</description></item>
<item><title>HubSpot: L1 Needs a person</title><link>https://agentdrives.com/tools/hubspot</link><guid>https://agentdrives.com/tools/hubspot#2026-10-16</guid><pubDate>Fri, 16 Oct 2026 12:00:00 GMT</pubDate><description>HubSpot's docs are agent-friendly (llms.txt, markdown pages, an official MCP server and an Agent CLI), but an agent cannot get in on its own: the email sign-up shows a visible reCAPTCHA checkbox before the code is sent. Every capability, the key, MCP and the checkout sit behind that wall, so nothing in the CRM was driven.</description></item>
<item><title>Linear: L1 Needs a person</title><link>https://agentdrives.com/tools/linear</link><guid>https://agentdrives.com/tools/linear#2026-10-16</guid><pubDate>Fri, 16 Oct 2026 12:00:00 GMT</pubDate><description>An agent cannot get into Linear on its own: the email sign-up shows a visible Cloudflare Turnstile and no other way in fits an agent (Google needs an account we lack, no GitHub, no API sign-up). The docs are excellent for agents (llms.txt, Markdown pages, a public GraphQL schema, an official MCP server that takes API keys), but all of it needs an account.</description></item>
<item><title>Salesforce: L1 Needs a person</title><link>https://agentdrives.com/tools/salesforce</link><guid>https://agentdrives.com/tools/salesforce#2026-10-16</guid><pubDate>Fri, 16 Oct 2026 12:00:00 GMT</pubDate><description>An agent cannot get into Salesforce: the free Developer Edition sign-up on developer.salesforce.com and the Trailblazer sign-in behind the Starter Suite trial are refused by Akamai (403, no challenge), and the Enterprise trial form requires a phone number. The docs are agent-friendly on docs.salesforce.com (llms.txt, markdown pages) and there is an official hosted MCP server and a rich sf CLI, but all of it needs an org we could not create, so no capability was driven.</description></item>
<item><title>Slack: L1 Needs a person</title><link>https://agentdrives.com/tools/slack</link><guid>https://agentdrives.com/tools/slack#2026-10-16</guid><pubDate>Fri, 16 Oct 2026 12:00:00 GMT</pubDate><description>An agent cannot get into Slack on its own: the email sign-up and the Developer Program join form both show a visible reCAPTCHA 'I'm not a robot' checkbox to tick it, so no account, token or core task was reached. What an agent can do without an account is read excellent developer docs (llms.txt, Markdown on every page), the Swagger 2.0 Web API spec and the official MCP server's OAuth metadata, which needs a pre-registered Slack app.</description></item>
<item><title>Parallel: L5 Autonomous</title><link>https://agentdrives.com/tools/parallel</link><guid>https://agentdrives.com/tools/parallel#2026-10-15</guid><pubDate>Thu, 15 Oct 2026 12:00:00 GMT</pubDate><description>An agent can search and extract through Parallel's free anonymous MCP server and pay per call with x402 or MPP for search, extract, responses and research, all without an account. Signing up by email link works without a bot check and the CLI's device login plus the Account API give a key headlessly, but on a new account every paid endpoint answers 402 until a card is saved, so only monitor management works. The account cannot be deleted without emailing support.</description></item>
<item><title>Airtable: L4 Runs on its own</title><link>https://agentdrives.com/tools/airtable</link><guid>https://agentdrives.com/tools/airtable#2026-10-15</guid><pubDate>Thu, 15 Oct 2026 12:00:00 GMT</pubDate><description>An agent can run almost all of Airtable's core once it has a token: REST and the official MCP server (46 tools) covered bases, records, schema, webhooks, automations, interfaces and forms, and Omni and field agents worked in the browser. Getting in needs a browser: sign-up is blocked headless, tokens are made only in the web UI, a workspace must be created in the UI, and automations can only be turned on there. Paying is a Stripe card form in the app; no agent rail or billing API.</description></item>
<item><title>Plane: L4 Runs on its own</title><link>https://agentdrives.com/tools/plane</link><guid>https://agentdrives.com/tools/plane#2026-10-15</guid><pubDate>Thu, 15 Oct 2026 12:00:00 GMT</pubDate><description>Plane is highly agent-operable once a key exists: every core task except AI agents ran end to end over the documented REST API (and the official MCP server), three times each, with clean read-back. Getting in still takes the browser: sign-up is an emailed code and API keys are minted only in the web UI. Paying goes through Stripe's hosted portal, blocked to our agent by robots.txt there, and the account cannot be deleted: only deactivated, which a later code login undoes (workspace data was removed, but the account and its login remain).</description></item>
<item><title>Exa: L2 Gets in</title><link>https://agentdrives.com/tools/exa</link><guid>https://agentdrives.com/tools/exa#2026-10-15</guid><pubDate>Thu, 15 Oct 2026 12:00:00 GMT</pubDate><description>An agent can use Exa without an account: the hosted MCP server searches and reads pages with no key, and /search and /contents take x402 or MPP payments per call. Getting an account is where it stops: the sign-up form shows a Cloudflare Turnstile and the dashboard blocks our agent's browser with a Vercel checkpoint, so answer, agent runs, websets and monitors stayed out of reach.</description></item>
<item><title>Intercom: L1 Needs a person</title><link>https://agentdrives.com/tools/intercom</link><guid>https://agentdrives.com/tools/intercom#2026-10-15</guid><pubDate>Thu, 15 Oct 2026 12:00:00 GMT</pubDate><description>An agent can sign up for Intercom's no-card trial in a browser, take an API token from the Developer Hub web page, and then run the helpdesk headless: conversations, tickets, ticket types, contacts, articles and Fin's knowledge all worked by API and read back cleanly, and Fin and Copilot answered from content the agent added. The Fin Agent API (ask, procedures, escalate) refused our trial with 'not enabled for your app' and has to be requested, tokens can only be made in the browser, and buying goes through a Stripe card form.</description></item>
<item><title>Akiflow: L1 Needs a person</title><link>https://agentdrives.com/tools/akiflow</link><guid>https://agentdrives.com/tools/akiflow#2026-10-15</guid><pubDate>Thu, 15 Oct 2026 12:00:00 GMT</pubDate><description>An agent cannot get into Akiflow on its own: registration answers with a reCAPTCHA image puzzle, the page hides it and hangs. The emailed login code works, and the only agent surface is a hosted MCP server behind OAuth (DCR), so nothing behind the door could be tested. There is no free plan and the 7-day trial needs a card.</description></item>
<item><title>Help Scout: L1 Needs a person</title><link>https://agentdrives.com/tools/helpscout</link><guid>https://agentdrives.com/tools/helpscout#2026-10-15</guid><pubDate>Thu, 15 Oct 2026 12:00:00 GMT</pubDate><description>Help Scout's sign-up form accepts an agent's address without a bot check, but then requires an SMS code to a phone number before the account exists, so an agent alone gets no account, no key and no API or MCP call. The docs (developer llms.txt) and the official MCP server's OAuth metadata (PRM, DCR) are agent-readable.</description></item>
<item><title>PandaDoc: L1 Needs a person</title><link>https://agentdrives.com/tools/pandadoc</link><guid>https://agentdrives.com/tools/pandadoc#2026-10-15</guid><pubDate>Thu, 15 Oct 2026 12:00:00 GMT</pubDate><description>PandaDoc's developer docs are among the most agent-ready we have seen (llms.txt, markdown pages, OpenAPI, a keyless docs MCP and an official OAuth MCP server), but an agent cannot get in: the free trial sign-up passes both form steps and then its invisible reCAPTCHA answers &quot;Captcha is not valid&quot; to our agent's browser. With no account there is no key or MCP session, so none of the 9 core capabilities could be tried.</description></item>
<item><title>AgentMail: L4 Runs on its own</title><link>https://agentdrives.com/tools/agentmail</link><guid>https://agentdrives.com/tools/agentmail#2026-10-14</guid><pubDate>Wed, 14 Oct 2026 12:00:00 GMT</pubDate><description>An agent can sign up, verify, get a key and run all nine core email tasks headless through the API, the official MCP server (the 28 Jul 2026 spec) and the CLI, with clear errors and working idempotency. It cannot delete its account (no route) or reach billing, since the console sits behind Cloudflare checks; free accounts may mail only 3 new recipients in their first hour.</description></item>
<item><title>Brave Search API: L1 Needs a person</title><link>https://agentdrives.com/tools/brave</link><guid>https://agentdrives.com/tools/brave#2026-10-14</guid><pubDate>Wed, 14 Oct 2026 12:00:00 GMT</pubDate><description>An agent can sign up and verify in a browser, but an API key needs an activated plan, and every plan, even the one with $5 of free monthly credits, needs a card at Stripe Checkout. Without an account, the docs playground ran real web, LLM-context, news, video, image and place searches in a browser, and Brave's own x402 host sells most endpoints per call, but our one payment answered 502 'could not be settled'. The account was deleted in the browser.</description></item>
<item><title>Jira: L1 Needs a person</title><link>https://agentdrives.com/tools/atlassian</link><guid>https://agentdrives.com/tools/atlassian#2026-10-14</guid><pubDate>Wed, 14 Oct 2026 12:00:00 GMT</pubDate><description>An agent cannot get into Jira on its own: both email sign-ups are stopped by reCAPTCHA (an invisible score refusal, then a visible checkbox). The docs, llms.txt and the official MCP server's OAuth metadata (PRM, DCR) are agent-friendly, but every capability sits behind an account, so none could be driven.</description></item>
<item><title>GitHub: L4 Runs on its own</title><link>https://agentdrives.com/tools/github</link><guid>https://agentdrives.com/tools/github#2026-10-13</guid><pubDate>Tue, 13 Oct 2026 12:00:00 GMT</pubDate><description>An agent cannot open a GitHub account: the sign-up page answers our signed agent with a DataDome block. On an existing account, the device-flow login (one browser approval) gives a token, and REST, GraphQL, gh and the official MCP server (the 28 Jul 2026 spec) run the core work: repos, commits, PRs, reviews, issues, Actions, Projects, three times each. Codespaces refuse our datacenter network; the Copilot cloud agent needs a paid plan.</description></item>
<item><title>Browserbase: L2 Gets in</title><link>https://agentdrives.com/tools/browserbase</link><guid>https://agentdrives.com/tools/browserbase#2026-10-13</guid><pubDate>Tue, 13 Oct 2026 12:00:00 GMT</pubDate><description>Browserbase sells browser sessions, search and fetch to agents with no account over x402 (v1) and MPP on its own domain; we paid one $0.01 session and the agent read it back and ended it. Everything else (API key, agents, functions, contexts) needs an account, and the sign-up form requires a phone number, so an agent stops there.</description></item>
<item><title>Steel: L4 Runs on its own</title><link>https://agentdrives.com/tools/steel</link><guid>https://agentdrives.com/tools/steel#2026-10-12</guid><pubDate>Mon, 12 Oct 2026 12:00:00 GMT</pubDate><description>An agent can do almost all of Steel through its API, SDK, CLI or official MCP server: sessions over CDP, scrape/screenshot/PDF, profiles, stored logins, files and extensions all worked and read back. Getting in needs a browser (email link sign-up and a dashboard key), CAPTCHA solving and proxies need $10 of paid balance bought by card, and pay-per-call x402 covers scrape, screenshot and PDF with no account.</description></item>
<item><title>TidyCal: L3 Does the work</title><link>https://agentdrives.com/tools/tidycal</link><guid>https://agentdrives.com/tools/tidycal#2026-10-12</guid><pubDate>Mon, 12 Oct 2026 12:00:00 GMT</pubDate><description>On TidyCal's free plan an agent can do the core scheduling in a browser: create a booking type, publish it, and book, reschedule and cancel an appointment. The REST API and the read-only MCP server need a paid plan, so nothing works headless after the docs. Sign-up is a reCAPTCHA web form that let our agent's browser through, and Pro is sold only through a hosted Stripe card checkout.</description></item>
<item><title>BigCommerce: L1 Needs a person</title><link>https://agentdrives.com/tools/bigcommerce</link><guid>https://agentdrives.com/tools/bigcommerce#2026-10-12</guid><pubDate>Mon, 12 Oct 2026 12:00:00 GMT</pubDate><description>An agent cannot open a BigCommerce store on its own: the trial sign-up form shows a visible reCAPTCHA Enterprise checkbox, there is no headless sign-up, and the first API token is created only in the control panel. Before sign-up, the docs serve agents well (llms.txt, Markdown pages, a docs-search MCP, 77 OpenAPI 3.1.0 specs), but no store capability could be reached.</description></item>
<item><title>Box: L1 Needs a person</title><link>https://agentdrives.com/tools/box</link><guid>https://agentdrives.com/tools/box#2026-10-12</guid><pubDate>Mon, 12 Oct 2026 12:00:00 GMT</pubDate><description>An agent cannot get into Box on its own: both documented sign-ups (personal and free developer) put an hCaptcha checkbox in front of account creation. Everything before the door is strong: Markdown docs with llms.txt, a public OpenAPI (3.0.2), a CLI and an official OAuth MCP server, but first credentials come from the Developer Console UI and paid plans only through a web checkout.</description></item>
<item><title>DocuSign: L1 Needs a person</title><link>https://agentdrives.com/tools/docusign</link><guid>https://agentdrives.com/tools/docusign#2026-10-12</guid><pubDate>Mon, 12 Oct 2026 12:00:00 GMT</pubDate><description>Docusign's docs, Swagger specs and MCP auth metadata are public, but both ways in (the free developer account and the free trial) stop at an Arkose Labs puzzle, so our agent never got an account. Even past it, robots.txt disallows the REST base path /restapi/, the Apps and Keys page and the demo MCP server to every agent, and integration keys are made only in the web UI.</description></item>
<item><title>Dropbox: L1 Needs a person</title><link>https://agentdrives.com/tools/dropbox</link><guid>https://agentdrives.com/tools/dropbox#2026-10-12</guid><pubDate>Mon, 12 Oct 2026 12:00:00 GMT</pubDate><description>Dropbox's only sign-up is a web form that shows an Arkose Labs puzzle, so an agent cannot get an account on its own and no capability could be tried. Without an account the agent surface is good: public API docs, llms.txt, an official MCP server with valid PRM, and headless OAuth client registration via DCR. Paid trials ask for a card, PayPal or IBAN.</description></item>
<item><title>Ecwid: L1 Needs a person</title><link>https://agentdrives.com/tools/ecwid</link><guid>https://agentdrives.com/tools/ecwid#2026-10-12</guid><pubDate>Mon, 12 Oct 2026 12:00:00 GMT</pubDate><description>An agent can read Ecwid's developer docs well (llms.txt, Markdown pages, a docs-search MCP), but it cannot open a store: the sign-up form shows a visible Cloudflare Turnstile checkbox, and there is no API sign-up. Even past that, the docs say the REST API works only for paid-plan stores, and tokens come only from the web control panel.</description></item>
<item><title>Heap: L1 Needs a person</title><link>https://agentdrives.com/tools/heap</link><guid>https://agentdrives.com/tools/heap#2026-10-12</guid><pubDate>Mon, 12 Oct 2026 12:00:00 GMT</pubDate><description>Heap's developer docs suit agents: an llms.txt, Markdown pages and an OpenAPI 3.1.0 definition per reference page. The only sign-up route is a web form, and it showed a reCAPTCHA image puzzle to our agent. No account was made and no capability could be driven.</description></item>
<item><title>Lemon Squeezy: L1 Needs a person</title><link>https://agentdrives.com/tools/lemonsqueezy</link><guid>https://agentdrives.com/tools/lemonsqueezy#2026-10-12</guid><pubDate>Mon, 12 Oct 2026 12:00:00 GMT</pubDate><description>An agent cannot sign up for Lemon Squeezy: the registration form needs a reCAPTCHA v2 checkbox, and there is no API sign-up. Without an account no core capability could be driven; only the docs, the public License API and the official JS SDK are reachable. API keys and products are dashboard-only.</description></item>
<item><title>Mollie: L1 Needs a person</title><link>https://agentdrives.com/tools/mollie</link><guid>https://agentdrives.com/tools/mollie#2026-10-12</guid><pubDate>Mon, 12 Oct 2026 12:00:00 GMT</pubDate><description>An agent cannot open a Mollie account: the sign-up form's reCAPTCHA rejected our agent's browser and showed a picture puzzle. Mollie's agent-facing docs are strong (llms.txt, markdown pages, Agent Skills, OpenAPI 3.1.0) and its official MCP server uses OAuth with CIMD, but API keys come only from the Web App. No capability could be tested.</description></item>
<item><title>n8n: L1 Needs a person</title><link>https://agentdrives.com/tools/n8n</link><guid>https://agentdrives.com/tools/n8n#2026-10-12</guid><pubDate>Mon, 12 Oct 2026 12:00:00 GMT</pubDate><description>n8n's docs are agent-friendly (llms.txt, Markdown pages, a docs MCP server) and the product offers an official MCP server, a public API and a CLI. Our agent verified its email but could not finish sign-up: the last form carries a visible Cloudflare Turnstile box, so no instance, key or workflow was reached. Even past sign-up, the docs say the public API is not on the free trial, and API keys and MCP tokens are made only in the web UI.</description></item>
<item><title>Pirsch: L1 Needs a person</title><link>https://agentdrives.com/tools/pirsch</link><guid>https://agentdrives.com/tools/pirsch#2026-10-12</guid><pubDate>Mon, 12 Oct 2026 12:00:00 GMT</pubDate><description>Pirsch has a large, well documented REST API (about 150 operations, including account delete) and a docs-linked third-party MCP server that speaks MCP (the 28 Jul 2026 spec), but an agent cannot get in: sign-up is a web form with an ALTCHA 'I'm not a robot' checkbox and there is no sign-up API. So no capability was driven. Paying is a hosted Stripe checkout; the 30-day trial needs no card.</description></item>
<item><title>Polar: L1 Needs a person</title><link>https://agentdrives.com/tools/polar</link><guid>https://agentdrives.com/tools/polar#2026-10-12</guid><pubDate>Mon, 12 Oct 2026 12:00:00 GMT</pubDate><description>Polar's docs are agent-ready (llms.txt, Markdown pages, OpenAPI 3.1.0, CLI, OAuth MCP server), but our agent could not get in: email sign-in sits behind a Cloudflare Turnstile widget that failed our agent's browser. API tokens are dashboard-only, so no capability could be driven.</description></item>
<item><title>Publer: L1 Needs a person</title><link>https://agentdrives.com/tools/publer</link><guid>https://agentdrives.com/tools/publer#2026-10-12</guid><pubDate>Mon, 12 Oct 2026 12:00:00 GMT</pubDate><description>An agent cannot get into Publer: the only sign-up is a web form whose reCAPTCHA showed our agent's browser a picture puzzle. Even with an account, the API and official MCP server are Business/Enterprise only and keys are made in the web UI. The docs are very agent-friendly (llms.txt, markdown pages, ask endpoint).</description></item>
<item><title>Render: L1 Needs a person</title><link>https://agentdrives.com/tools/render</link><guid>https://agentdrives.com/tools/render#2026-10-12</guid><pubDate>Mon, 12 Oct 2026 12:00:00 GMT</pubDate><description>Render's agent docs are excellent: llms.txt, Markdown for every page, a docs-search API and a hosted MCP server. But an agent cannot get in: the email sign-up shows an hCaptcha puzzle, API keys are made only in the dashboard, MCP OAuth needs a pre-registered client, and robots.txt disallows the whole API host and the dashboard. No capability could be driven.</description></item>
<item><title>ScrapingBee: L1 Needs a person</title><link>https://agentdrives.com/tools/scrapingbee</link><guid>https://agentdrives.com/tools/scrapingbee#2026-10-12</guid><pubDate>Mon, 12 Oct 2026 12:00:00 GMT</pubDate><description>ScrapingBee's only sign-up is a web form with a visible reCAPTCHA v2 checkbox, so an agent cannot get an account or API key alone. Docs (llms.txt), an official remote MCP server (18 tools, the 25 Nov 2025 MCP spec) and a CLI are agent-friendly once a human hands over a key. No OpenAPI and no agent payment rail.</description></item>
<item><title>SerpApi: L1 Needs a person</title><link>https://agentdrives.com/tools/serpapi</link><guid>https://agentdrives.com/tools/serpapi#2026-10-12</guid><pubDate>Mon, 12 Oct 2026 12:00:00 GMT</pubDate><description>SerpApi has agent-friendly docs (llms.txt, Markdown pages) and a current, stateless MCP server, but an agent cannot get an account: the sign-up form shows a reCAPTCHA picture puzzle and there is no API sign-up. Without a key no search works, and robots.txt also disallows the documented /search endpoint. Only the keyless parts worked: locations lookup and the MCP engine schemas.</description></item>
<item><title>Wix: L1 Needs a person</title><link>https://agentdrives.com/tools/wix</link><guid>https://agentdrives.com/tools/wix#2026-10-12</guid><pubDate>Mon, 12 Oct 2026 12:00:00 GMT</pubDate><description>Wix documents a broad REST API, SDK, CLI and an official MCP server, with markdown docs for agents. An agent cannot open an account on its own: the sign-up form shows a reCAPTCHA Enterprise checkbox to our agent's browser, and every route to a key or token needs an account. Nothing past the docs could be driven.</description></item>
<item><title>Plausible Analytics: L3 Does the work</title><link>https://agentdrives.com/tools/plausible</link><guid>https://agentdrives.com/tools/plausible#2026-10-11</guid><pubDate>Sun, 11 Oct 2026 12:00:00 GMT</pubDate><description>An agent can open a 30-day trial (no card) in a browser and then read its stats headless over the Stats API. Setup is web-only on the trial: sites, goals, funnels, shared links, API keys and account delete. The write API (Sites API) is Enterprise only. The Events API silently drops events from our agent (202 with `x-plausible-dropped: 1`). Core coverage: 5 of 8 core capabilities done and verified (, 03, 04, 05 and 07). was partial, failed, and (funnel analysis) is also partial: the funnel's CRUD steps (create/rename/delete) were done, but the dashboard funnel report itself, the capability's defining check, timed out when opened and was never verified.</description></item>
<item><title>Netlify: L2 Gets in</title><link>https://agentdrives.com/tools/netlify</link><guid>https://agentdrives.com/tools/netlify#2026-10-11</guid><pubDate>Sun, 11 Oct 2026 12:00:00 GMT</pubDate><description>An agent can deploy a static site to Netlify with no account (netlify deploy --allow-anonymous) and use the Image CDN on it, and the docs are agent-ready (llms.txt, Markdown pages, OpenAPI, MCP server card). Opening an account failed: the email sign-up form silently reset after an invisible reCAPTCHA Enterprise check, so no token, MCP, functions or project management were reachable.</description></item>
<item><title>Acuity Scheduling: L1 Needs a person</title><link>https://agentdrives.com/tools/acuityscheduling</link><guid>https://agentdrives.com/tools/acuityscheduling#2026-10-11</guid><pubDate>Sun, 11 Oct 2026 12:00:00 GMT</pubDate><description>Acuity's docs are agent-friendly (llms.txt, Markdown pages, OpenAPI 3.1.0), but an agent cannot get in: the Squarespace sign-up form stalled silently behind an invisible reCAPTCHA Enterprise check, and robots.txt disallows /api/*, which covers the whole documented REST API. No capability could be driven; paying is a web-only plan choice after a no-card trial.</description></item>
<item><title>Amplitude: L1 Needs a person</title><link>https://agentdrives.com/tools/amplitude</link><guid>https://agentdrives.com/tools/amplitude#2026-10-11</guid><pubDate>Sun, 11 Oct 2026 12:00:00 GMT</pubDate><description>Amplitude is unusually well documented for agents (llms.txt, Markdown pages, OpenAPI 3.1, an AI catalog, an official OAuth MCP server and a public Docs MCP), but an agent cannot get in: the only sign-up is a web form whose invisible reCAPTCHA rejected our agent's browser. No product capability could be driven; paying needs a card in the web app and deleting an org is a monthly support ticket.</description></item>
<item><title>Close: L1 Needs a person</title><link>https://agentdrives.com/tools/close</link><guid>https://agentdrives.com/tools/close#2026-10-11</guid><pubDate>Sun, 11 Oct 2026 12:00:00 GMT</pubDate><description>Close's sign-up refused our agent's browser through an invisible reCAPTCHA check, with no challenge a human could solve, so we never got an account, key or token. Its public agent surface is good: llms.txt, an OpenAPI 3.1.0 spec, Markdown docs and an official MCP server with OAuth DCR that worked headless. No agent payment rail; the trial needs no card.</description></item>
<item><title>Framer: L1 Needs a person</title><link>https://agentdrives.com/tools/framer</link><guid>https://agentdrives.com/tools/framer#2026-10-11</guid><pubDate>Sun, 11 Oct 2026 12:00:00 GMT</pubDate><description>Framer's docs are very agent-readable (llms.txt, markdown on every page) and it offers a CLI, a Server API package and an OAuth MCP endpoint. But our signed agent could not open an account: the email step is refused by an invisible Castle risk check (403 'Access denied by policy') with no challenge to hand to a human, so nothing behind the login could be tried.</description></item>
<item><title>Gorgias: L1 Needs a person</title><link>https://agentdrives.com/tools/gorgias</link><guid>https://agentdrives.com/tools/gorgias#2026-10-11</guid><pubDate>Sun, 11 Oct 2026 12:00:00 GMT</pubDate><description>An agent cannot open a Gorgias account: the sign-up form's invisible Cloudflare Turnstile never cleared for our agent's browser, and no API sign-up exists. Outside the account Gorgias is agent-ready: an official MCP server with 155 tools and OAuth metadata, markdown API docs with OpenAPI 3.1.0, and a no-card trial. Behind the door, tenant robots.txt disallows the REST API for every agent.</description></item>
<item><title>Mailgun: L1 Needs a person</title><link>https://agentdrives.com/tools/mailgun</link><guid>https://agentdrives.com/tools/mailgun#2026-10-11</guid><pubDate>Sun, 11 Oct 2026 12:00:00 GMT</pubDate><description>An agent cannot get into Mailgun: the free sign-up form was rejected by an invisible reCAPTCHA (&quot;Could not validate reCaptcha response&quot;) and there is no API sign-up. Even with an account, robots.txt on api.mailgun.net disallows every path for all user agents. The docs are agent-friendly (llms.txt, .md pages, OpenAPI 3.1.0) and there is an official local MCP server with 74 tools on the 25 Nov 2025 spec.</description></item>
<item><title>MongoDB Atlas: L1 Needs a person</title><link>https://agentdrives.com/tools/mongodb</link><guid>https://agentdrives.com/tools/mongodb#2026-10-11</guid><pubDate>Sun, 11 Oct 2026 12:00:00 GMT</pubDate><description>An agent cannot get into MongoDB Atlas on its own: the sign-up form's invisible reCAPTCHA rejected our signed agent (INVALID_CAPTCHA, shown as a 'server error'), and robots.txt disallows the Atlas CLI's sign-up page. Outside the account it is strong for agents: llms.txt, Markdown docs, a 522-operation OpenAPI, and an official MCP server that speaks MCP (the 28 Jul 2026 spec) with CIMD-capable OAuth.</description></item>
<item><title>Squarespace: L1 Needs a person</title><link>https://agentdrives.com/tools/squarespace</link><guid>https://agentdrives.com/tools/squarespace#2026-10-11</guid><pubDate>Sun, 11 Oct 2026 12:00:00 GMT</pubDate><description>An agent cannot create a Squarespace account: the web-only sign-up, guarded by invisible reCAPTCHA Enterprise, returned a 401 'username or password is incorrect' and showed nothing. Without an account, only the official no-auth MCP server (domain search and name ideas) and the Markdown developer docs work. Sites, store, invoices, scheduling and campaigns are behind sign-in and mostly web-UI-only.</description></item>
<item><title>Umami: L3 Does the work</title><link>https://agentdrives.com/tools/umami</link><guid>https://agentdrives.com/tools/umami#2026-10-08</guid><pubDate>Thu, 08 Oct 2026 12:00:00 GMT</pubDate><description>An agent can sign up for Umami Cloud's free plan without a bot check and use the whole dashboard in a browser: websites, goals, funnels, notes, links, pixels, shares, export and account delete. The API and MCP server need a Pro key, and hits our self-identified agent sent to /api/send were dropped as bot traffic, so every report it read was empty.</description></item>
<item><title>Taskade: L1 Needs a person</title><link>https://agentdrives.com/tools/taskade</link><guid>https://agentdrives.com/tools/taskade#2026-10-08</guid><pubDate>Thu, 08 Oct 2026 12:00:00 GMT</pubDate><description>An agent cannot get into Taskade on its own: the only sign-up is a web form with a visible Cloudflare Turnstile widget to do it. Even with an account, robots.txt disallows /api/, the base of both documented APIs, and the hosted MCP is for paid workspaces only. The docs themselves are very agent-friendly: llms.txt indexes and a Markdown copy of every page.</description></item>
<item><title>Cloudinary: L4 Runs on its own</title><link>https://agentdrives.com/tools/cloudinary</link><guid>https://agentdrives.com/tools/cloudinary#2026-10-06</guid><pubDate>Tue, 06 Oct 2026 12:00:00 GMT</pubDate><description>One unauthenticated API call gives an agent a working Cloudinary cloud, and from there all 9 core capabilities ran headless through REST, the CLI and three remote MCP servers, verified by reading state back. The Console is where an agent stops: its password setup has a reCAPTCHA, upgrading is a card form there, and deleting the account takes a support ticket.</description></item>
<item><title>DocuSeal: L4 Runs on its own</title><link>https://agentdrives.com/tools/docuseal</link><guid>https://agentdrives.com/tools/docuseal#2026-10-06</guid><pubDate>Tue, 06 Oct 2026 12:00:00 GMT</pubDate><description>An agent signed up, got an API key (after an email code) and ran the full template-to-signed-PDF workflow headless through the documented REST API; all 7 core capabilities verified, with signer steps done in a browser by design. On the free plan the API runs as the Developer Sandbox; production API, webhooks and team features are Pro via Stripe Checkout with a card, and account deletion is web-only.</description></item>
<item><title>Zulip: L4 Runs on its own</title><link>https://agentdrives.com/tools/zulip</link><guid>https://agentdrives.com/tools/zulip#2026-10-06</guid><pubDate>Tue, 06 Oct 2026 12:00:00 GMT</pubDate><description>Zulip Cloud Free can be run almost entirely by an agent through its documented REST API: all 7 core capabilities and most secondary ones were done and read back, and the organization was deactivated by API. Only the sign-up form needs a browser, for an invisible ALTCHA proof-of-work that cleared on its own. No MCP, llms.txt or agent payment rail; paying is Stripe Checkout with a card.</description></item>
<item><title>Firecrawl: L4 Runs on its own</title><link>https://agentdrives.com/tools/firecrawl</link><guid>https://agentdrives.com/tools/firecrawl#2026-10-06</guid><pubDate>Tue, 06 Oct 2026 12:00:00 GMT</pubDate><description>Firecrawl's core works for an agent: scrape, crawl, map, search, extract, actions, agent and parse all ran and read back on the free plan, and scrape/search/parse even work keyless through MCP or the API. Getting your own key still needs a browser (web sign-up, PKCE email link, dashboard or cli-auth Authorize), since agent registration only accepts WorkOS ID-JAG. Leaving is web-only: the agent deleted the account in the dashboard, and we could not confirm the deletion took effect.</description></item>
<item><title>Pipedream: L4 Runs on its own</title><link>https://agentdrives.com/tools/pipedream</link><guid>https://agentdrives.com/tools/pipedream#2026-10-06</guid><pubDate>Tue, 06 Oct 2026 12:00:00 GMT</pubDate><description>Pipedream Connect's core (connected accounts, tool runs via REST and MCP, proxy, triggers, webhooks) worked headless and verified on the free plan once credentials existed. Sign-up and the first OAuth client need the web app, buying a plan needs a card in Stripe Checkout, and account deletion is web-only and showed a 500 while succeeding.</description></item>
<item><title>Browserless: L4 Runs on its own</title><link>https://agentdrives.com/tools/browserless</link><guid>https://agentdrives.com/tools/browserless#2026-10-06</guid><pubDate>Tue, 06 Oct 2026 12:00:00 GMT</pubDate><description>With a token, an agent can do nearly everything in Browserless headless: REST, BrowserQL, Puppeteer, the Agent Run API and a 16-tool MCP server all worked on the Free plan and were verified. Sign-up (email OTP, no CAPTCHA), getting the token, and cancel/delete are web UI only, and there is no agent payment rail. Persisted session state did not survive a reconnect, and profile creation failed with an unclear error.</description></item>
<item><title>SignWell: L3 Does the work</title><link>https://agentdrives.com/tools/signwell</link><guid>https://agentdrives.com/tools/signwell#2026-10-06</guid><pubDate>Tue, 06 Oct 2026 12:00:00 GMT</pubDate><description>SignWell's documented REST API, official CLI and stdio MCP server let an agent do the whole core flow: draft, fields, signing order, send, track, signed PDF, templates and webhooks, free in test mode. Sign-up and email verification worked headless, but the API key is only in the web settings behind a mandatory onboarding wizard, and leaving (cancel plus delete) is a web-only flow with a retention offer. There is no agent payment rail, only an in-app Stripe card form.</description></item>
<item><title>Craft: L3 Does the work</title><link>https://agentdrives.com/tools/craft</link><guid>https://agentdrives.com/tools/craft#2026-10-06</guid><pubDate>Tue, 06 Oct 2026 12:00:00 GMT</pubDate><description>Craft has a rich documented space API (44 operations) and an official OAuth MCP server. The agent signed up, made an API link and approved MCP itself in its browser, then drove 7 of 9 core capabilities: documents, folders, tasks, daily notes, collections and whiteboards headless, publishing in the browser. Sign-up, credentials, publish, share, the Assistant and account deletion are web-only; MCP is on the older 25 Nov 2025 spec (DCR only), a task update answers a false 404, and cross-document regex ignores capital letters.</description></item>
<item><title>Coda: L3 Does the work</title><link>https://agentdrives.com/tools/coda</link><guid>https://agentdrives.com/tools/coda#2026-10-06</guid><pubDate>Tue, 06 Oct 2026 12:00:00 GMT</pubDate><description>The agent signed up, verified its email and made an API token itself in a browser; from there it ran Coda (now Superhuman Docs) through the REST API and the official MCP server: a doc, pages, a typed table with formula and button columns, rows, sharing and a Pack, all read back. 7 of the 10 core capabilities are done and verified; AI columns, automations and the AI assistant building tables were not tested. The gaps are the browser-only sign-up and token, an MCP server on the older 25 Nov 2025 spec that redirects doc calls with an empty 307, publishing that needs a maker profile made in the web app, a card-only checkout, and account deletion: the re-auth page on grammarly.com showed no form in our agent's browser (one try).</description></item>
<item><title>Stripe: L3 Does the work</title><link>https://agentdrives.com/tools/stripe</link><guid>https://agentdrives.com/tools/stripe#2026-10-06</guid><pubDate>Tue, 06 Oct 2026 12:00:00 GMT</pubDate><description>An agent gets working Stripe test keys with one CLI command and no account, then drives payments, Checkout, Elements, subscriptions, invoices, coupons, refunds, webhooks and the official MCP server headless (6 of 9 core capabilities). The unclaimed-sandbox key is restricted, and turning it into a full account means a sign-up form that showed a visible hCaptcha puzzle, so metering, Connect, Terminal and every Dashboard feature stayed out of reach. Agent-native payment rails (x402 v2 and MPP) exist, but only on Stripe's Climate side endpoint.</description></item>
<item><title>Mattermost: L3 Does the work</title><link>https://agentdrives.com/tools/mattermost</link><guid>https://agentdrives.com/tools/mattermost#2026-10-06</guid><pubDate>Tue, 06 Oct 2026 12:00:00 GMT</pubDate><description>An agent can sign up for a 30-day Mattermost Cloud Enterprise trial without a card, but only in the browser. After that the documented REST API v4 does almost all of the chat product headless: channels, posts, threads, files, search, webhooks, guests, groups and plugins. The AI Agents and MCP need an LLM key, calls are browser media, buying goes through sales, and no way to delete the workspace was found.</description></item>
<item><title>Railway: L3 Does the work</title><link>https://agentdrives.com/tools/railway</link><guid>https://agentdrives.com/tools/railway#2026-10-06</guid><pubDate>Tue, 06 Oct 2026 12:00:00 GMT</pubDate><description>Railway is unusually agent-ready on paper (llms.txt, markdown docs, auth.md, API catalog, PRM, CIMD, device flow, official MCP), and an agent can get a free VM and a project token with no account via `ssh railway.new`, then add databases, set variables, open TCP proxies, read logs and metrics, and run sandboxes. But account sign-up sits behind a visible Cloudflare Turnstile, and the anonymous token cannot deploy code, so deploying an app, MCP and paying all need a human.</description></item>
<item><title>TickTick: L3 Does the work</title><link>https://agentdrives.com/tools/ticktick</link><guid>https://agentdrives.com/tools/ticktick#2026-10-06</guid><pubDate>Tue, 06 Oct 2026 12:00:00 GMT</pubDate><description>With a personal API key, an agent can drive TickTick's tasks, lists, tags, reminders, repeats, comments, Kanban, focus records and habit check-ins through the documented REST API or the official 28 Jul 2026 MCP server. Sign-up, key creation and account deletion need the web app; countdowns cannot be created and API-made habits did not show in the app. Premium is a card-only Stripe Checkout.</description></item>
<item><title>Penpot: L3 Does the work</title><link>https://agentdrives.com/tools/penpot</link><guid>https://agentdrives.com/tools/penpot#2026-10-06</guid><pubDate>Tue, 06 Oct 2026 12:00:00 GMT</pubDate><description>An agent can get through Penpot's whole access ladder headless with the documented RPC API: sign up, verify, token, first design, delete account. It can drive most design work through low-level update-file changes, comments, teams, libraries, templates and .penpot export/import. The official MCP server works but needs a live browser tab running the Penpot plugin; prototype interactions need Transit encoding, and token changes do not reach the shapes.</description></item>
<item><title>Mixpanel: L3 Does the work</title><link>https://agentdrives.com/tools/mixpanel</link><guid>https://agentdrives.com/tools/mixpanel#2026-10-06</guid><pubDate>Tue, 06 Oct 2026 12:00:00 GMT</pubDate><description>An agent can sign up for Mixpanel's free plan in a browser without a CAPTCHA, but the first credential (a service account) exists only in the web UI. With it, ingestion, raw export, feature flags with targeting, experiments, Lexicon and boards (via the official 66-tool MCP server) all work headless. Every analysis query (Insights, funnels, retention, MCP Run-Query) returns HTTP 402 on the free plan, upgrading needs a card in a Stripe form, and deleting the organization is a web button with a 90-day delay.</description></item>
<item><title>Browse AI: L3 Does the work</title><link>https://agentdrives.com/tools/browse</link><guid>https://agentdrives.com/tools/browse#2026-10-06</guid><pubDate>Tue, 06 Oct 2026 12:00:00 GMT</pubDate><description>Browse AI has a clean, documented REST API for running robots, monitors, bulk runs and webhooks; an agent drives all of that headless once a robot exists. Sign-up, API keys and robot training are web UI only (no CAPTCHA met); the agent did them in its own browser. 4 of 8 core capabilities done and verified; pagination failed, screenshots and change alerts were not tried.</description></item>
<item><title>Shopify: L2 Gets in</title><link>https://agentdrives.com/tools/shopify</link><guid>https://agentdrives.com/tools/shopify#2026-10-06</guid><pubDate>Tue, 06 Oct 2026 12:00:00 GMT</pubDate><description>Without any account, an agent can create a temporary Shopify store from the CLI and run the Admin GraphQL API on it: products, variants, inventory, theme files, pages, metaobjects, bundles, shipping rates and discounts all worked and read back. A real account is behind a Cloudflare 'Verify you are human' challenge, so orders, customers, payments, plans and keeping the store need a human. The official Setup MCP only accepts OAuth from ChatGPT, Claude and Perplexity.</description></item>
<item><title>Fly.io: L2 Gets in</title><link>https://agentdrives.com/tools/fly</link><guid>https://agentdrives.com/tools/fly#2026-10-06</guid><pubDate>Tue, 06 Oct 2026 12:00:00 GMT</pubDate><description>On Fly.io an agent can drive Sprites end to end over the documented REST API and the official Sprites MCP: create, exec, checkpoint/restore and a public URL. The Machines side stopped right after sign-up: Fly's risk check flagged the new account and every app, Machine and Postgres action asked for a card, although the docs promise a no-card trial. Sign-up, verification and credentials need a browser; the agent-facing docs (llms.txt, Markdown, OpenAPI 3.1, auth.md) are excellent.</description></item>
<item><title>Zapier: L2 Gets in</title><link>https://agentdrives.com/tools/zapier</link><guid>https://agentdrives.com/tools/zapier#2026-10-06</guid><pubDate>Tue, 06 Oct 2026 12:00:00 GMT</pubDate><description>An agent can sign up and authorise Zapier in a browser (no CAPTCHA, no email confirmation needed) and then work headless through the SDK CLI and the official MCP server: we created, updated and read back records in Zapier Tables, ran a Tables action through MCP, and saved and used an MCP Skill. Zaps, the core product, have no headless route for a normal account, and in our agent's browser the editor's Copilot left the draft Zap unfinished. Account deletion is web only.</description></item>
<item><title>Gumroad: L2 Gets in</title><link>https://agentdrives.com/tools/gumroad</link><guid>https://agentdrives.com/tools/gumroad#2026-10-06</guid><pubDate>Tue, 06 Oct 2026 12:00:00 GMT</pubDate><description>An agent gets a Gumroad account and a token with a few browser steps (sign-up form, token button), then works fully headless through a ~80-operation REST API, an official CLI and an official MCP server: drafts, variants, discounts, files, upsells, webhooks. It cannot sell anything: publishing any product needs a payout method with identity verification (phone, date of birth, address, ID), and emails, workflows and service products are held back by sales and account-age gates.</description></item>
<item><title>Webflow: L2 Gets in</title><link>https://agentdrives.com/tools/webflow</link><guid>https://agentdrives.com/tools/webflow#2026-10-06</guid><pubDate>Tue, 06 Oct 2026 12:00:00 GMT</pubDate><description>Webflow has strong agent surfaces: Markdown docs with llms.txt, an OpenAPI 3.1 spec, and an official remote MCP server on the current 28 Jul 2026 protocol. Sign-up and MCP OAuth worked in a browser, but on the free plan an agent cannot create a site: the dashboard shows a HUMAN press-and-hold check and the Create Site API is Enterprise-only. Without a site, no core capability could be driven.</description></item>
<item><title>ActiveCampaign: L1 Needs a person</title><link>https://agentdrives.com/tools/activecampaign</link><guid>https://agentdrives.com/tools/activecampaign#2026-10-06</guid><pubDate>Tue, 06 Oct 2026 12:00:00 GMT</pubDate><description>ActiveCampaign's docs are agent-ready (llms.txt, markdown negotiation, OpenAPI 3.1.0, a docs MCP on the 28 Jul 2026 spec, auth.md, AI catalog), but an agent cannot get in: the free-trial sign-up hits a Cloudflare Turnstile challenge and credentials only come from the app UI. No product capability was driven.</description></item>
<item><title>Asana: L1 Needs a person</title><link>https://agentdrives.com/tools/asana</link><guid>https://agentdrives.com/tools/asana#2026-10-06</guid><pubDate>Tue, 06 Oct 2026 12:00:00 GMT</pubDate><description>Asana has a large REST API, an official OAuth MCP server and agent-readable Markdown docs, but no way for an agent to get in: the sign-up form's reCAPTCHA Enterprise rejected our agent's browser and showed a visible checkbox. Credentials need the web developer console or a human OAuth consent, so no capability could be driven.</description></item>
<item><title>Backblaze B2: L1 Needs a person</title><link>https://agentdrives.com/tools/backblaze</link><guid>https://agentdrives.com/tools/backblaze#2026-10-06</guid><pubDate>Tue, 06 Oct 2026 12:00:00 GMT</pubDate><description>An agent cannot open a Backblaze account: both sign-up pages show a reCAPTCHA v2 'Security Check' to our agent's browser, so we drove no capability. Without an account the agent side looks good: Markdown docs, llms.txt, and an official MCP server that speaks MCP (the 28 Jul 2026 spec) with 40 tools. Cancel and delete are web-console only, per the docs.</description></item>
<item><title>Baserow: L1 Needs a person</title><link>https://agentdrives.com/tools/baserow</link><guid>https://agentdrives.com/tools/baserow#2026-10-06</guid><pubDate>Tue, 06 Oct 2026 12:00:00 GMT</pubDate><description>Baserow has a large documented REST API (OpenAPI 3.0.3, 424 operations), an official MCP server and llms.txt, but an agent cannot create an account: sign-up, by API and by web form, needs a Cloudflare Turnstile token. Without an account nothing beyond the docs could be driven; payment is card-only through the signed-in web UI.</description></item>
<item><title>beehiiv: L1 Needs a person</title><link>https://agentdrives.com/tools/beehiiv</link><guid>https://agentdrives.com/tools/beehiiv#2026-10-06</guid><pubDate>Tue, 06 Oct 2026 12:00:00 GMT</pubDate><description>beehiiv's docs are agent-friendly (llms.txt, Markdown twins, OpenAPI 3.1.0, docs and marketing MCPs) and it has an official OAuth MCP server. An agent cannot get in: Cloudflare hard-blocks app.beehiiv.com/signup and /login for our signed agent, headless and in a browser, and API keys can only be made in that app. No core capability could be driven.</description></item>
<item><title>Buffer: L1 Needs a person</title><link>https://agentdrives.com/tools/buffer</link><guid>https://agentdrives.com/tools/buffer#2026-10-06</guid><pubDate>Tue, 06 Oct 2026 12:00:00 GMT</pubDate><description>Buffer offers a GraphQL API, an official MCP server, a CLI with agent skill files and Markdown docs, but an agent cannot get an account: the web-only sign-up shows an hCaptcha picture puzzle. Without an account there is no API key, so no capability could be driven.</description></item>
<item><title>Cal.com: L1 Needs a person</title><link>https://agentdrives.com/tools/cal</link><guid>https://agentdrives.com/tools/cal#2026-10-06</guid><pubDate>Tue, 06 Oct 2026 12:00:00 GMT</pubDate><description>Cal.com is very well prepared for agents on paper: AI catalog, MCP server card, auth.md, agent skills, llms.txt with markdown docs and a 356-operation OpenAPI. But sign-up has no API and the web form shows a Cloudflare Turnstile that did not clear for our signed agent browser, so the drive never got credentials and drove no core capability.</description></item>
<item><title>Calendly: L1 Needs a person</title><link>https://agentdrives.com/tools/calendly</link><guid>https://agentdrives.com/tools/calendly#2026-10-06</guid><pubDate>Tue, 06 Oct 2026 12:00:00 GMT</pubDate><description>Calendly documents its API well for agents (llms.txt, Markdown pages, OpenAPI 3.1, hosted MCP with OAuth and DCR), but creating an account stops at a visible reCAPTCHA v2 after the sign-up form. So no credentials and no scheduling action could be tested.</description></item>
<item><title>Chatwoot: L1 Needs a person</title><link>https://agentdrives.com/tools/chatwoot</link><guid>https://agentdrives.com/tools/chatwoot#2026-10-06</guid><pubDate>Tue, 06 Oct 2026 12:00:00 GMT</pubDate><description>Chatwoot's developer surface is strong for agents: llms.txt, Markdown pages, OpenAPI 3.1.0, an official CLI with an agent skill, and a modern docs MCP. But Cloud sign-up shows a visible hCaptcha puzzle, so no account, token or core action was possible on this drive.</description></item>
<item><title>Crisp: L1 Needs a person</title><link>https://agentdrives.com/tools/crisp</link><guid>https://agentdrives.com/tools/crisp#2026-10-06</guid><pubDate>Tue, 06 Oct 2026 12:00:00 GMT</pubDate><description>Crisp has a broad REST API, official SDKs and an official MCP server, but an agent cannot get in on its own: the workspace sign-up shows a visible hCaptcha puzzle and every working token is issued inside the workspace dashboard. Without a human we reached only docs, the MCP tool list and an empty plugin dev-token call; no core capability could be driven.</description></item>
<item><title>Fathom Analytics: L1 Needs a person</title><link>https://agentdrives.com/tools/usefathom</link><guid>https://agentdrives.com/tools/usefathom#2026-10-06</guid><pubDate>Tue, 06 Oct 2026 12:00:00 GMT</pubDate><description>Fathom Analytics has a clean, agent-friendly API surface (llms.txt, Markdown API reference, OpenAPI 3.1.0), but an agent cannot get in: the only way to start is a 7-day trial whose sign-up form requires a credit card and ZIP code, and API tokens are made in the web app. We could not create an account, so no core capability was driven; only the free UTM builder and the public demo dashboard worked.</description></item>
<item><title>folk: L1 Needs a person</title><link>https://agentdrives.com/tools/folk</link><guid>https://agentdrives.com/tools/folk#2026-10-06</guid><pubDate>Tue, 06 Oct 2026 12:00:00 GMT</pubDate><description>folk documents its API and official MCP server well (llms.txt, Markdown pages, OpenAPI 3.1.0, PRM and CIMD/DCR on the MCP OAuth). An agent can start sign-up in the browser, but the emailed magic link runs Stytch Device Fingerprinting, which rejected our agent's browser twice with a 'Login Error'. Without a session there is no API key or MCP token, so no CRM capability could be driven.</description></item>
<item><title>Formspree: L1 Needs a person</title><link>https://agentdrives.com/tools/formspree</link><guid>https://agentdrives.com/tools/formspree#2026-10-06</guid><pubDate>Tue, 06 Oct 2026 12:00:00 GMT</pubDate><description>An agent cannot get into Formspree on its own: sign-up is a web form, and Register raised a reCAPTCHA v2 picture puzzle. Every way to create a form (dashboard, claim URL, CLI deploy key) needs that account. The docs serve agents well (llms.txt, Markdown articles), but there is no MCP server, OpenAPI spec or agent auth.</description></item>
<item><title>FreshBooks: L1 Needs a person</title><link>https://agentdrives.com/tools/freshbooks</link><guid>https://agentdrives.com/tools/freshbooks#2026-10-06</guid><pubDate>Tue, 06 Oct 2026 12:00:00 GMT</pubDate><description>An agent cannot get into FreshBooks alone: the sign-up page on auth.freshbooks.com showed our agent's browser a visible reCAPTCHA image puzzle, so no capability was driven. Without an account an agent finds good HTML docs, SDKs, webhooks, an official OAuth-protected MCP server with correct Protected Resource Metadata, and can register its own OAuth client via DCR, but every data route needs a logged-in user.</description></item>
<item><title>Freshdesk: L1 Needs a person</title><link>https://agentdrives.com/tools/freshdesk</link><guid>https://agentdrives.com/tools/freshdesk#2026-10-06</guid><pubDate>Tue, 06 Oct 2026 12:00:00 GMT</pubDate><description>Freshdesk has a documented REST API and an official MCP server (API-key auth, Growth plan and up), but an agent cannot get an account: the sign-up page on www.freshworks.com is behind a Cloudflare managed challenge that our signed agent did not pass. Docs are readable headless. The MCP 401 points to Protected Resource Metadata that returns 404, and there is no OpenAPI, no agent payment rail and no billing API.</description></item>
<item><title>Front: L1 Needs a person</title><link>https://agentdrives.com/tools/front</link><guid>https://agentdrives.com/tools/front#2026-10-06</guid><pubDate>Tue, 06 Oct 2026 12:00:00 GMT</pubDate><description>Front's docs are well prepared for agents (llms.txt, Markdown pages, OpenAPI, an official MCP server), but an agent cannot get in: the only sign-up route is a web form that requires a phone number, and API tokens and MCP OAuth clients are only made inside an account. No core capability could be driven.</description></item>
<item><title>Kit: L1 Needs a person</title><link>https://agentdrives.com/tools/kit</link><guid>https://agentdrives.com/tools/kit#2026-10-06</guid><pubDate>Tue, 06 Oct 2026 12:00:00 GMT</pubDate><description>Kit's developer docs are agent-friendly (llms.txt, Markdown pages, OpenAPI 3.0.3, a docs MCP on the 28 Jul 2026 spec), but app.kit.com/users/signup and all of kit.com answer our signed agent with a Cloudflare 'Verify you are human' challenge, so no account, key or core task was reached. Credentials come only from the web app (API key) or an OAuth consent by a signed-in creator; Kit's docs say the API and the Kit MCP are not available on the free plan.</description></item>
<item><title>Klaviyo: L1 Needs a person</title><link>https://agentdrives.com/tools/klaviyo</link><guid>https://agentdrives.com/tools/klaviyo#2026-10-06</guid><pubDate>Tue, 06 Oct 2026 12:00:00 GMT</pubDate><description>Klaviyo has a strong agent surface on paper: a 345-operation REST API with an OpenAPI spec, Markdown docs, an llms.txt, and an official MCP server (remote with OAuth/CIMD, local with an API key). An agent cannot get in on its own: the free sign-up form makes a phone number mandatory and there is no API or agent sign-up, so no capability could be driven. The local MCP server still speaks MCP (the 25 Nov 2025 spec) and there is no agent payment rail.</description></item>
<item><title>Mailchimp: L1 Needs a person</title><link>https://agentdrives.com/tools/mailchimp</link><guid>https://agentdrives.com/tools/mailchimp#2026-10-06</guid><pubDate>Tue, 06 Oct 2026 12:00:00 GMT</pubDate><description>Mailchimp's developer docs are agent-friendly: llms.txt, Markdown pages, agent skills and a docs-search MCP (legacy, its tool failing). An agent cannot get in: sign-up is web-only and its reCAPTCHA showed a visible image puzzle, so no API key and no capability could be driven.</description></item>
<item><title>MailerLite: L1 Needs a person</title><link>https://agentdrives.com/tools/mailerlite</link><guid>https://agentdrives.com/tools/mailerlite#2026-10-06</guid><pubDate>Tue, 06 Oct 2026 12:00:00 GMT</pubDate><description>MailerLite has a strong agent surface on paper: Markdown docs with llms.txt, an official CLI, six SDKs and a hosted OAuth MCP server with 77 tools. An agent cannot get in on its own: the only sign-up is a web form behind a visible Cloudflare Turnstile, so nothing in the product was driven.</description></item>
<item><title>Mailtrap: L1 Needs a person</title><link>https://agentdrives.com/tools/mailtrap</link><guid>https://agentdrives.com/tools/mailtrap#2026-10-06</guid><pubDate>Tue, 06 Oct 2026 12:00:00 GMT</pubDate><description>Mailtrap has strong agent surfaces on paper: llms.txt and Markdown docs, OpenAPI 3.1.0 (136 operations), an official CLI and a stdio MCP server with 125 tools. But sign-up is a web form that showed our agent's browser a visible reCAPTCHA checkbox, and tokens are only made in the web app, so an agent cannot get in on its own and no core capability could be driven.</description></item>
<item><title>Make: L1 Needs a person</title><link>https://agentdrives.com/tools/make</link><guid>https://agentdrives.com/tools/make#2026-10-06</guid><pubDate>Tue, 06 Oct 2026 12:00:00 GMT</pubDate><description>Make documents a full REST API, CLI, SDK and hosted MCP server, and its docs are agent-friendly (llms.txt, markdown). But sign-up, login and OAuth consent all run through www.make.com pages behind a Cloudflare managed challenge that did not clear for our signed agent, so no account, token or capability could be driven.</description></item>
<item><title>Moneybird: L1 Needs a person</title><link>https://agentdrives.com/tools/moneybird</link><guid>https://agentdrives.com/tools/moneybird#2026-10-06</guid><pubDate>Tue, 06 Oct 2026 12:00:00 GMT</pubDate><description>Moneybird has unusually good agent tooling on paper: an official MCP server with OAuth (PRM, DCR and CIMD), an official CLI, a 297-operation OpenAPI 3.1 spec and llms.txt. But an agent cannot get in on its own: the only sign-up is a web form behind invisible reCAPTCHA, which gave our agent's browser no token, no puzzle and no error, so no account, token or API call was possible and no core capability could be driven.</description></item>
<item><title>Perplexity API: L1 Needs a person</title><link>https://agentdrives.com/tools/perplexity</link><guid>https://agentdrives.com/tools/perplexity#2026-10-06</guid><pubDate>Tue, 06 Oct 2026 12:00:00 GMT</pubDate><description>Perplexity's docs are agent-ready (llms.txt, markdown pages, six OpenAPI specs, an official hosted MCP server with RFC 9728 metadata and CIMD), but an agent cannot get in: console.perplexity.ai and www.perplexity.ai answer our signed agent with a Cloudflare 'Verify you are human' challenge, also in a real browser. Without a key every API, CLI and MCP call returns 401, so no capability was driven.</description></item>
<item><title>Pinata: L1 Needs a person</title><link>https://agentdrives.com/tools/pinata</link><guid>https://agentdrives.com/tools/pinata#2026-10-06</guid><pubDate>Tue, 06 Oct 2026 12:00:00 GMT</pubDate><description>Pinata's docs are very agent-friendly (llms.txt, markdown, a modern docs MCP), and it runs a first-party MPP endpoint that sells account-free IPFS uploads and downloads. But sign-up is a web form behind a visible Cloudflare Turnstile and API keys come only from the dashboard, so our agent got no account: it could only read public CIDs through the gateway.</description></item>
<item><title>Plain: L1 Needs a person</title><link>https://agentdrives.com/tools/plain</link><guid>https://agentdrives.com/tools/plain#2026-10-06</guid><pubDate>Tue, 06 Oct 2026 12:00:00 GMT</pubDate><description>Plain has a public GraphQL schema, SDK, CLI, an official OAuth MCP server and markdown docs, but an agent cannot create an account: the WorkOS sign-up page shows a visible Cloudflare Turnstile and the email sign-in path answered 'Access blocked'. No capability could be driven; billing (7-day no-card trial, plan change by API, card in a Hyperline portal) is graded from docs only.</description></item>
<item><title>Postmark: L1 Needs a person</title><link>https://agentdrives.com/tools/postmarkapp</link><guid>https://agentdrives.com/tools/postmarkapp#2026-10-06</guid><pubDate>Tue, 06 Oct 2026 12:00:00 GMT</pubDate><description>Postmark's agent-facing docs are unusually complete (llms.txt, AI catalog, auth.md, api-catalog, Agent Skills, MCP server card) and the test token lets an agent dry-run sends with no account. But sign-up is a web form whose reCAPTCHA escalated to a picture challenge for our agent's browser, and tokens can only be issued by a human in the UI, so no real send, template or domain work was possible.</description></item>
<item><title>Resend: L1 Needs a person</title><link>https://agentdrives.com/tools/resend</link><guid>https://agentdrives.com/tools/resend#2026-10-06</guid><pubDate>Tue, 06 Oct 2026 12:00:00 GMT</pubDate><description>Resend publishes agent docs (llms.txt, markdown pages, OpenAPI, auth.md, skills, CLI, OAuth MCP server), but our agent could not get an account: the sign-up form returned a generic server error twice, with no visible challenge to hand to a human. Without an account there is no API key, so none of the capabilities could be driven.</description></item>
<item><title>SavvyCal: L1 Needs a person</title><link>https://agentdrives.com/tools/savvycal</link><guid>https://agentdrives.com/tools/savvycal#2026-10-06</guid><pubDate>Tue, 06 Oct 2026 12:00:00 GMT</pubDate><description>SavvyCal documents a REST API, but an agent cannot get in: the sign-up form shows a visible hCaptcha puzzle. Without an account there is no token, so no core capability could be driven; billing, cancel and delete are web-only.</description></item>
<item><title>SendGrid: L1 Needs a person</title><link>https://agentdrives.com/tools/sendgrid</link><guid>https://agentdrives.com/tools/sendgrid#2026-10-06</guid><pubDate>Tue, 06 Oct 2026 12:00:00 GMT</pubDate><description>An agent can read all of SendGrid's docs headless (llms.txt, Markdown pages, OpenAPI 3.1.0, a docs-only MCP server) but cannot get an account: the Twilio sign-up form shows a Cloudflare Turnstile check to take it. Without an account no API key exists, so no capability could be driven; paying is card-in-console and deleting the account goes through Support.</description></item>
<item><title>tawk.to: L1 Needs a person</title><link>https://agentdrives.com/tools/tawk</link><guid>https://agentdrives.com/tools/tawk#2026-10-06</guid><pubDate>Tue, 06 Oct 2026 12:00:00 GMT</pubDate><description>An agent can read tawk.to's docs (llms.txt, developer portal, help center), but the only sign-up route is a web form behind Cloudflare Turnstile. It rejected our agent's browser, so no capability could be tried. Even with an account, the REST API needs a human-approved access request, and there is no OpenAPI, no official MCP server and no machine payment rail.</description></item>
<item><title>Teamwork.com: L1 Needs a person</title><link>https://agentdrives.com/tools/teamwork</link><guid>https://agentdrives.com/tools/teamwork#2026-10-06</guid><pubDate>Tue, 06 Oct 2026 12:00:00 GMT</pubDate><description>Teamwork.com has an official MCP server that speaks MCP (the 28 Jul 2026 spec), OAuth metadata and a 429-operation Swagger spec, but an agent cannot get in: the sign-up form requires a phone number and there is no headless sign-up or credential path. No capability could be driven.</description></item>
<item><title>Todoist: L1 Needs a person</title><link>https://agentdrives.com/tools/todoist</link><guid>https://agentdrives.com/tools/todoist#2026-10-06</guid><pubDate>Tue, 06 Oct 2026 12:00:00 GMT</pubDate><description>Todoist has a strong agent surface on paper: an OpenAPI 3.1.0 REST API, an official OAuth MCP server with PRM and CIMD/DCR, a CLI and SDK. But an agent cannot get in on its own: the email sign-up form runs an invisible Cloudflare Turnstile that rejected our agent's browser to complete it, so no account, token or capability could be driven.</description></item>
<item><title>Trello: L1 Needs a person</title><link>https://agentdrives.com/tools/trello</link><guid>https://agentdrives.com/tools/trello#2026-10-06</guid><pubDate>Tue, 06 Oct 2026 12:00:00 GMT</pubDate><description>Trello has a full REST API (OpenAPI 3.0.0, 261 operations) and an official remote MCP server with current OAuth discovery (PRM, CIMD), but both need a signed-in Atlassian account. The Atlassian sign-up form showed our agent's browser a visible reCAPTCHA, so no capability could be driven. Paying is credit card in the web UI only.</description></item>
<item><title>Turso: L1 Needs a person</title><link>https://agentdrives.com/tools/turso</link><guid>https://agentdrives.com/tools/turso#2026-10-06</guid><pubDate>Tue, 06 Oct 2026 12:00:00 GMT</pubDate><description>Turso's docs are very agent-friendly (llms.txt, Markdown pages, OpenAPI, a hosted OAuth MCP server with CIMD), and its embedded engine runs locally through the official SDK with no account: SQL, vectors, FTS and CDC all worked. The cloud product stopped at sign-up: the only route is a Clerk web form that shows a visible Cloudflare Turnstile on submit, so no account, token or cloud database was made.</description></item>
<item><title>Typeform: L1 Needs a person</title><link>https://agentdrives.com/tools/typeform</link><guid>https://agentdrives.com/tools/typeform#2026-10-06</guid><pubDate>Tue, 06 Oct 2026 12:00:00 GMT</pubDate><description>Typeform has a documented REST API and an official MCP server with proper OAuth discovery (PRM, CIMD, DCR), but an agent cannot get an account: our agent's browser sign-up was silently denied by Typeform's registration inline hook (E0000135) with a misleading 'you might already have an account' message. Without an account there is no token, so no form, response or analytics capability could be driven.</description></item>
<item><title>Typefully: L1 Needs a person</title><link>https://agentdrives.com/tools/typefully</link><guid>https://agentdrives.com/tools/typefully#2026-10-06</guid><pubDate>Tue, 06 Oct 2026 12:00:00 GMT</pubDate><description>Typefully has an agent-ready surface: an OpenAPI 3.1.0 REST API, an official MCP server with OAuth (CIMD) or API-key auth, llms.txt and Markdown docs, and API and MCP on the free plan. An agent cannot get in on its own: email sign-up shows an interactive Cloudflare Turnstile, and keys and tokens need the web settings or a browser consent page. So nothing was driven.</description></item>
<item><title>Wrike: L1 Needs a person</title><link>https://agentdrives.com/tools/wrike</link><guid>https://agentdrives.com/tools/wrike#2026-10-06</guid><pubDate>Tue, 06 Oct 2026 12:00:00 GMT</pubDate><description>Wrike's docs are agent-ready: llms.txt, Markdown pages, an api-catalog with OpenAPI 3.0.1, and an official MCP server with Protected Resource Metadata. An agent cannot get an account, though: the free-trial registration endpoint sits behind a Cloudflare managed challenge. No API, MCP or product capability could be driven.</description></item>
<item><title>Xero: L1 Needs a person</title><link>https://agentdrives.com/tools/xero</link><guid>https://agentdrives.com/tools/xero#2026-10-06</guid><pubDate>Tue, 06 Oct 2026 12:00:00 GMT</pubDate><description>Xero stops an agent at sign-up: both the free trial and the free developer login require a phone number, so no account, credentials or capability could be reached. The developer surface is strong (official MCP server with 51 tools, CLI, OpenAPI 3.0.0, Demo Company), but every route needs an OAuth client from a logged-in account, and the MCP server is stdio-only on the the older 25 Nov 2025 spec protocol.</description></item>
<item><title>Zendesk: L1 Needs a person</title><link>https://agentdrives.com/tools/zendesk</link><guid>https://agentdrives.com/tools/zendesk#2026-10-06</guid><pubDate>Tue, 06 Oct 2026 12:00:00 GMT</pubDate><description>Zendesk's free 14-day trial needs no card, but its sign-up form requires a phone number, so an agent cannot create an account; the only API route to create accounts is reseller-only. Discovery is decent: OpenAPI 3.0.3 and an official per-account MCP server with a server card and RFC 9728 metadata, on legacy MCP (the 18 Jun 2025 spec) with DCR-only OAuth.</description></item>
<item><title>Carrd: L0 Read-only</title><link>https://agentdrives.com/tools/carrd</link><guid>https://agentdrives.com/tools/carrd#2026-10-06</guid><pubDate>Tue, 06 Oct 2026 12:00:00 GMT</pubDate><description>Carrd has no API, CLI or MCP: everything runs in the web builder. A browser agent can build a site and sign up inline from the Publish panel (the /signup page is behind a Cloudflare challenge). Email verification then shows a reCAPTCHA picture challenge, so the site never went live and the no-card trial stayed locked. The site and the account were deleted in the browser.</description></item>
<item><title>Later: L0 Read-only</title><link>https://agentdrives.com/tools/later</link><guid>https://agentdrives.com/tools/later#2026-10-06</guid><pubDate>Tue, 06 Oct 2026 12:00:00 GMT</pubDate><description>An agent cannot get into Later Social: app.later.com, which serves sign-up, log-in and checkout, shows our signed agent a Cloudflare Turnstile check. Later Social has no public API, CLI or MCP server; the only Later API is the sales-gated Influence Reporting API.</description></item>
<item><title>zcal: L0 Read-only</title><link>https://agentdrives.com/tools/zcal</link><guid>https://agentdrives.com/tools/zcal#2026-10-06</guid><pubDate>Tue, 06 Oct 2026 12:00:00 GMT</pubDate><description>zcal has no public API, CLI or MCP server; everything happens in its web app. Sign-up shows a Cloudflare Turnstile that rejected our agent's browser, so an agent could not get an account. Its help docs are agent-friendly: llms.txt and Markdown pages.</description></item>
<item><title>Anchor Browser: L4 Runs on its own</title><link>https://agentdrives.com/tools/anchorbrowser</link><guid>https://agentdrives.com/tools/anchorbrowser#2026-10-05</guid><pubDate>Mon, 05 Oct 2026 12:00:00 GMT</pubDate><description>Anchor Browser lets an agent in with no account at all: a short text puzzle over HTTP returns an API key, and from there sessions, CDP control, natural-language tasks, saved tasks, managed logins, profiles, files, webhooks and batches all worked headless on the free tier (9 of 10 core capabilities verified). The stops are buying more credits (dashboard only, no payment rail or billing API) and deleting the self-made project; the MCP server is still on the 25 Nov 2025 spec.</description></item>
<item><title>NocoDB: L4 Runs on its own</title><link>https://agentdrives.com/tools/nocodb</link><guid>https://agentdrives.com/tools/nocodb#2026-10-03</guid><pubDate>Sat, 03 Oct 2026 12:00:00 GMT</pubDate><description>Once it holds a token, an agent can run most of NocoDB on the free plan: bases, tables, fields, records, views, sharing, CSV import, workflows, interfaces and dashboards all worked, mostly over the official MCP server, and NocoAI built a table from one sentence in the web app. Getting in needs a browser (sign-up form, emailed code, token page), a workflow needs a human click to go live, and several REST groups are plan-gated or unreachable with any token.</description></item>
<item><title>Brevo: L2 Gets in</title><link>https://agentdrives.com/tools/brevo</link><guid>https://agentdrives.com/tools/brevo#2026-10-03</guid><pubDate>Sat, 03 Oct 2026 12:00:00 GMT</pubDate><description>An agent can sign up for Brevo's free plan in a browser, verify by email headless, and get an MCP or REST token through OAuth with one browser consent, then manage contacts, lists, CRM deals and records, templates, webhooks and eCommerce data over a 282-tool MCP server and a 286-operation REST API. It cannot send: new accounts need Brevo's manual activation and an authenticated sender domain, and the web app stays behind an organization-address step, so API keys, the editor and account deletion are out of reach.</description></item>
<item><title>PostHog: L1 Needs a person</title><link>https://agentdrives.com/tools/posthog</link><guid>https://agentdrives.com/tools/posthog#2026-10-03</guid><pubDate>Sat, 03 Oct 2026 12:00:00 GMT</pubDate><description>PostHog is very well documented for agents: llms.txt, Markdown for every page, a public OpenAPI spec, an MCP server with OAuth discovery and an auth.md manifest. But our agent could not get an account: the documented headless sign-up (the wizard's provisioning) returned 403, and the web form ends in a Cloudflare Turnstile. Nothing past the docs could be driven.</description></item>
<item><title>Attio: L4 Runs on its own</title><link>https://agentdrives.com/tools/attio</link><guid>https://agentdrives.com/tools/attio#2026-10-02</guid><pubDate>Fri, 02 Oct 2026 12:00:00 GMT</pubDate><description>Once a token exists, an agent can run almost all of Attio's CRM core over a clean, well-documented REST API and an official 41-tool MCP server: every core capability was done and verified. Getting there takes a browser: sign-up with an emailed code, token creation in settings, and one OAuth consent click for MCP. Workflows, sequences and billing are browser-only, and SQL is Enterprise-only.</description></item>
<item><title>Basecamp: L4 Runs on its own</title><link>https://agentdrives.com/tools/basecamp</link><guid>https://agentdrives.com/tools/basecamp#2026-10-02</guid><pubDate>Fri, 02 Oct 2026 12:00:00 GMT</pubDate><description>Basecamp is one of the most agent-ready products we've driven: a plain form POST signs up a free account, and the official CLI with its built-in MCP server, the REST API and the SDKs covered all nine core capabilities. The one browser step is approving the OAuth device code, and each token reaches only the account chosen there. Paying, cancelling and deleting are web-only, and paid trials need no card.</description></item>
<item><title>Formbricks: L4 Runs on its own</title><link>https://agentdrives.com/tools/formbricks</link><guid>https://agentdrives.com/tools/formbricks#2026-10-02</guid><pubDate>Fri, 02 Oct 2026 12:00:00 GMT</pubDate><description>An agent can run Formbricks nearly end to end. After a browser sign-up with no CAPTCHA and a one-time API key from the UI, the REST API and the official OAuth MCP server cover the whole survey lifecycle: create, edit with logic, publish, collect, read, update and delete responses, plus webhooks and targeting. All 8 core capabilities were done and verified. What stays in the browser: sign-up, key creation, tags, segments, billing and account deletion. Follow-ups, workflows and Unify Feedback need paid plans beyond the no-card trial.</description></item>
<item><title>Shortcut: L4 Runs on its own</title><link>https://agentdrives.com/tools/shortcut</link><guid>https://agentdrives.com/tools/shortcut#2026-10-02</guid><pubDate>Fri, 02 Oct 2026 12:00:00 GMT</pubDate><description>Once the agent had signed up and created an API token in its browser, Shortcut is very agent-friendly: an accurate v4 OpenAPI, clear JSON errors and an official MCP server with dynamic OAuth registration let us create, move, link and clean up stories, epics, iterations, objectives and docs headless. Sign-up, token creation, turning on Docs and roadmap placement need the browser, buying has no agent route, and deleting the account failed silently in the UI.</description></item>
<item><title>Buttondown: L4 Runs on its own</title><link>https://agentdrives.com/tools/buttondown</link><guid>https://agentdrives.com/tools/buttondown#2026-10-02</guid><pubDate>Fri, 02 Oct 2026 12:00:00 GMT</pubDate><description>Buttondown is very agent-friendly once the key is in hand: a complete OpenAPI, clear errors that name the fix, and on the free plan we drafted, scheduled, sent, personalised, archived, exported, imported and bulk-edited through the API, all verified by reading back. Sign-up, the first API key and account deletion need the dashboard (no CAPTCHA, so a browser agent manages), and automations, RSS and tags are behind a card-only paid plan with no billing API.</description></item>
<item><title>Fillout: L4 Runs on its own</title><link>https://agentdrives.com/tools/fillout</link><guid>https://agentdrives.com/tools/fillout#2026-10-02</guid><pubDate>Fri, 02 Oct 2026 12:00:00 GMT</pubDate><description>An agent can sign up and get a key in a browser, then handle submissions headless (create, list, search, delete, webhooks) through a small, accurate REST API. The Zite MCP connects through OAuth DCR but has no form tools, so building forms (fields, logic, calculations, publish, workflows) takes the web builder, where Fillout's own Form Agent made those edits from a single prompt. Payments and scheduling need Stripe or a Google/Outlook calendar, which we did not have. Upgrading uses an embedded Stripe card form.</description></item>
<item><title>Twenty: L4 Runs on its own</title><link>https://agentdrives.com/tools/twenty</link><guid>https://agentdrives.com/tools/twenty#2026-10-02</guid><pubDate>Fri, 02 Oct 2026 12:00:00 GMT</pubDate><description>Once a workspace exists, Twenty is one of the most agent-ready CRMs: its official MCP server (324 tools) and REST/GraphQL let an agent run records, custom objects, views, workflows, AI-agent steps and dashboards end to end. Sign-up, onboarding and the first API key need a browser, but invisible reCAPTCHA let our agent through and a 7-day trial needs no card. Paying is web-only, and the card step did not open for our agent's browser.</description></item>
<item><title>Pipedrive: L3 Does the work</title><link>https://agentdrives.com/tools/pipedrive</link><guid>https://agentdrives.com/tools/pipedrive#2026-10-02</guid><pubDate>Fri, 02 Oct 2026 12:00:00 GMT</pubDate><description>Pipedrive is very drivable once an agent is in: through the free developer sandbox (one browser form, no CAPTCHA) and an API token, we created, moved, converted, searched, filtered and deleted CRM data end to end via REST v1/v2 and the official OAuth-protected MCP server. The regular trial sign-up was refused with a generic error (400; an invisible reCAPTCHA is on the page), email sending, automations, reports and billing have no API, and there is no agent payment rail or account deletion.</description></item>
<item><title>Convex: L3 Does the work</title><link>https://agentdrives.com/tools/convex</link><guid>https://agentdrives.com/tools/convex#2026-10-02</guid><pubDate>Fri, 02 Oct 2026 12:00:00 GMT</pubDate><description>Convex is one of the most agent-ready backends to build on. It has llms.txt and markdown docs, an OpenAPI Management API, an Agent Mode guide, and a CLI that starts a local backend with no account; on that backend every core backend task worked on the first try, and so did file storage, text and vector search, custom-JWT auth and live subscriptions. The hosted cloud is closed to agents at the first door: auth.convex.dev/sign-up shows a visible Cloudflare 'Verify you are human' challenge, so the drive got no cloud project, no deploy key, no MCP session and no purchase. The open-source self-hosted backend installed with Docker in under a minute and the CLI could drive it fully.</description></item>
<item><title>monday.com: L3 Does the work</title><link>https://agentdrives.com/tools/monday</link><guid>https://agentdrives.com/tools/monday#2026-10-02</guid><pubDate>Fri, 02 Oct 2026 12:00:00 GMT</pubDate><description>monday.com is unusually agent-ready once an agent is inside: llms.txt, agent skills, and a hosted MCP with 98 tools that accepts the API token directly. Through it we built boards, items, workflows, dashboards, forms, docs, agents and Vibe apps, and verified each by reading it back. Getting in was harder than advertised: the agent sign-up API was down (503) and the plain sign-up showed a visible reCAPTCHA, but the agent browser sign-up worked without a challenge. Sidekick, Kanban/timeline views, automation creation on trial with a personal token, paying and account deletion are not reachable headless.</description></item>
<item><title>Neon: L2 Gets in</title><link>https://agentdrives.com/tools/neon</link><guid>https://agentdrives.com/tools/neon#2026-10-02</guid><pubDate>Fri, 02 Oct 2026 12:00:00 GMT</pubDate><description>Neon is unusually agent-friendly without an account: auth.md and `neon claim create` gave a working Postgres database, Managed Better Auth and a Data API in seconds, and we drove SQL, extensions, autoscaling, scale-to-zero, auth sign-ups, RLS-protected REST CRUD and neon.ts deploys headless. The real account is out of reach (a Cloudflare interstitial on console sign-up), and claimable projects block branching, restore, roles, functions, storage and most of the Management API until a human claims them, so 5 of 11 non-gated core capabilities were verified.</description></item>
<item><title>PlanetScale: L2 Gets in</title><link>https://agentdrives.com/tools/planetscale</link><guid>https://agentdrives.com/tools/planetscale#2026-10-02</guid><pubDate>Fri, 02 Oct 2026 12:00:00 GMT</pubDate><description>An agent gets into PlanetScale entirely headless: sign-up form without CAPTCHA, email verification, CLI device login, service tokens, REST API and a 25-tool hosted MCP server, all with unusually agent-friendly JSON errors and an agent setup guide. The wall is the first real action: there is no free plan, so creating a database (and with it every core capability) needs a card attached through Stripe Checkout. Account deletion works only in the web UI.</description></item>
<item><title>Postiz: L2 Gets in</title><link>https://agentdrives.com/tools/postiz</link><guid>https://agentdrives.com/tools/postiz#2026-10-02</guid><pubDate>Fri, 02 Oct 2026 12:00:00 GMT</pubDate><description>Postiz is built for agents on paper (llms.txt, OpenAPI, CLI, official MCP with dynamic client registration), and sign-up plus email verification went through in the browser with no CAPTCHA. But there is no free plan and the 7-day trial needs a card, so the API and CLI refuse with 'No subscription found' and no channel or post can be created.</description></item>
<item><title>Copper: L1 Needs a person</title><link>https://agentdrives.com/tools/copper</link><guid>https://agentdrives.com/tools/copper#2026-10-02</guid><pubDate>Fri, 02 Oct 2026 12:00:00 GMT</pubDate><description>Copper's REST API is solid: once an agent has a key it can run the core CRM loop of contacts, deals, stages, won/lost, tasks, activities, custom fields and tags headlessly and verify every step. Getting in is the problem. The visible sign-up is Google-only. Email features depend on Gmail, reports and automations are UI-only, and there is no agent payment rail or self-serve account deletion.</description></item>
<item><title>Invoice Ninja: L1 Needs a person</title><link>https://agentdrives.com/tools/invoiceninja</link><guid>https://agentdrives.com/tools/invoiceninja#2026-10-02</guid><pubDate>Fri, 02 Oct 2026 12:00:00 GMT</pubDate><description>Invoice Ninja has a broad, well-documented REST API (OpenAPI, 365 operations) and the production API answers agents from a datacenter without bot checks, but an agent cannot get an account: the only sign-up is a web form with a visible Cloudflare Turnstile checkbox. The documented demo sandbox is also behind a Cloudflare challenge, and REST API tokens are a Pro feature, so no capability could be driven.</description></item>
<item><title>Jotform: L1 Needs a person</title><link>https://agentdrives.com/tools/jotform</link><guid>https://agentdrives.com/tools/jotform#2026-10-02</guid><pubDate>Fri, 02 Oct 2026 12:00:00 GMT</pubDate><description>Jotform has a broad documented REST API, SDKs and an official OAuth MCP server, but our agent never got credentials. Documented sign-up fails on an undocumented terms field and the web sign-up shows reCAPTCHA v2.</description></item>
<item><title>Tally: L4 Runs on its own</title><link>https://agentdrives.com/tools/tally</link><guid>https://agentdrives.com/tools/tally#2026-10-01</guid><pubDate>Thu, 01 Oct 2026 12:00:00 GMT</pubDate><description>Once a browser sign-up has produced an API key, Tally is very easy for an agent to work with. The REST API, the official MCP server (`https://api.tally.so/mcp`, 26 tools) and the markdown docs let an agent create, edit, publish, read and clean up forms headless, and almost everything worked on the first try. The weak points are at the edges. Sign-up, email verification and API key creation happen only in the web app. Pro-gated endpoints answer `401 You are not authorized` rather than saying a plan is needed. Drop-off analytics on the Free plan returned invented sample numbers. Upgrading and account deletion happen only in the browser.

**Scores:** overall 70 · coverage 64 · access 55 · reliability 78 · docs 86 · core coverage 100%</description></item>
<item><title>Notion: L1 Needs a person</title><link>https://agentdrives.com/tools/notion</link><guid>https://agentdrives.com/tools/notion#2026-10-01</guid><pubDate>Thu, 01 Oct 2026 12:00:00 GMT</pubDate><description>Notion has an excellent agent surface on paper: REST API with OpenAPI, the ntn CLI, an official hosted MCP server with dynamic client registration, webhooks and markdown docs with llms.txt. The agent could not get in: sign-up is browser-only, the first verification code never arrived, and every later request, including one from a fresh address, got 'Signup is not allowed.' from the server. No core capability could be exercised.</description></item>
</channel></rss>