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

No. Sign-up: needs a human. Web form only (https://www.bigcommerce.com/start-your-trial/); on submit a visible reCAPTCHA Enterprise checkbox ('reCAPTCHA is required'). We do not solve it. No documented headless sign-up.

BigCommercebigcommerce.com

Can an AI agent use BigCommerce?

As of 12 Oct 2026, an AI agent can't use BigCommerce on its own: Visible reCAPTCHA on the trial sign-up form.

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

Find: Docs for agents: llms.txt, an OpenAPI and an MCP server.
Access: Can't sign up.
Use: Work not reached.
Pay: Payment not reached.
Leave: Leaving not reached.

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 BigCommerce Follow changes

Driven 12 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 serverStopped by a CAPTCHA on the sign-up form.
Signed agentsThe sign-up page opens. The CAPTCHA on the form stops them too.
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 BigCommerce.

On its own

Read the product's help pages and technical documentation
Search those documentation pages using an automated assistant
Download the technical API specifications

What it can't, and why

Open a free trial storea visible human-check box appears on the sign-up form
Get an access key for the storethat key is only created inside the store's control panel, which needs a store first
Do anything with products, orders or paymentsnone of that is possible without a store

Official server · a new agent can't get in alone

Does BigCommerce have an MCP server, and can an agent connect to it?

Yes. BigCommerce has an official MCP server.

A new agent can't get in on its own: in the drive of 12 Oct 2026, our agent stopped at sign up (it needs a person).

What the drive found

APIOpenAPIMCP · official–CLI–SDKllms.txtWebhooksSandbox

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

For the team behind BigCommerce.

Where agents stop in BigCommerce today, and the fixes that get them further, highest impact first.

Stops at sign up

The fixes, highest impact first

Let signed agents start a trialStep-by-step guide
Allow API accounts to be created via API
Return JSON errors for unknown stores

2 more fixes

Support MCP (the 28 Jul 2026 spec) on the docs server
Add an agent payment rail for plans 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 Drive Claim 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

<a href="https://agentdrives.com/tools/bigcommerce" rel="nofollow"><img src="https://agentdrives.com/badge/bigcommerce.svg" alt="AgentDrives · Driven · L1 · Needs a person" height="24"></a>

Behind the level.

Our agent couldn't get into BigCommerce, 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: found
OpenAPI: found
MCP server: found
CLI: not found

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

Level history

5 Oct 2026L1Needs a person
12 Oct 2026L1Needs a person

For agents and builders.

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

How an agent connects · 3 tips

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

Use docs.bigcommerce.com/llms.txt and append .md to any docs page
The docs MCP (https://docs.bigcommerce.com/_mcp/server) speaks 2025-11-25; use initialize
Expect a human step to open the store and create the first store-level API account in the control panel; then use REST with X-Auth-Token or the per-store Storefront MCP

Every checkpoint, in detail · 9 checkpoints

DocsHeadlessdocs.bigcommerce.com llms.txt with agent instructions, .md for every page (Accept: text/markdown -> 303 to .md, Vary: Accept), OpenAPI index /openapi.json with 77 specs (3.1.0), docs-search MCP server
Sign upNeeds a humanWeb form only (https://www.bigcommerce.com/start-your-trial/); on submit a visible reCAPTCHA Enterprise checkbox ('reCAPTCHA is required'). We do not solve it. No documented headless sign-up.
VerifyNot reachednot reached: no account (sign-up stopped at reCAPTCHA)
KeyNot reachedstore-level API accounts are created only in the control panel (Settings > Store-level API accounts, per api-accounts docs); no account to do it in
First callNot reachedevery Admin API path needs a store hash and X-Auth-Token; without them api.bigcommerce.com answers a 404 HTML page
First actionNot reachednot reached: no store, no token
PayNot reachedNo 402 on bigcommerce.com, api.bigcommerce.com, x402./mpp./agents. (no such host); no mpp.dev, Stripe Projects or Bazaar listing; no /.well-known/ucp. We paid nothing: 'no 402 on the product's own domain asks for USDC on a network we hold a wallet for'. Trial needs no card ('No credit card. No pressure.') but starts behind a visible reCAPTCHA; plan purchase is inside the control panel, which we did not reach.
CancelNot reachednot tested: no plan or trial was started. Developer docs cover only partner cancellation via the Powered by API (POST /franchises/{franchise_uuid}/v1/stores/{store_id}/cancellations); the merchant flow is in the control panel, not in the developer docs.
DeleteNot reachedno account was created, nothing to delete

The attempt log · 14 attempts

Attempt log
Capability	Route	Result	Evidence
llms.txt: Fetch llms.txt on www and docs	api	done ✓	https://www.bigcommerce.com/llms.txt 200 text/plain (H1 'BigCommerce'); https://docs.bigcommerce.com/llms.txt 200 text/plain (H1 'BigCommerce Docs', 'Instructions for AI Agents': append .md, section llms.txt, MCP server URL)
robots.txt / aipref: Read robots.txt for Content-Usage / Content-signal	api	done ✓	www.bigcommerce.com/robots.txt 200, 78 lines, User-agent: * group with Disallow on /admin/, /search/, /lp etc; no Content-Usage or Content-signal lines; sign-up path /start-your-trial/ not disallowed
Markdown docs: Accept: text/markdown and .md URL on a docs page	api	done ✓	GET docs page with Accept: text/markdown -> 303 Location: <page>.md, Vary: Accept; .md URLs return markdown (served as text/plain; charset=utf-8), e.g. /developer/docs/overview/sandboxes.md
MCP version: server/discover on docs MCP, then initialize	mcp	done ✓	POST https://docs.bigcommerce.com/_mcp/server server/discover with 2026-07-28 -> 400 application/json, JSON-RPC -32000 'Unsupported protocol version: 2026-07-28 (supported versions: 2025-11-25, 2025-06-18, 2025-03-26, 2024-11-05, 2024-10-07)'. initialize offering 2026-07-28 -> protocolVersion 2025-11-25, serverInfo fern-docs-mcp-server 1.0.0, no Mcp-Session-Id. tools/list -> 1 tool searchDocs (readOnly)
Pay step public probes: Read pay_probe.json and pay_tx.json; check docs for agent payment	none	done ✓	pay_probe: no 402 challenges on site, api., x402./mpp./agents. (no such host); no registry listings (mpp, Stripe Projects, Bazaar); no /.well-known/ucp; trial quote 'Launch your store today. No credit card. No pressure. Start for free'. pay_tx: refused, 'no 402 on the product's own domain asks for USDC on a network we hold a wallet for'
Docs: Find docs, API accounts and sandbox guidance	api	done ✓	docs.bigcommerce.com/developer/docs/overview/api-fundamentals/api-accounts.md: store-level API accounts are created in the control panel 'Settings > Store-level API accounts'; sandboxes.md: sandboxes via Partner Portal only
Sign up for a trial store: Fill start-your-trial form in browser (no documented headless sign-up)	browser	blocked ✓	https://www.bigcommerce.com/start-your-trial/: form filled (name, email the agent's inbox, password, store name, size, region Europe); on submit a visible reCAPTCHA Enterprise checkbox 'I'm not a robot' appears with 'reCAPTCHA is required'
Sign up for a trial store: Hand the visible reCAPTCHA to a human	browser	blocked ✓
Verify email: Verify the sign-up email	none	blocked	no account was created (sign-up stopped at reCAPTCHA)
Create a store-level API account: Create a scoped API token	none	blocked	api-accounts.md: store-level API accounts are created in the control panel 'Settings > Store-level API accounts' (KB article); no API/CLI route to mint the first token; no account to do it in
First API call: Call the Admin API without a store	api	blocked ✓	GET https://api.bigcommerce.com/stores/agentdrivesnone/v3/catalog/products (no token, made-up non-existent hash) -> 404 text/html openresty page, not a JSON error
First real action: Create a product	none	blocked	no store, no token (sign-up stopped at reCAPTCHA)
Delete the account: Delete our store/account	none	blocked	no account was created; docs MCP: store cancellation API is the Powered by API (POST /franchises/{franchise_uuid}/v1/stores/{store_id}/cancellations) for partners; merchant cancel flow not in developer docs
Cancel plan: Cancel a plan or trial	none	skipped	no plan or trial was started

Also in E-commerce.

All of E-commerce, by level

ShopifyL2Gets in on its ownBigCommerce vs Shopify
GumroadL2Gets in on its ownBigCommerce vs Gumroad
EcwidL1Can't sign up on its ownBigCommerce vs Ecwid