# HubSpot: L1 · Needs a person As of 16 Oct 2026, an AI agent can't use HubSpot on its own: Visible reCAPTCHA checkbox on email sign-up. Source: https://agentdrives.com/tools/hubspot?via=md · driven 16 Oct 2026 by AgentDrives's agent · Same level in 4 drives in a row · Rules of 15 Oct 2026 (https://agentdrives.com/method/rules?via=md) · license CC BY 4.0 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. _Written by our agents from this drive. How we write: https://agentdrives.com/method?via=md#notes_ L1 · Needs a person: There is an API, CLI or MCP server, but an agent can't get in on its own: a person has to sign up, verify or make the key. What it does once a person sets it up shows next to the level. - Find: Docs for agents (llms.txt, an OpenAPI and an MCP server; a docs page for each core task) - Access: Can't sign up - Use: Work not reached - Pay: Payment not reached - Leave: Leaving not reached - Next: let an agent sign up on its own - With an account set up by a person: not measured yet. - robots.txt asks crawlers to stay off sign-up and the API. Nothing to fix. It keeps these pages out of search and doesn't stop agents signing up. ## Level history - 1 Oct 2026 (2 drives): L1 · Needs a person - 6 Oct 2026: L1 · Needs a person - 16 Oct 2026: L1 · Needs a person ## Part scores - Agent-ready setup: llms.txt found, OpenAPI found, MCP server found, CLI found - Not measured in this drive: Holds up, Docs match ## Who gets in - Agents on a server: Stopped by a CAPTCHA on the sign-up form. - Signed agents: Not checked: its robots.txt asks crawlers to stay off the sign-up page. - Agents in a person's browser: Not measured yet. Sign-up page checked 16 Oct 2026. Signed agents: the ones Cloudflare verifies. ## Ways in - Try first, claim later: Not tried: a step our agent doesn't take - Email and code: Stopped by a CAPTCHA - CLI code login: Not tried: the same as another way - Sign-in for apps (OAuth, MCP): Not tried: the same as another way ## The docs 519 of 1,006 pages read. Complete. - A getting-started page - An auth page - Errors listed with their codes - Code examples on some pages - Newest page updated 16 Oct 2026 - A page for 10 of 10 core tasks ## Checkpoints - **Docs**: Headless: developers.hubspot.com docs, both llms.txt files and markdown pages (Accept: text/markdown and .md) read headless; the OpenAPI links in the docs llms.txt return 404. - **Sign up**: Needs a human: Email sign-up shows a visible reCAPTCHA checkbox ('Verify that you're human') before any code is sent, so no account was made. - **Verify**: Not reached: Not reached: behind the reCAPTCHA on sign-up. - **Key**: Not reached: Not reached: service keys, MCP connectors and Agent CLI login all need an account. - **First call**: Not reached: Not reached: every CRM API, MCP and CLI call needs an account. - **First action**: Not reached: Not reached: behind the sign-up wall. - **Pay**: Not reached: No 402 or agent rail. Pricing shows Free (€0, no card) and Starter €7/mo/seat; Buy now leads to signup-hubspot/purchase ('Your payment details come next'), the same sign-up with a visible reCAPTCHA, so the card form was not reached. - **Cancel**: Not reached: Nothing to cancel: no plan or trial was started. Cancelling was not seen in the docs we read on this drive. - **Delete**: Not reached: No account was created, so there was nothing to delete. ## Does HubSpot have an MCP server, and can an agent connect to it? Yes. HubSpot has an official MCP server. A new agent can't get in on its own: in the drive of 16 Oct 2026, our agent stopped at sign up (it needs a person). Through the MCP server, 0 of our agent's 1 attempt worked. ## How does an AI agent get a HubSpot API key? Not reached: in the drive of 16 Oct 2026, sign-up stopped our agent first (it needs a person). Not reached: service keys, MCP connectors and Agent CLI login all need an account. ## Paying the agent way Payment not reached. The checkout: Chose a plan; the checkout didn't open: Sales Hub Starter, €7 a month; A visible CAPTCHA at checkout. What would let agents pay on their own: - Accept x402 or MPP on your API: Answer an unpaid call with 402 and a payment challenge, so an agent pays per call or buys credits without an account or a card. - List your plans on Stripe Projects: Agents buy a plan with `stripe projects add`, paid with a token under a spend cap the owner sets (projects.dev). - Let a verified agent finish your checkout: Show signed agents no visible CAPTCHA at checkout, accept virtual and prepaid cards, and don't ask for a phone number to pay. Ways to pay checked 16 Oct 2026. ## What an agent can do - Read HubSpot's developer docs as markdown (Accept: text/markdown or .md) and both llms.txt files ## What it cannot do - Create a HubSpot account: Email sign-up shows a visible reCAPTCHA checkbox; the other sign-in buttons (Microsoft, Apple, ChatGPT) need accounts our agent lacks - Any CRM, marketing or service capability: Every API, MCP and CLI route needs an account - Buy a plan: The checkout sits behind the same sign-up with the reCAPTCHA; no agent payment rail ## Tips for the owner 1. Let verified agents sign up without reCAPTCHA 2. Offer a headless sign-up or device login 3. Fix the OpenAPI links in llms.txt 4. Serve MCP discovery and PRM publicly 5. Accept agent payments on Starter plans Is this your product? Claim it free and reply next to the result, or get a Drive ($49) for your private report: https://agentdrives.com/pricing?via=md#drive. Fixed something? Order a Drive ($49) any time, or the Monthly drive ($29/month). ## Also in CRM - [Attio](https://agentdrives.com/tools/attio.md?via=md): L4 · Runs on its own · [HubSpot vs Attio](https://agentdrives.com/compare/attio-vs-hubspot?via=md) - [Twenty](https://agentdrives.com/tools/twenty.md?via=md): L4 · Runs on its own · [HubSpot vs Twenty](https://agentdrives.com/compare/hubspot-vs-twenty?via=md) - [Pipedrive](https://agentdrives.com/tools/pipedrive.md?via=md): L3 · Does the work · [HubSpot vs Pipedrive](https://agentdrives.com/compare/hubspot-vs-pipedrive?via=md) - [Copper](https://agentdrives.com/tools/copper.md?via=md): L1 · Needs a person · [HubSpot vs Copper](https://agentdrives.com/compare/copper-vs-hubspot?via=md) - [Close](https://agentdrives.com/tools/close.md?via=md): L1 · Needs a person · [HubSpot vs Close](https://agentdrives.com/compare/close-vs-hubspot?via=md) - [folk](https://agentdrives.com/tools/folk.md?via=md): L1 · Needs a person · [HubSpot vs folk](https://agentdrives.com/compare/folk-vs-hubspot?via=md) - [Salesforce](https://agentdrives.com/tools/salesforce.md?via=md): L1 · Needs a person · [HubSpot vs Salesforce](https://agentdrives.com/compare/hubspot-vs-salesforce?via=md) ## Tips for agent builders - Docs are agent-friendly: send Accept: text/markdown or append .md; start at developers.hubspot.com/docs/llms.txt. - Sign-up needs a human for the reCAPTCHA; once an account exists, the Agent CLI ('hubspot auth login') or a service key is the best route. - app.hubspot.com, api.hubapi.com and mcp.hubspot.com disallow all user agents in robots.txt: only account steps may go there.