Test storeTest cards only, nothing ships.All sandbox stores
NorthlightFlowers
Store analytics

How agents use Northlight Flowers

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 v5 · 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.

89%said who they werea UCP profile or a named bot
11%proved itsignature checked out
  • Proved 11%
  • IP-checked crawler 58%
  • Said, not proved 20%
  • Said nothing (scripts) 11%

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 4 Nov 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 7%14%15%<1% signature failed <1% claims to be a crawler 17%1% 54%
UCP over REST 7%<1%3%<1% signature failed <1% claims to be a crawler <1%7% 18%
UCP over MCP 20%—6%3% signature failed <1%1% 28%
WebMCP in the page Too few requests to split <1%
UCP over A2A <1%—<1%—<1% <1%
All doors35%15%23%18%9%100%
  • Verified
  • IP-checked
  • Declared
  • Browser
  • Script
Storefront pages54%
Browser 17% · declared 15% (<1% signature failed) · IP-checked 14% · verified 7% · Script 1%
UCP over REST18%
verified 7% · Script 7% · declared 3% (<1% signature failed) · Browser <1% · IP-checked <1%
UCP over MCP28%
verified 20% · declared 6% (3% signature failed) · Script 1% · Browser <1%
WebMCP in the page<1%
Too few requests to split
UCP over A2A<1%
verified <1% · declared <1% · Script <1%

How we decide each level

Discovery and negotiation: what agents read first

Share of reads of the store's discovery files

/.well-known/ucp the UCP profile37%
/robots.txt 30%
/mcp tool list, read before a call14%
/llms.txt 8%
A2A agent card 6%
OAuth metadata 3%
/ucp/openapi.json 1%
Read the store profile firstThe first request was discovery: the profile, the tool list or llms.txt59%

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%<1%
UCP over MCPYes4%9%
WebMCP in the pageIn the pages<1%—
UCP over A2AYeson flowers-a2a<1%10%
Embedded checkoutYeson flowers-embedded——

The rest of sessions used storefront pages only (86%). 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.

A verified agent Verified · UCP request signature UCP over REST 20 Nov, 03:20 UTC · 102 requests · 15 min 3 s

Search and pick

  1. +0 s REST POST /ucp/catalog/search × 2 results found 1382 ms

Checkout

  1. +21 s REST POST /ucp/checkout-sessions answered missing 418 ms
  2. +22 s REST PUT /ucp/checkout-sessions/{id} ready to pay 387 ms
  3. +23 s REST GET /ucp/checkout-sessions/{id} ready to pay 309 ms
  4. +24 s REST POST /ucp/checkout-sessions/{id}/cancel 318 ms

Search and pick

  1. +49 s REST POST /ucp/catalog/search results found 336 ms

Checkout

  1. +50 s REST POST /ucp/checkout-sessions answered missing 369 ms
  2. +53 s REST PUT /ucp/checkout-sessions/{id} ready to pay 417 ms
  3. +54 s REST GET /ucp/checkout-sessions/{id} ready to pay 330 ms
  4. +59 s REST GET /ucp/checkout-sessions/{id} 295 ms

After the order

  1. +1:02 REST GET /ucp/orders/{id} 1466 ms

Search and pick

  1. +5:14 REST POST /ucp/catalog/search results found 1096 ms

Checkout

  1. +5:17 REST POST /ucp/checkout-sessions answered missing 360 ms
  2. +5:18 REST PUT /ucp/checkout-sessions/{id} ready to pay 379 ms
  3. +5:24 REST GET /ucp/checkout-sessions/{id} ready to pay 279 ms

Search and pick

  1. +7:49 REST POST /ucp/catalog/search results found 1101 ms

Checkout

  1. +7:53 REST POST /ucp/checkout-sessions answered missing 388 ms
  2. +7:58 REST PUT /ucp/checkout-sessions/{id} ready to pay 344 ms

Search and pick

  1. +9:34 REST POST /ucp/catalog/search results found 981 ms

Checkout

  1. +9:35 REST POST /ucp/checkout-sessions answered missing 391 ms
  2. +9:35 REST PUT /ucp/checkout-sessions/{id} ready to pay 316 ms
  3. +9:36 REST GET /ucp/checkout-sessions/{id} ready to pay 265 ms

