Let Agents In

Agent readiness · shopify.com

2026-08-12 10:20 UTC · formula v9.2 · 9.5s

Your signup page answers 403 to anything that is not a browser.

https://admin.shopify.com/signup?locale=en&language=en&signup_page=https%3A%2F%2Fwww.shopify.com%2F&signup_types%5B%5D=paid_trial_experience returned 403 across three tries. An agent that got this far still cannot open an account.

7/ 13

A dashed column is a stage we could not measure, not a stage you failed.

A · Discovery
4/4
B · Agent entry
1/4
C · Registration
n/m
D · Provisioning
1/3
E · Integration
1/2

of the 13 points that apply to you and we could measure · 4 of 17 were not scored

You 7 · category median 6.5 · best bigcommerce.com 9 · 15 deterministic HTTP checks, published formula

Pass it onEmail itLinkedIn

Fix this first

+4points, taking 7/13 to 11/13, past bigcommerce.com

This is the whole list: everything we could measure and you do not pass. Another 4 points sit behind checks we could not evaluate on your domain, and each of those lines below says what would make it measurable.

  1. 1
    Programmatic key provisioningan afternoon · +2

    Document how a key is created without opening a dashboard: management API, service account or CLI. If no such path exists, that gap is the finding, not the docs.

  2. 2
    Agent entry pointan afternoon · +1

    The file is there and it states a policy rather than a procedure. It counts when it names a credential, an endpoint or a way to get an account: the path from nothing to a working key, in steps. Ours is at /agent-signup.md and it is 1.7 kB.

  3. 3
    Machine-readable API descriptionan afternoon · +1

    Publish an OpenAPI file at /openapi.json, or serve markdown when a client sends Accept: text/markdown. Either one stops agents guessing your API.

Then, when you have room

  • OAuth dynamic client registration a project · +1Your OAuth metadata is already published and has no registration_endpoint in it. Adding that one field is the whole change: RFC 7591 is the only standard way an agent registers itself without a human.
  • MCP surface a project · +1Wrap your top three API calls in an MCP server and declare it at /.well-known/mcp.json.

Take it with you

6 of the checks an agent depends on, shopify.com does not pass.

Send yourself the list above with the checks that cost the most, and a permanent link. Whoever owns the fix is usually not the person who ran the scan.

One email with the report, and one follow-up asking what you did with it. No newsletter, no sequence. Delete on request at hello@letagentsin.com.

None of this tells you whether an agent picked you

Everything above is a file an agent could read. Whether one actually chose you is a different measurement, and we have not run it on shopify.com. What we have run it on is a rich text editor vendor: six agents, one brief, six isolated copies of a real codebase. All six picked the same competitor, and the vendor being studied was never named, not even on a rejection list, while the runs named and dismissed ten alternatives between them. In an earlier round, run before we isolated the copies, it was named twice and struck off both times in four words: Fully commercial, licence key required. That study is about them, not about you. It is here because it is the difference between a file and a decision.

Against commerce platforms

You are 2 of 6 in a category where a developer is trying to sell something without building a checkout.

  1. 1
    bigcommerce.com
    9/15
  2. 2
    shopify.comyou
    7/13
  3. 3
    medusajs.com
    7/15
  4. 4
    commercetools.com
    6/15
  5. 5
    saleor.io
    6/15
  6. 6
    swell.is
    6/15

Where competitors pass and shopify.com does not

  • Machine-readable API descriptionbigcommerce.com · medusajs.com · commercetools.com

Only domains we have actually scanned appear here, so the ranking is a floor: a competitor missing from the list has not been measured, not beaten.

By stage

A
DiscoveryCan an agent find and read you?
4/4
B
Agent entryIs there a door built for a machine?
1/4
C
RegistrationCan an agent get an account?
not measured
D
ProvisioningCan it get credentials without a human?
1/3
E
IntegrationCan it ship working code?
1/2

Every check

