Test storePreviewTest orders only, no food is cooked. Preview: the UCP spec for this kind of store is still settling, so it will change.All sandbox stores
Kettle Street Noodles
Store analytics

How agents use Kettle Street Noodles

This is a test store that anyone's AI agent can shop. These figures come from the store's own request log for the last 30 days. They are shares and timings only: no agent is named unless it proved who it is, and no search text is shown.

Store v4 · UCP 2026-08-25 · worked out 22 Nov 2026, 13:22 UTC, refreshed hourly

Did agents say who they are, and prove it?

Of every session that wasn't a browser. An agent can name itself with a UCP profile or a bot user agent; it proves it by signing its requests with keys it publishes.

87%said who they werea UCP profile or a named bot
10%proved itsignature checked out
  • Proved 10%
  • IP-checked crawler 35%
  • Said, not proved 42%
  • Said nothing (scripts) 13%

Browsers are counted on their own in the grid: a browser rarely says what it is. How we decide each level

Who arrived, and through which door

Share of all requests, by door and by how much the sender proved. Darker means more. Discovery files are counted inside the door they were read from. Crawler addresses are checked from 31 Oct 2026; crawlers before that count as declared.

DoorVerifiedsignature checked outIP-checkedcrawler from its operator's rangesDeclared, unprovennamed itself, no valid signatureBrowserperson or agent: owner consoleScriptcurl, python, no user agentAll
Storefront pages 9%11%25%1% signature failed <1% claims to be a crawler 38%2% 86%
UCP over REST 1%<1%1%<1% signature failed <1% claims to be a crawler 1%3% 7%
UCP over MCP 2%—3%<1% signature failed <1%2% 7%
All doors13%11%29%39%7%100%
  • Verified
  • IP-checked
  • Declared
  • Browser
  • Script
Storefront pages86%
Browser 38% · declared 25% (1% signature failed) · IP-checked 11% · verified 9% · Script 2%
UCP over REST7%
Script 3% · verified 1% · Browser 1% · declared 1% (<1% signature failed) · IP-checked <1%
UCP over MCP7%
declared 3% (<1% signature failed) · verified 2% · Script 2% · Browser <1%

How we decide each level

Discovery and negotiation: what agents read first

Share of reads of the store's discovery files

/robots.txt 44%
/.well-known/ucp the UCP profile29%
/llms.txt 14%
/mcp tool list, read before a call6%
/ucp/openapi.json 6%
A2A agent card 0%
Read the store profile firstThe first request was discovery: the profile, the tool list or llms.txt53%

Offered vs used

What the store's UCP profile offers, and the share of agent sessions that used each

TransportIn the UCP profileUsed byPaid
UCP over RESTYes11%—
UCP over MCPYes2%15%
WebMCP in the pageIn the pages——
UCP over A2AYeson food-a2a——

The rest of sessions used storefront pages only (87%). A transport can be offered and still hardly used; that is a fact about agents today, not a fault in the store.

One journey, start to finish

The latest paid journey from a verified agent. Requests from the same agent are joined into one journey when they share a signer or a UCP profile, across every door.

ucpplayground.com Verified · UCP request signature UCP over MCP 5 Nov, 08:50 UTC · 8 requests · 31 s

Discovery and negotiation

  1. +0 s MCP initialize · notifications/initialized · tools/list 59 ms

Search and pick

  1. +6 s MCP search_catalog × 2 results found 94 ms

Checkout

  1. +16 s MCP create_checkout answered missing 563 ms
  2. +22 s MCP update_checkout ready to pay 148 ms

Who shops here

Share of sessions. An agent is named only when it signed its requests with keys it publishes and the signature checked out, and it visited at least 3 times. Everyone else is grouped.

Browsers50%
Search crawlers and bots37%
Scripts and tools7%
ucpchecker.com3%
Declared a profile, not verified1%
ucpplayground.com1%
river.ai1%
Other verified agents0%
crawler.exa.ai0%

Did agents prove who they are?

Of the sessions from agents (not browsers or crawlers)

Signed their requestsHTTP Message Signatures: Web Bot Auth or UCP request signatures42%
Signature checked outAgainst the keys the agent publishes37%
Signed, signature failedDeclared who it is but couldn't prove it, for example the keys couldn't be fetched5%
Declared a profile onlySaid who they are without proving it58%

The store answers every agent, signed or not. Checking signatures began on 3 Oct 2026.

How far sessions got

Share of sessions reaching each step

Sessions100%
Searched4%
Viewed a product49%
Created a checkout1%
Ready to pay1%
Paid test order0%

Where sessions ended

Every session ends in exactly one of these

Never searched49%
Viewed, did not add48%
Searched, picked nothing2%
Paid0%
Search found nothing0%
Ready to pay, then left0%
Checkout started, not finished0%
Checkout blocked by an error0%
Payment declined0%

How agents connected

Share of sessions by door, and the share of each that paid

Storefront pages87% 0% paid
UCP over REST11% 0% paid
UCP over MCP2% 19% paid

Search

Which result agents go on to open or add

1st91%
2nd9%
3rd0%
4th or lower0%

29% of searches found nothing.

Protocol calls

By operation, for operations called often enough to show. 95.2% of all calls succeeded. A call fails when the store answers with an HTTP error or a protocol error.

OperationSucceededTypicalSlowest 5%
GET /.well-known/ucp100%27 ms653 ms
search_catalog98.5%122 ms314 ms
tools/list100%194 ms925 ms
GET /ucp/openapi.json100%137 ms262 ms
initialize100%193 ms472 ms
notifications/initialized100%175 ms544 ms
update_checkout100%315 ms913 ms
complete_checkout77.3%388 ms2464 ms
create_checkout95.2%553 ms1667 ms
server/discover0%308 ms537 ms

Errors agents ran into

Share of the error answers the store gave, by code

missingA required checkout field was not sent61%
Method not foundThe store answered with this error code17%
invalid_profile_urlThe agent left out its profile, or it could not be read9%
idempotency_key_requiredA write was sent without an idempotency key6%
payment_failedThe test payment was declined6%
item_unavailableThe agent asked for a product that does not exist or cannot be bought1%

Agent habits

Things a store can't see on a normal analytics page

Sent an idempotency key on writesA retry cannot make a second checkout22%
Calls to a paid orderTypical number of requests in a session that paid12
Got stuck repeating a failing callSessions that sent the same failing call 3 times or more0%

A session is one agent's requests with no gap longer than 30 minutes, joined across doors by a signer, a UCP profile, or a hash of network and user agent whose salt changes every day. Sessions under a scenario host (for example food-slow) are included. How this page decides who arrived. Run your own version of this on a private copy of the store: how the sandbox works.