Search and pick

  1. +10:48 REST POST /ucp/catalog/search results found 1658 ms

Checkout

  1. +10:48 REST POST /ucp/checkout-sessions answered missing 444 ms
  2. +10:49 REST PUT /ucp/checkout-sessions/{id} ready to pay 439 ms
  3. +10:50 REST GET /ucp/checkout-sessions/{id} × 4 ready to pay 1243 ms

Search and pick

  1. +11:15 REST POST /ucp/catalog/search results found 340 ms

Checkout

  1. +11:16 REST POST /ucp/checkout-sessions answered missing 350 ms
  2. +11:16 REST PUT /ucp/checkout-sessions/{id} ready to pay 397 ms
  3. +11:17 REST GET /ucp/checkout-sessions/{id} × 6 ready to pay 1782 ms
  4. +11:24 REST POST /ucp/checkout-sessions/{id}/complete ready to pay 486 ms
  5. +11:25 REST GET /ucp/checkout-sessions/{id} × 2 ready to pay 628 ms

Search and pick

  1. +12:09 REST POST /ucp/catalog/search results found 996 ms

Checkout

  1. +12:10 REST POST /ucp/checkout-sessions answered missing 378 ms
  2. +12:11 REST PUT /ucp/checkout-sessions/{id} ready to pay 376 ms
  3. +12:12 REST GET /ucp/checkout-sessions/{id} × 6 ready to pay 1628 ms
  4. +12:18 REST POST /ucp/checkout-sessions/{id}/complete ready to pay 314 ms
  5. +12:19 REST GET /ucp/checkout-sessions/{id} × 2 ready to pay 585 ms

Search and pick

  1. +12:33 REST POST /ucp/catalog/search results found 294 ms

Checkout

  1. +12:36 REST POST /ucp/checkout-sessions answered missing 351 ms

Search and pick

  1. +13:06 REST POST /ucp/catalog/search results found 307 ms

Checkout

  1. +13:07 REST POST /ucp/checkout-sessions answered missing 429 ms
  2. +13:07 REST PUT /ucp/checkout-sessions/{id} ready to pay 397 ms
  3. +13:08 REST GET /ucp/checkout-sessions/{id} × 2 ready to pay 1526 ms

Search and pick

  1. +13:11 REST POST /ucp/catalog/search results found 837 ms

Checkout

  1. +13:12 REST POST /ucp/checkout-sessions answered missing 596 ms
  2. +13:12 REST GET /ucp/checkout-sessions/{id} × 2 ready to pay 1247 ms
  3. +13:13 REST PUT /ucp/checkout-sessions/{id} ready to pay 857 ms
  4. +13:14 REST GET /ucp/checkout-sessions/{id} × 2 ready to pay 1209 ms
  5. +13:15 REST POST /ucp/checkout-sessions/{id}/complete ready to pay 381 ms
  6. +13:16 REST GET /ucp/checkout-sessions/{id} × 2 ready to pay 580 ms
  7. +13:17 REST POST /ucp/checkout-sessions/{id}/complete ready to pay 304 ms

Search and pick

  1. +13:47 REST POST /ucp/catalog/search results found 342 ms

Checkout

  1. +13:48 REST POST /ucp/checkout-sessions answered missing 449 ms
  2. +13:49 REST PUT /ucp/checkout-sessions/{id} ready to pay 475 ms
  3. +13:51 REST GET /ucp/checkout-sessions/{id} × 6 ready to pay 1849 ms
  4. +13:58 REST GET /ucp/checkout-sessions/{id} × 2 579 ms

After the order

  1. +14:09 REST GET /ucp/orders/{id} 272 ms

Checkout

  1. +14:48 REST GET /ucp/checkout-sessions/{id} 2101 ms

Search and pick

  1. +14:50 REST POST /ucp/catalog/search results found 1750 ms

After the order

  1. +14:50 REST GET /ucp/orders/{id} 1690 ms

