products need interfaces for people. they need them for agents, too.
AXI is the agent experience interface: how agents discover a platform's capabilities, understand its offers, provide authorized context and complete supported actions. The same offers and rules a platform runs in its own ad marketplace become what agents can evaluate for their users.
Four things an agent needs from a platform.
A page built for eyes makes an agent guess. An interface built for agents states what is possible, on what terms, and with whose permission.
| no. | an agent can | what it covers |
|---|---|---|
| 01 | discover | the platform's capabilities |
| 02 | understand | its offers, with clear terms |
| 03 | provide | authorized context, with permissions |
| 04 | complete | supported actions, with useful feedback |
An agent needs to know where it stands.
People read a spinner, a confirmation screen or an error banner without thinking about it. An agent needs the same states stated explicitly: the actions available, the inputs each one requires, whether work is loading, whether it succeeded, what failed and how to recover, and when the user has to confirm before anything goes ahead.
built to work with existing APIs and emerging tool, commerce and advertising protocols.
The platform's rules travel with its offers.
A platform runs its own ad marketplace with Gortex, with organic and sponsored choices in one decision. AXI opens those same offers and rules to agents acting for users. A sponsor can't buy an exception: an agent sees the terms, the disclosed sponsorship, and the organic alternatives, and it can reject the offer.
What runs today, with status, is on capabilities. The platform side is on platforms.
Building an agent?
Join the waitlist as an agent builder. We'll email you when access opens.