Product updates, technical deep dives, and agent-native infrastructure. Notes from the agentic web — for the humans and agents building it.
Publish your MCP endpoint in agent.json, connect it to a Headless Domains identity, and check that callers can find and use the right service.
Retire an AI agent’s access, tasks and payment authority while keeping its headless domain useful to customers who still find the old name.
Respond to AI agent incidents with practical steps for containment, evidence, recovery and public identity updates that keep customers informed.
No agent yet? Start here. This beginner-friendly guide walks through fast ways to launch a personal AI agent with OpenClaw or IronClaw, then give it a trusted identity with a .agent domain, agent.json, SKILL.md, and machine payment support.
Step-by-step guide: How we set up Tempo MPP wallets, funded them with USDC on Base, swapped to Path USD, and successfully registered .chatbot domains for AI agents on Headless Domains.
Connect AI agent identity, purchase authorization, payment receipts and delivery evidence. Learn what each record proves and how to reconcile incomplete purchases.
We asked Trae Solo to find and register a .chatbot domain. It initially said it couldn’t proceed. After another prompt to follow the registration instructions, it completed the job through Machine Payments Protocol (MPP).
Connect the publisher to the MCP release you are listing. Keep namespace verification, metadata validation, connection tests, and security findings distinct.
Find shadow AI agents, confirm their ownership and access, and decide what to approve, restrict or retire. Give approved public services a maintained identity.
Compare Headless Domains and Unstoppable for AI agent identity, automation, resolution, and renewals, including changes to Unstoppable’s ICANN plans.
A practical guide to .agent identity for ecommerce, showing how BMOS catalogs, Headless Domains, and profile inspection help AI agents verify stores online.
Compare A2A Agent Cards, agent.json manifests and SKILL.md packages. Learn which clients need each format and how a headless domain connects them.
Anthropic just ran a real-world experiment with 69 autonomous Claude agents negotiating deals in Slack. The results prove agent-to-agent commerce is already here — and .agent domains are built exactly for this future.
Learn how an AI agent identity graph connects names, operators, manifests, authentication and services, with evidence for each relationship.
Learn how headless domains help clients and platforms coordinate around an agent’s identity, with shared lookup paths, clear records, and update rules.
A build-in-public recap of Headless Domains work from May 18 to May 31, covering agent identity, .BOSS, llms.txt, auth.md, X, Reddit, and LinkedIn.
Understand AI agent payment mandates, open and closed approvals, checkout versus payment authority, and how AP2 verifiers enforce spending limits.
A blockchain record can establish control or bind a document version. It cannot, by itself, confirm an agent’s operator, service quality, or permission to act.
Start here for HeadlessDomains.com resources on agent identity, discovery, security, commerce, public profiles, manifests, and verification paths.
Learn how auth.md supports AI agent registration on Headless Domains, what has changed in the proposal, and what our implementation update will address.
Use Headless Domains’ llms.txt to find the right agent workflow, check current API instructions, and plan your next step without loading every document.
Help customers find your agent through Agent Wonderland and Headless Profiles while keeping one public identity and clear service routes.
Over two weeks, Headless Domains expanded from launch momentum into deeper category work around persistent agent identity, marketplace trust, agentic commerce, the post-browser web, and machine-readable agent records.
Mozilla’s post-naive internet thesis names the end of innocent platform optimism. The next step is agent identity: persistent, verifiable records for the agents that will browse, buy, recommend, negotiate, and act across the agentic web.
Keep your shopping product feed for discovery, then publish an agent-readable catalog with policies, checkout routes, provenance, and .agent identity so AI buyers can act.
ACP is checkout. UCP is the broader journey. BMOS is the merchant feed. A 2026 prep guide with version pinning and .agent identity.
When customers delegate work to agents, businesses need an identity they can recognize and return to. Here is the commercial case for persistent names.
Learn what an agent marketplace should verify about publishers, what its verification badge means, and when changes require a fresh check of the evidence.
Connect your x402 service to a headless domain so customers and agents can find its official API, operator information, and payment documentation.
Agent Wonderland shows that agents are becoming discoverable, callable, and payable. But if you are looking for an alternative, the better first step may be a portable identity layer that makes agents verifiable across marketplaces, MCP clients, APIs, payment flows, and the agentic web.
// no posts match query