SC 1.0 and AgentReady: how the requirements map
Which requirements of the Specoria Commerce Readiness Specification correspond to AgentReady’s public requirements, and which have no equivalent. We only map what we could read in AgentReady’s own public text.
Sources and date
AgentReady v1.0 as published on the pages below, read on October 8, 2026. AgentReady describes itself as an open standard for agent readiness and states that it defines requirements, not weights or scores. If those pages change, this mapping may be out of date until we read them again.
How we map
- Same intent: both require the same thing, with minor differences noted.
- Overlaps: the two requirements share part of their scope; the note says where they differ.
- No equivalent: we found no AgentReady requirement for it in the text we read. Most store-specific requirements (prices, stock, returns, shipping, cart, checkout) fall here: AgentReady focuses on documentation, APIs and agent protocols.
- We map only to AgentReady items whose full requirement sentence we read in the specification text; for the others we only use the ID, level and title shown in llms.txt.
From SC 1.0 to AgentReady
| SC requirement | AgentReady | Relation | Note |
|---|---|---|---|
SC-ACCESS-01Search and user agents allowed (robots.txt) | AR-FIND-01 | Overlaps | Both ask robots.txt not to shut agents out. AR-FIND-01 asks not to block agents and crawlers at all; SC-ACCESS-01 scores search and user agents and leaves training bots out of the score, so a store may block training bots and still pass. |
SC-ACCESS-02Is bot protection open to agents? | AR-FIND-01 | Overlaps | AR-FIND-01 also covers blocking at the network layer; SC-ACCESS-02 tests that layer by requesting the homepage and a product page. |
AR-READ-02 | Overlaps | AR-READ-02 asks for a 429 instead of a silent challenge page. SC-ACCESS-02 scores a challenge page as a partial pass and treats a 429 as not verifiable, not as a block. AR-READ-02’s 404 rule is not scored by Specoria. | |
SC-ACCESS-03Product name and price readable without JavaScript | AR-READ-01 | Same intent | Same intent: the content must be in the initial HTML. SC-ACCESS-03 checks it on a product page (product name and price); on hotel and service sites, on the homepage. |
SC-ACCESS-04Sitemap | AR-FIND-03 | Same intent | Same intent. AR-FIND-03 asks for a sitemap referenced from robots.txt; SC-ACCESS-04 also passes when only /sitemap.xml exists. |
SC-ACCESS-05Can the product page be indexed? | - | No equivalent | |
SC-DATA-01Product structured data (schema.org) | AR-READ-08 | Overlaps | AR-READ-08 asks for JSON-LD on key pages, the homepage above all. SC-DATA-01 asks specifically for Product (or ProductGroup) JSON-LD on product pages. |
SC-DATA-02Price, currency, availability and URL | - | No equivalent | |
SC-DATA-03Product identity (GTIN/MPN, brand, SKU) | - | No equivalent | |
SC-DATA-04Images and description | - | No equivalent | |
SC-DATA-05Reviews and rating | - | No equivalent | |
SC-DATA-06Can variants (size, color) be addressed? | - | No equivalent | |
SC-POLICY-01Machine-readable return policy | - | No equivalent | |
SC-POLICY-02Returns page and window | - | No equivalent | |
SC-POLICY-03Machine-readable shipping information | - | No equivalent | |
SC-POLICY-04Shipping cost and time on the page | - | No equivalent | |
SC-POLICY-05Business identity | AR-READ-08 | Overlaps | Both look for JSON-LD on the homepage. SC-POLICY-05 asks for store identity data (name, address, contact, social profiles); AR-READ-08 doesn’t prescribe a type. |
SC-POLICY-06Legal pages (distance selling, Türkiye) | - | No equivalent | |
SC-CONSISTENCY-01Price consistency | - | No equivalent | |
SC-CONSISTENCY-02Stock consistency | - | No equivalent | |
SC-CONSISTENCY-03Currency and language | - | No equivalent | |
SC-CONSISTENCY-04Return window consistency | - | No equivalent | |
SC-CONSISTENCY-05Taxes-included wording | - | No equivalent | |
SC-CART-02Add-to-cart button in the initial HTML | - | No equivalent | |
SC-CART-03Is the cart button accessible? | - | No equivalent | |
SC-CHECKOUT-01Buying without an account | - | No equivalent | |
SC-CHECKOUT-02Order tracking | - | No equivalent | |
SC-CART-01Site search that works by URL | - | No equivalent | |
SC-HOTEL-01Hotel structured data (Hotel / LodgingBusiness) | - | No equivalent | |
SC-HOTEL-02Amenities in structured data | - | No equivalent | |
SC-HOTEL-03Rooms and prices readable | - | No equivalent | |
SC-HOTEL-04Cancellation policy discoverable | - | No equivalent | |
SC-HOTEL-05Booking entry point reachable | - | No equivalent | |
SC-SERVICE-01Business structured data (Organization / ProfessionalService) | - | No equivalent | |
SC-SERVICE-02Services described | - | No equivalent | |
SC-SERVICE-03Pricing or “how it works” discoverable | - | No equivalent | |
SC-SERVICE-04Contact details readable | - | No equivalent | |
SC-SERVICE-05Contact or quote form within one click | - | No equivalent |
From AgentReady to SC 1.0
| ID | Level | Title (as in llms.txt) | In the Specoria test |
|---|---|---|---|
AR-FIND-01 | MUST | Allow agents and crawlers in robots.txt | Related SC requirements: SC-ACCESS-01, SC-ACCESS-02 (differences in the table above). |
AR-FIND-02 | SHOULD | Publish the answer as first-party docs | Not tested by Specoria. |
AR-FIND-03 | SHOULD | List your pages in a sitemap.xml | Related SC requirements: SC-ACCESS-04 (differences in the table above). |
AR-FIND-04 | MAY | Publish an AI Catalog and link it | Information row only: the test requests /.well-known/ai-catalog.json and reports whether it exists. Not scored. |
AR-READ-01 | MUST | Fetchable without JavaScript | Related SC requirements: SC-ACCESS-03 (differences in the table above). |
AR-READ-02 | MUST | Return accurate HTTP status codes | Related SC requirements: SC-ACCESS-02 (differences in the table above). |
AR-READ-03 | SHOULD | Homepage in raw HTML | Not tested by Specoria. |
AR-READ-04 | SHOULD | Docs pages that answer | Not tested by Specoria. |
AR-READ-05 | SHOULD | Fenced code, language-tagged | Not tested by Specoria. |
AR-READ-06 | SHOULD | .well-known/* | Information row only: the test requests a fixed list of /.well-known/ discovery files and reports which exist. Not scored. |
AR-READ-07 | SHOULD | llms.txt | Information rows only: whether llms.txt exists and its structure. Not scored. |
AR-READ-08 | SHOULD | JSON-LD | Related SC requirements: SC-DATA-01, SC-POLICY-05 (differences in the table above). |
AR-READ-09 | MAY | Markdown mirror (our summary; no separate title line in llms.txt) | Not tested by Specoria. |
AR-ACT-01 | SHOULD | Auth an agent can get through | Not tested by Specoria. |
AR-ACT-02 | SHOULD | Public API with a machine-readable contract | Not tested by Specoria. |
AR-ACT-03 | SHOULD | MCP server | Information row only: the test looks for an MCP discovery file. It doesn’t connect to an MCP server. Not scored. |
AR-ACT-04 | MAY | MCP server card (our summary; no separate title line in llms.txt) | Not tested by Specoria. |
AR-ACT-05 | MAY | MCP Apps | Not tested by Specoria. |
AR-ACT-06 | SHOULD | SDKs and a CLI | Not tested by Specoria. |
AR-ACT-07 | MAY | WebMCP | Information row only: WebMCP markers in the page source. Not scored. |
AR-ACT-08 | MAY | Let agents pay | Information row only: a UCP profile at /.well-known/ucp and a possible ACP checkout endpoint (GET only). Not scored. |
AR-ACT-09 | MAY | NLWeb ask endpoint | Not tested by Specoria. |
Specoria wrote both the SC specification and this mapping. AgentReady is not affiliated with Specoria and has not reviewed it. Corrections: contact@specoria.com.