Store analytics · method

How this page decides who arrived

Every figure comes from the store's own records. Nothing is estimated or filled in. Where we can't be sure, the page says "likely" and lists the reasons.

Back to how agents use Fernway Wholesale

Levels of proof

Level	How it's decided	What the store keeps
Verified	The request was signed with keys the agent publishes, and the signature checked out: Web Bot Auth or UCP request signatures (HTTP Message Signatures).	The scheme and the signer's name
Declared, unproven	The agent named itself, with a UCP-Agent profile or a bot user agent, but sent no signature or one that failed. When it failed, the reason is kept, for example "keys unreachable".	The name, the reason
IP-checked	A declared crawler whose network is inside the ranges its operator publishes (GPTBot, ClaudeBot, Googlebot and others publish them). Outside the ranges it shows as "claims to be". A crawler whose operator publishes no ranges stays declared.	In range or not; never the address
Browser: likely person or likely agent	Judged from behaviour, see below. Always "likely", always with reasons.	The network type, timings, screen size
Script	curl, python, Guzzle and other tools, or no user agent at all.	The tool's name

Person or agent, among browsers

Shown in the store owner's console only for now, until the accuracy below is measured. It is not on the public page.

Time on each page, and how even the rhythm is
The network type: a cloud or datacenter network, or a home or mobile one
The hour in the browser's own time zone
A small first-party script on the store's own pages, with no cookies and nothing sent anywhere else: screen size, navigator.webdriver, headless hints

A session is "likely an agent" when 4 or more signals lean that way and none points clearly to a person; "likely a person" when 3 or more lean to a person and none points clearly to an agent; otherwise "can't tell". A browser that signs its requests is named by its signer instead.

How we know it works

The answer is checked against sessions whose truth we know: UCP Playground and UCP Checker runs and signed agents (known agents), and staff visits (known people). It is judged on behaviour alone for this.

Not enough labelled sessions yetThe accuracy is published once there are 20 known agent runs and 20 staff visits in the last 30 days. So far: 1 and 0.—

What is never stored

IP addresses, buyer details, search text on this page, and anything that could follow a person from one day to the next. Requests are joined into a journey by signer, UCP profile, or a hash of network type and user agent whose salt changes every day.

The store answers every agent the same way, signed or not. This page shows agents; it does not rank them or treat any differently.