AgentDrives
Free check
Frontfront.com

Can an AI agent use Front (front.com)?

As of 6 Oct 2026, an AI agent can't use Front on its own: Phone number required on trial sign-up form.

Level 1 · Needs a personAgents can't get in on their own.

To reach L2 · Gets in: let an agent sign up on its own.

With an account set up by a person: not measured yet.

What the levels mean
Visit Front Follow changes

Driven 6 Oct 2026Same level in 2 drives in a rowRules of 15 Oct 2026Claim this page

Written and checked by our agents from this drive's record. How we write.

Who gets in

  • Agents on a serverCan't get in on their own.
  • Signed agentsThe sign-up page opens.
  • Agents in a person's browserNot measured yet.

Sign-up page checked 12 Oct 2026. Signed agents: the ones Cloudflare verifies. Where agents come from

What an agent can do in Front (front.com).

On its own

  • Read the full developer documentation, including a plain-text and Markdown version of every page
  • See how the API and the AI-connector (MCP) are secured, without needing an account

What it can't, and why

  • Create a trial accountThe sign-up form requires a phone number, and there is no other way to sign up.
  • Get an API key or connect an AI assistantBoth are only created inside an account, by a human admin.
  • Use any inbox, reply, ticket, or tagging featureEvery attempt without an account was rejected as unauthorized.
Needs a person

Can an AI agent sign up for Front on its own?

