Test storePreviewTest booking: nobody is expecting you. Preview: the UCP spec for this kind of store is still settling, so it will change.All sandbox stores
Harbour RowStays
Manage bookingBook a stay
Store analytics

How agents use Harbour Row Stays

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 v2 · UCP 2026-08-25 · worked out 22 Nov 2026, 13:32 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.

83%said who they werea UCP profile or a named bot
15%proved itsignature checked out
  • Proved 15%
  • IP-checked crawler 30%
  • Said, not proved 38%
  • Said nothing (scripts) 17%

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%10%17%<1% signature failed <1% claims to be a crawler 33%3% 73%
UCP over REST 4%<1%3%<1% signature failed <1% claims to be a crawler 4%5% 18%
UCP over MCP 6%—2%<1% signature failed <1%<1% 9%
All doors20%11%23%38%9%100%
  • Verified
  • IP-checked
  • Declared
  • Browser
  • Script
Storefront pages73%
Browser 33% · declared 17% (<1% signature failed) · IP-checked 10% · verified 9% · Script 3%
UCP over REST18%
Script 5% · Browser 4% · verified 4% · declared 3% (<1% signature failed) · IP-checked <1%
UCP over MCP9%
verified 6% · declared 2% (<1% signature failed) · Browser <1% · Script <1%

How we decide each level

Discovery and negotiation: what agents read first

Share of reads of the store's discovery files

/robots.txt 43%
/.well-known/ucp the UCP profile31%
/llms.txt 13%
/mcp tool list, read before a call7%
/ucp/openapi.json 5%
A2A agent card 1%
Read the store profile firstThe first request was discovery: the profile, the tool list or llms.txt52%

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 RESTYes21%1%
UCP over MCPYes4%9%
WebMCP in the pageIn the pages——

The rest of sessions used storefront pages only (76%). 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, 05:24 UTC · 6 requests · 29 s

Discovery and negotiation

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

Search and pick

  1. +9 s MCP search_properties results found 574 ms

Checkout

  1. +19 s MCP create_booking_session ready to pay 58 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.

Browsers44%
Search crawlers and bots36%
Scripts and tools10%
ucpchecker.com6%
ucpplayground.com1%
Declared a profile, not verified1%
river.ai1%
Other verified agents0%

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

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%
Searched dates4%
Viewed a room19%
Started a booking1%
Ready to pay0%
Booked0%

Where sessions ended

Every session ends in exactly one of these

Never searched78%
Viewed, did not add18%
Searched, picked nothing3%
Checkout started, not finished0%
Paid0%
Ready to pay, then left0%
Search found nothing0%

How agents connected

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

Storefront pages76% 0% paid
UCP over REST21% 1% paid
UCP over MCP3% 4% paid

Search

Which result agents go on to open or add

Too few picks to show a split yet.

Protocol calls

By operation, for operations called often enough to show. 94.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%21 ms467 ms
tools/list100%189 ms614 ms
GET /ucp/openapi.json100%15 ms245 ms
initialize100%191 ms258 ms
search_properties100%339 ms574 ms
notifications/initialized100%209 ms251 ms
GET /ucp/search0%51 ms226 ms
POST /ucp/booking-sessions75%77 ms112 ms

Errors agents ran into

Share of the error answers the store gave, by code

invalid_profile_urlThe agent left out its profile, or it could not be read42%
missingA required checkout field was not sent22%
eligibility_invalidThe store answered with this error code14%
not_foundThe agent asked for an id the store does not have11%
payment_failedThe test payment was declined6%
invalid_datesThe store answered with this error code6%

Agent habits

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

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