AgentsReady
Verified deep dive · SaaS

HubSpot

Run the agent liveReport a change
6 minTime to key
NoNo-human path
2Human gates
7/10Onboarding score
Admin approvalEmail verification

Fastest path to a key

  1. Sign up for free CRM (or free developer account) at hubspot.com with Google/Microsoft or email
  2. Phone OTP
    Verify email; complete onboarding questionnaire (company, role; phone may be requested)
  3. Agent: curl -fsSL https://api.hubapi.com/hub/cli/backend/hub-cli/latest/install.sh | sh; run 'hubspot auth login' (browser OAuth, user-scoped)
  4. For a raw token: Settings > Integrations > Service keys (account service key) or legacy private app > copy pat-na1-... token
  5. Call https://api.hubapi.com/crm/v3/objects/contacts with Bearer token (or 'hubspot whoami')
  6. Working API key

Biggest gap

Remote MCP has no DCR - outside the pre-built Claude/ChatGPT connectors, users must create an MCP connector app to get OAuth credentials.

Worth copying

An Agent CLI built for agents: self-describing --help, dry-run mode for every write, installable skills, and an install prompt to paste into the agent.

Sources (7) · checked 2026-10-11
61Readiness score / 100
L3 Agent-operableBeats 82% of 1,846 companies
Access20/20
Context11/20
Interfaces20/32
Onboarding8/19
Trust2/9
llms.txt · root
MCP · https://mcp.hubspot.com/

Biggest gains

  1. +8 Machine-readable API spec. Publish an OpenAPI spec at a stable URL like /openapi.json and link it from llms.txt.
  2. +6 Docs available as markdown. Serve every docs page as .md, or honour Accept: text/markdown.
  3. +6 Agents can self-register OAuth clients. Support dynamic client registration (RFC 7591) or client ID metadata documents so MCP clients connect in one click.
All 20 checks
  • PASSAgents get the real page, not a bot wall10
  • PASSrobots.txt lets user-triggered agents in6
  • PASSContent is server-rendered4
  • PASSllms.txt exists8
  • FAILllms-full.txt exists3
  • FAILDocs available as markdown6
  • PASSSitemap2
  • PASSStructured metadata1
  • PASSPublic developer docs4
  • FAILMachine-readable API spec8
  • PASSRemote MCP server for the product12
  • PASSDocs MCP or searchable docs4
  • FAILSDKs and a CLI4
  • PASSOAuth discovery metadata5
  • FAILAgents can self-register OAuth clients6
  • FAILSelf-serve API keys5
  • PASSFree tier or test mode3
  • FAILAgent manifests4
  • PASSsecurity.txt2
  • FAILPublic status page3

Your fix pack: 9 changes, up to +39 points

Each change is ready to paste, filled in for hubspot.com, with a command to check it worked. Or hand the whole list to your coding agent.

An OpenAPI spec is the contract agents and SDK generators build against. Without it they guess from prose.

Where: https://hubspot.com/openapi.json, linked from llms.txt and the API reference
// Serve the spec your API framework already generates (FastAPI: /openapi.json is built in).
// Next.js: app/openapi.json/route.ts
import spec from "@/openapi/openapi.json";
export const GET = () => Response.json(spec, { headers: { "Access-Control-Allow-Origin": "*" } });

// Every operation needs: operationId, summary, description, request/response examples,
// and the auth scheme (components.securitySchemes) so agents know how to send the key.
Check it worked:curl -s https://hubspot.com/openapi.json | head -c 200

Add the badge to your README

AgentsReady badge for hubspot.com
[![AgentsReady](https://agentsready.dev/badge/hubspot.com)](https://agentsready.dev/c/hubspot.com)