Checkout

  1. +14:51 REST POST /ucp/checkout-sessions answered missing 464 ms
  2. +14:52 REST PUT /ucp/checkout-sessions/{id} ready to pay 426 ms
  3. +14:53 REST GET /ucp/checkout-sessions/{id} × 6 ready to pay 1933 ms
  4. +15:01 REST GET /ucp/checkout-sessions/{id} 314 ms

After the order

  1. +15:01 REST GET /ucp/orders/{id} 282 ms

Checkout

  1. +15:02 REST GET /ucp/checkout-sessions/{id} 288 ms

After the order

  1. +15:03 REST GET /ucp/orders/{id} 224 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.

Browsers47%
Search crawlers and bots40%
Scripts and tools6%
ucpchecker.com3%
ucpplayground.com1%
Declared a profile, not verified1%
sandbox.withgordon.ai1%
ahrefs.com0%
river.ai0%
Other verified agents0%
crawler.exa.ai0%
papchecker.com0%

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 signatures48%
Signature checked outAgainst the keys the agent publishes45%
Signed, signature failedDeclared who it is but couldn't prove it, for example the keys couldn't be fetched3%
Declared a profile onlySaid who they are without proving it52%

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%
Searched5%
Viewed a product58%
Created a checkout1%
Ready to pay1%
Paid test order0%

Where sessions ended

Every session ends in exactly one of these

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

How agents connected

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

Storefront pages86% 0% paid
UCP over REST10% 0% paid
UCP over MCP4% 11% paid
UCP over A2A0% 0% paid
WebMCP in the page0% 0% paid

Search

Which result agents go on to open or add

1st93%
2nd1%
3rd2%
4th or lower4%

24% of searches found nothing.

Protocol calls

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

OperationSucceededTypicalSlowest 5%
search_catalog99.6%277 ms860 ms
GET /.well-known/ucp100%123 ms667 ms
tools/list96.4%202 ms954 ms
initialize99.6%191 ms437 ms
search_locations80.1%142 ms332 ms
notifications/initialized100%185 ms426 ms
POST /ucp/common/locations/search81.2%222 ms482 ms
POST /ucp/catalog/search98.5%331 ms994 ms
create_checkout100%146 ms525 ms
GET /.well-known/agent-card.json91.9%46 ms459 ms
update_checkout100%127 ms418 ms
lookup_locations100%138 ms327 ms
POST /ucp/common/locations/lookup100%153 ms348 ms
get_product100%48 ms597 ms
complete_checkout99%117 ms694 ms
get_checkout100%36 ms89 ms
GET /ucp/checkout-sessions/{id}98.9%293 ms624 ms
POST /ucp/checkout-sessions100%337 ms692 ms
GET /.well-known/oauth-protected-resource100%178 ms635 ms
POST /ucp/catalog/lookup98.7%276 ms603 ms
GET /.well-known/oauth-authorization-server100%176 ms648 ms
GET /.well-known/ucp/2026-04-08100%446 ms1236 ms
ask_business88.7%335 ms1280 ms
GET /ucp/openapi.json100%68 ms258 ms
POST /ucp/common/ask78.9%314 ms512 ms
create_cart100%288 ms591 ms
get_order96.6%24 ms595 ms
PUT /ucp/checkout-sessions/{id}100%368 ms565 ms
server/discover0%201 ms245 ms
ping0%177 ms258 ms
GET /.well-known/ucpchecker-verify.txt91.7%582 ms1059 ms
cancel_checkout100%68 ms632 ms
GET /ucp/orders/{id}90%224 ms1466 ms
POST /ucp/checkout-sessions/{id}/complete100%381 ms486 ms

Errors agents ran into

Share of the error answers the store gave, by code

missingA required checkout field was not sent62%
invalid_requestThe request was not in a shape the store accepts26%
payment_failedThe test payment was declined4%
Not Acceptable: Client must accept both application/json and texThe store answered with this error code3%
identity_requiredThe store answered with this error code3%
invalid_profile_urlThe agent left out its profile, or it could not be read2%

Agent habits

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

Sent an idempotency key on writesA retry cannot make a second checkout60%
Calls to a paid orderTypical number of requests in a session that paid30
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 flowers-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.