The standards still being written, and why that's not a reason to wait.
The specifications an AI agent uses to connect to a business, prove who it is, and get authorised to spend are all still being actively revised by the organisations building them. That's genuinely unsettled, not a reason to wait. The work that needs doing doesn't depend on any of it finishing first.
6 min read
Where the real uncertainty sits
Say a small group of self-catering cottages hears that the way an AI agent checks availability is still being revised, version numbers changing, edge cases argued over in public working groups, and reasonably concludes: we'll wait until it's finished. That's a longer wait than it sounds. Specifications this new tend to keep evolving for years, not months, and a business that waits for "finished" is waiting for a moving target.
This hub's pillar draws the line between what's already settled about agentic commerce and what's still being decided. The specifications covering how an agent connects to a business, proves who it is, and gets authorised to spend, gone through piece by piece in this site's hub on protocols and agent checkout, sit squarely on the unsettled side: real, working specifications, and all still actively changing shape, new versions, new edge cases, genuine disagreement between the organisations building them. Anyone claiming a fixed, final answer about how any of them will look in a year is overstating what's known.
What doesn't depend on any of it finishing
None of that revision touches whether a cottage's own facts, how many dogs it takes, its actual availability, its real cancellation terms, are accurate and current. Those facts don't change shape when a specification reaches a new version. A business that gets them right today doesn't have to redo that work later; the facts sit apart from the protocol, a separate layer entirely, the way a hotel's real room count doesn't change because the software checking it gets updated.
Waiting has a cost the standards don't
The risk in waiting isn't that the standards might change, they will. It's that the underlying facts stay wrong for longer than they need to. A cottage with an inaccurate cancellation policy loses exactly as many good matches while the specifications are unsettled as it will once they're finished, because the readers of that policy, human or agent, aren't waiting for a protocol to mature before checking it.
A cottage that waited eighteen months for the specifications to settle before writing an accurate cancellation policy didn't save any real effort. It just spent eighteen months answering the same requests with the same vague policy it started with, while a cottage two doors down fixed the fact in an afternoon and kept the bookings the vague one lost.
Where this shows up for a business
Selfe tracks the specifications underneath so a business doesn't have to, connecting a cottage's real facts once and keeping that connection current as each layer continues to evolve. The business's job is getting its own facts right, not following a working group's changelog.
Should we hold off building anything until the standards stabilise?
No, the facts a business needs to get right, availability, terms, constraints, don't change shape with a specification update. That work is safe to do now.
How do we keep up with which version of which specification matters?
That's the layer Selfe tracks directly, so a business's own facts stay connected as the specifications underneath continue to change.
The next twelve months in agentic commerce.
Most writing on where AI agents are heading falls into one of two camps: everything changes overnight, or nothing really changes at all. Neither is honest. Some things about agentic commerce are already settled enough to build for. Others genuinely aren't decided yet, and pretending otherwise doesn't help anyone plan.
The businesses that will be ready before anyone asks them to be.
Being ready for AI agents isn't a deadline to hit when the volume arrives. An AI agent already checks the same facts today that it will at scale next year, just less often. The businesses ahead of the curve are doing the unglamorous work now, before anyone's asking them to.
What changes for transactions once agents hold payment credentials.
Once an AI agent can hold a payment mandate and complete a purchase on someone's behalf, it's tempting to assume checkout itself transforms. For most businesses, what changes is narrower than that, and what doesn't change is worth stating plainly.