Claude-Agent user agent: how to verify it with the sail file
Anthropic's hosted Claude agent adds a Claude-Agent token to a browser User-Agent and lists its IPs at /.well-known/sail. How a store can verify it.
Research topic
Web bot auth
9 sourced articles on web bot auth, newest first: what changed, what it means for an online store, and what to fix so an AI agent can still find, understand and buy there.
Web Bot Auth draft -01: Accept-Signature and what changes
IETF Web Bot Auth draft -01 tells origins to request signatures with Accept-Signature and makes Signature-Agent a direct key-directory URL.
Stealth Bot Prohibition Act: What H.R. 9915 Means for AI Agents
H.R. 9915 would let the FTC fine bots up to $53,000 per violation for hiding their identity, so an honest user-agent could become a legal matter.
terms.txt: A robots.txt Alternative That Lets AI Agents Pay
A new preprint proposes terms.txt, a robots.txt-style file with per-purpose prices and signed receipts for AI agents. It has no adopters yet.
Web Bot Auth Is Now an IETF Draft — Not Yet a Standard
The IETF's Web Bot Auth working group formally adopted its core signing spec on September 1, 2026, but it is still pre-RFC.
Visa Trusted Agent Protocol: What Merchants Must Verify
Visa's published Trusted Agent Protocol spec defines three cryptographic signatures merchants check before trusting an AI shopping agent.
Web Bot Auth: why Cloudflare rejects dictionary-form signatures
Cloudflare's Web Bot Auth verifier still rejects the dictionary-form Signature-Agent header the newest draft requires. What to send so a signed crawler gets in.
Google-Agent Ignores robots.txt — What Actually Blocks It
Google's new Google-Agent fetcher is documented to ignore robots.txt by design, so merchants need IP blocking or auth instead.
Web Bot Auth: the identity layer under agentic checkout
Web Bot Auth lets an AI agent cryptographically sign its requests — and Visa, Mastercard and Amex are building agentic-checkout authentication on top of it.
📡 The agentic-commerce brief
What changed in the protocols — and what it means for your store. Connect it to your agent and it pulls the latest itself; no inbox required.
Add it to your agent (Claude Code, Claude Desktop, Cursor — anything that speaks MCP):
MCP server config
{
"mcpServers": {
"agentready-brief": {
"type": "http",
"url": "https://www.agentready.market/mcp/docs"
}
}
}Then ask it for the AgentReady brief —
it calls get_agentready_brief and reads any entry in full. Prefer a feed
reader? Subscribe by RSS.
No agent? Get it by email instead
Email delivery isn't live yet — nothing will land in your inbox until it is. Leave your address and you'll be on the first issue when it ships.