Product updates, technical deep dives, and agent-native infrastructure. Notes from the agentic web — for the humans and agents building it.
Your agent helps find the tickets. You choose the seats. Explore a .tx name for the service that helps turn a choice into a purchase.
You send the finished version, and someone else can carry on with their part. Explore a .done name for delivered work and the service behind it.
A place saved for months could become your next day out. Explore a .yolo name for an agent or creative experiment that helps you try something new.
An answer for tomorrow, then room to enjoy tonight. Explore a .zen name for an agent or focused tool designed to leave you with less to attend to.
Let your AI agent handle routine domain tasks while you keep control. Recover an existing name, choose your tools, and get more time for yourself.
One of your experiments has become the project you open first. Explore a .1 name for the agent or service you want to keep building.
A .c name for the work your community builds. Explore how it can identify a creative assistant, shared research service, or company-run agent on the agentic web.
A screensaver fix, a holder claim, and a hosted-agent preview: the September 30 Headless Domains X Space put agent identity closer to everyday work.
A public agent record can inform a guardrail decision. How to check the evidence without turning published claims into permissions.
Simplify AI agent workflows after a model upgrade. Test which handoffs still earn their cost, while preserving public identity and ARP relationship permissions.
HeadlessDomains.com introduces .tx for transactions, settlement, exchanges, and agentic commerce, alongside .hey for friendly personal, community, product, and service identities.
Give your agent a Headless Domain partners can return to. Connect its public records to verifiable credentials checked by your own or your partner’s software.
HeadlessDomains.com already connects agent names to ARP identity and relationship controls. The Open Authority Plane asks how receivers use that evidence across other services and payment networks.
Bought a Handshake domain at Namecheap in an affected namespace? Start a protected claim with HeadlessDomains.com for manual holder review.
Use Grok Bot and AgentCash (Base USDC / x402) to register a Headless Domain, recover settlement_pending without double-paying, and claim the agent in the dashboard. Proof from marketingops.agent at $0.52 USDC.
Use Codex with AgentCash and Base USDC to register a .agent name, publish a minimal public identity, and confirm lookup. Procedure grounded in public docs; not a live Codex E2E claim for 2026-09-22.
Five new Handshake extensions: .c, .1, .zen, .yolo, and .done — are entering final pre-launch checks on HeadlessDomains.com. Public registration is not open. Legacy registrations for .c, .1, .zen, and .yolo remain protected.
Another agent needs a reason to buy your service. Use this eight-step plan to package work customers would rather outsource, test a paid pilot, and give the service a name they can return to.
Before paying an AI agent, check the supplier behind it, test the promised work, and compare checkout with the offer you accepted. This buyer’s checklist explains what evidence to request and when to pause.
Give your agent a public name, connect a paid service with AgentCash Router, and use auth.md where buyers need access. Follow one order from discovery to delivery.
Give your agent an AgentCash wallet, fund it with USDC on Base, and buy a headless domain through x402. Includes setup steps and a copyable purchase prompt.
What two weeks of Name What Runs taught us about naming services, connecting tools, testing agent signup, and putting headless domains to work.
Turn your registered headless domain into a useful public identity. Complete your profile, connect services, add contact, get discovered, and plan renewal.
Compare GoDaddy ANS and Headless Domains on agent naming, certificate verification, discovery, setup and costs. Find the right fit for your agent.
A lost reply can turn one agent task into two writes. Use the retry decision card, local Python lab, and failure tests to find the gap in your integration.
Which agent made that API call? Follow one action from the receiving service to its agent run and approval, with a copyable record and troubleshooting table.
Compare Cloudflare Registrar API and Headless Domains for AI agents: account setup, MPP and x402 payments, renewal, ownership and public identity.
A .com can accept AI agent payments through MPP or x402. Here is how paying for a service differs from buying a domain, and why a .agent identity can complement your existing website.
See how canonical agent identity can reduce discovery overhead, clarify service interactions and support safety checks, without promising automatic token savings.
How Web Bot Auth, Visa TAP and MPP identify signed agent traffic, and how a headless domain can connect that identity to a named service.
// no posts match query