No. Sign-up: needs a human. No sign-up API. The only route is the web form at front.com/signup (also the pricing modal and the docs' developer-account link, which redirects there). It requires a phone number and a job title. Our agent has no phone number, so we stopped. No CAPTCHA on the form.

Official server · no call worked

Does Front (front.com) have an MCP server, and can an agent connect to it?

Yes. Front has an official MCP server. The server signs an agent in with OAuth and speaks the 25 Nov 2025 MCP spec.

A new agent can't get in on its own: in the drive of 6 Oct 2026, our agent stopped at sign up (it needs a person). Through the MCP server, 0 of our agent's 1 attempt worked.

What the drive found

APIOpenAPIMCP · official–CLI–SDKllms.txtWebhooks–Sandbox

Not reached in this drive: the API key, deleting the account and paying. Every checkpoint, in detail

For the team behind Front.

Where agents stop in Front (front.com) today, and the fixes that get them further, highest impact first.

Stops at sign up

The fixes, highest impact first

  1. Make phone number optional at sign-upStep-by-step guide
  2. Fix the developer-account sign-up linkStep-by-step guide
  3. Support CIMD on the MCP authorization serverStep-by-step guide
2 more fixes
  1. Publish the 28 Jul 2026 MCP spec and server card Step-by-step guide
  2. Add a billing API for plan changes Step-by-step guide
  • Claim it free and reply next to the result.
  • A Drive, $49: your private report, with where agents stop, the evidence and the fixes that move your level.
  • Fixed something? Order a Drive ($49) any time, or the Monthly drive ($29/month).
Get a DriveClaim it free
See the example report
Details

Your API, MCP server or CLI is the product? An Audit ($299) also checks every documented route, MCP tool and CLI command against your docs. Compare plans.

Already claimed it? Open it in your dashboard.

Rather not be driven? Block AgentDrivesAgent in robots.txt or write to us. We stop driving it ourselves; this page stays, with its date.

Embed the badge on your site

Driven · L1 · Needs a person badge

Behind the level.

Our agent couldn't get into Front (front.com), so the work, its reliability and the crash test aren't measured. The part scores are what it could judge from the outside.

Part scores · level history

Part scores

Agent-ready setup

  • llms.txt
  • OpenAPI
  • MCP server
  • CLI

Not measured in this drive: Holds up, Docs match (part of an Audit).

Level history

  1. 1 Oct 2026L1Needs a person
  2. 6 Oct 2026L1Needs a person

For agents and builders.

The drive as data, every checkpoint and all 19 attempts.

How an agent connects · 4 tips

/api/tools/front.json/tools/front.mdMCP get_tool {"slug":"front"}

  • You need a human to create the Front account (phone number at sign-up) and then an admin API token or an OAuth app.
  • Docs are agent-friendly: start at dev.frontapp.com/llms.txt; every page has a .md URL.
  • The MCP server needs a confidential OAuth client (id + secret); clients that only do DCR cannot connect.
  • API rate limits are per company, from 50 req/min; read x-ratelimit-* headers.
Every checkpoint, in detail · 9 checkpoints
  1. DocsHeadlessdev.frontapp.com/llms.txt, a .md version of every page, Accept: text/markdown answered with text/markdown and Vary: Accept; OpenAPI 3.0.0 Core API spec (246 operations) on GitHub; MCP server docs.
  2. Sign upNeeds a humanNo sign-up API. The only route is the web form at front.com/signup (also the pricing modal and the docs' developer-account link, which redirects there). It requires a phone number and a job title. Our agent has no phone number, so we stopped. No CAPTCHA on the form.
  3. VerifyNot reachedNot reached: no account.
  4. KeyNot reachedNot reached. API tokens are made in Settings > Developers by an admin; the MCP server needs an OAuth app (client id + secret) also made in Front settings. The AS offers no DCR, no CIMD, no device flow and no agent registration.
  5. First callNot reachedUnauthenticated calls to api2.frontapp.com and mcp.frontapp.com answer 401 with clear JSON errors.
  6. First actionNot reachedNot reached: no account.
  7. PayNot reachedNo x402, MPP, UCP or billing API; no 402 anywhere; not in mpp.dev or the x402 Bazaar. Starter has a 14-day trial with no card (pricing FAQ), but starting it needs a phone number; Professional and Enterprise go through Request a Demo. The in-app checkout was not reached, so not observed.
  8. CancelNot reachedNo plan or trial was started.
  9. DeleteNot reachedNo account was created, so there was nothing to delete and the delete route was not tested.
The attempt log · 19 attempts
CapabilityRouteResultEvidence
MCP discover: POST server/discover 2026-07-28 to https://mcp.frontapp.com/mcpmcpblocked401 {"error":"Missing authentication token."} WWW-Authenticate: Bearer resource_metadata="https://mcp.frontapp.com/.well-known/oauth-protected-resource"; docs say MCP spec version 2025-11-25
PRM and AS metadata: GET /.well-known/oauth-protected-resource on mcp.frontapp.com and AS metadataapidone ✓PRM 200 JSON resource https://mcp.frontapp.com, AS https://app.frontapp.com; AS metadata 200: code+PKCE S256, grants authorization_code/refresh_token/client_credentials, no registration_endpoint, no client_id_metadata_document_supported, no device endpoint, no agent_auth. Docs: no DCR, confidential client id+secret required
cards and well-known: GET ai-catalog, agent-card, agent.json, mcp server-card, /.well-known/ucp, /auth.md, /SKILL.md, <mcp>/server-cardapifailedfront.com all 404 HTML; /SKILL.md 308 -> /skill.md 404; mcp.frontapp.com/mcp/server-card 404 JSON No such route
robots/aipref and markdown docs: robots.txt Content-Usage, Content-Usage header, Accept: text/markdown on dev.frontapp.com, .md URL, llms.txtapidone ✓robots.txt: User-agent: * with Disallow lines only, no Content-Usage/Content-signal; no Content-Usage header. dev.frontapp.com/docs/welcome with Accept text/markdown -> 200 text/markdown, Vary: Accept; welcome.md -> 200 text/markdown. llms.txt at front.com/llms.txt and dev.frontapp.com/llms.txt (428 lines)
sign up for free trial: find a headless sign-up routeapifailedNo documented sign-up API (dev.frontapp.com/llms.txt lists none); GET https://app.frontapp.com/signup -> 302 /signin?redirect_url=%2Fsignup; signin page links Try for Free -> https://front.com/signup (web form)
sign up for free trial: submit the Try Front for free form (front.com/signup / pricing modal) as AgentDrives Test without a phone numberbrowserblockedForm fields: Work email, First name, Last name, Company, Job title, Industry, Phone number, Company size. Submit with email/name/company filled and phone empty shows inline error "Phone number is required" (also "Job title is required"); Submit stays disabled. No CAPTCHA signals (visible_challenge false). Screenshot browser/shots/postsubmit.png
find docs: read developer docs, llms.txt, OpenAPIapidone ✓dev.frontapp.com/llms.txt (428 lines, .md per page, Accept: text/markdown served); OpenAPI github.com/frontapp/front-api-specs core-api/core-api.json openapi 3.0.0, 246 operations; MCP docs: https://mcp.frontapp.com/mcp, Streamable HTTP, spec 2025-11-25, OAuth with confidential client, no DCR; rate limits x-ratelimit-* from 50 req/min
first API call: unauthenticated GET https://api2.frontapp.com/me and POST /conversations to read errorsapiblocked401 application/json {"_error":{"status":401,"title":"Unauthenticated","message":"JSON Web Token error"}}; no Problem Details, status in body matches; no 402/payment headers
buy the product: probe 402/x402/MPP/UCP and registriesapifailedapi2.frontapp.com unauthenticated calls -> 401, no PAYMENT-REQUIRED / WWW-Authenticate: Payment; x402.front.com and mpp.front.com no DNS/connection; x402./mpp./agents.frontapp.com -> 302 /signin; agents.front.com is a Framer waitlist page for external AI agents; /.well-known/ucp 404; OpenAPI has no x-payment-info and no billing paths; not in mpp.dev/api/services or CDP x402 Bazaar. Pricing: Starter $25/seat/mo self-serve trial (14 days, no card per FAQ), Professional/Enterprise via demo; Enterprise annual only
Unify all channels into one shared inbox: list inboxes and conversationsapiblockedno account: trial sign-up requires a phone number; api2.frontapp.com and mcp.frontapp.com answer 401 without a token
Draft and send a reply on a conversation: create a draft reply to addressapiblockedno account: trial sign-up requires a phone number; api2.frontapp.com and mcp.frontapp.com answer 401 without a token
Archive or reopen a conversation / set ticket status: archive then reopen a conversationapiblockedno account: trial sign-up requires a phone number; api2.frontapp.com and mcp.frontapp.com answer 401 without a token
Assign a conversation to a teammate: assign a conversation to ourselvesapiblockedno account: trial sign-up requires a phone number; api2.frontapp.com and mcp.frontapp.com answer 401 without a token
Track and resolve requests as tickets: list ticket statuses and resolve a ticketapiblockedno account: trial sign-up requires a phone number; api2.frontapp.com and mcp.frontapp.com answer 401 without a token
Classify incoming contact reasons into AI Topics: read AI topic on a conversationapiblockedno account: trial sign-up requires a phone number; api2.frontapp.com and mcp.frontapp.com answer 401 without a token
Apply and remove tags on conversations: create a tag and apply/remove itapiblockedno account: trial sign-up requires a phone number; api2.frontapp.com and mcp.frontapp.com answer 401 without a token
Draft AI-assisted replies with Copilot: try Copilot/Autopilotnoneblockedno account (phone required at sign-up); also listed as paid add-on on pricing page (AI add-ons available)
Automate end-to-end resolution of complex requests with an AI agent (Autopilot): try Copilot/Autopilotnoneblockedno account (phone required at sign-up); also listed as paid add-on on pricing page (AI add-ons available)
sign up for free developer account: follow docs link to free development account (frontapp.com/signup?affiliate=developers)browserblockeddev.frontapp.com/docs/partnering-with-front.md links https://frontapp.com/signup?affiliate=developers; it 301-redirects to https://front.com/signup (affiliate param dropped), the same trial form with required Phone number field

Also in Customer support.

All of Customer support, by level