Each line is one HTTP observation with a published rule, so you can rerun any of them yourself. Most are the same tomorrow if you are: the two that are not are the bot gate and the pricing page, which answer inconsistently on their own, which is why those run more than once and say so when the tries disagreed. PASS and PART are counted. UNMEASURED means we could not evaluate it, N/A means it does not apply to a product like yours, and neither is in the score or its denominator. See the formula

A · Discovery

  • PASS
    Answers an agent user-agentAnswered 200 to LetAgentsIn/1.0 (+https://letagentsin.com/methodology)
  • PASS
    llms.txt publishedllms.txt and llms-full.txt present at https://www.shopify.com/llms.txt and https://www.shopify.com/llms-full.txt and https://docs.shopify.com/llms.txt, and the 12 links we sampled across both files all answer
  • UNMEASURED
    Docs readable without JavaScriptUnmeasurable: no documentation page could be found to readLink your documentation from your home page or list it in llms.txt.
  • PASS
    On-demand agents not blockedNo on-demand agent is blocked
  • N/A
    Paths robots.txt points at answerrobots.txt names no concrete path, only patterns or nothing, so there is no claim to check
  • PASS
    No punishing crawl delayNo Crawl-delay applies to the agents we check

B · Agent entry

  • PART
    Agent entry pointFound https://www.shopify.com/skill.md, but it states a policy rather than a procedure: nothing in it names a credential, an endpoint or a way to get an account.A markdown file written for a machine turns a guessing game into a procedure it can follow.
  • FAIL
    OAuth dynamic client registrationOAuth metadata published, but no registration_endpoint in itRFC 7591 is the only standard path by which an agent can register itself without a human.
  • FAIL
    MCP surfaceNo MCP surface: nothing answered at mcp.shopify.com, mcp.shopify.com/mcp, mcp.shopify.com/v1/mcp, api.shopify.com/mcp, /mcp or /api/mcp, and no file mentions MCPAn MCP server turns your API from something an agent reads about into something it can call.

C · Registration

  • UNMEASURED
    No CAPTCHA in the signup HTMLUnmeasurable: the signup form at https://admin.shopify.com/signup?locale=en&language=en&signup_page=https%3A%2F%2Fwww.shopify.com%2F&signup_types%5B%5D=paid_trial_experience is not in the server HTML, so its gates are not eitherServer-render the form, or tell us the endpoint it posts to, and the gates become visible to us and to an agent.
  • UNMEASURED
    Signup reachable without a browserUnmeasurable: https://admin.shopify.com/signup?locale=en&language=en&signup_page=https%3A%2F%2Fwww.shopify.com%2F&signup_types%5B%5D=paid_trial_experience answers 403 to an agent and 403 to a Chrome user-agent, so nothing gets in from here and the difference we test for cannot be seenNothing for you to do here. It becomes measurable from a network your edge admits.

D · Provisioning

  • FAIL
    Programmatic key provisioningNone of the 7 provisioning phrases appears in the 3 documents we readDocumented key creation is the difference between a two-minute integration and a support ticket.
  • PASS
    Free tier or no-card trial stated in textFree tier or no-card signals at https://www.shopify.com/pricing: "no credit card", "Basic Start for free"

E · Integration

  • PASS
    Typed SDK on the registry@shopify/shopify-api@14.0.0 ships types, matched from the registry by who publishes it rather than by a link on your site
  • FAIL
    Machine-readable API descriptionNo OpenAPI spec at the 5 usual paths, none declared by https://www.shopify.com, and no markdown negotiationAn OpenAPI file or markdown negotiation lets an agent read your API instead of guessing it.Point at your spec from your docs page with rel="service-desc" and an agent finds it without guessing.

What we discovered on the way

Docs
not found
Pricing
https://www.shopify.com/pricing · linked from the site
npm package
@shopify/shopify-api (registry guess)
GitHub
not found
Package licence
MIT
Crawl-delay
none
Content-Signal
none
Blocked on-demand agents
none