Interactive
The step-by-step operation above, and a verifier that checks a real proof in your browser, intact or tampered with. The demos page lists every interactive demo that is published.
DemosOpen protocol · draft 0.1
Companies book, sell, change and fix things for people every day. Now the request comes from the person's own agent.
VXP is an open protocol for that work. The person authorizes what their agent may do with the company, the company does it in its own systems under its own rules, and both keep signed evidence that anyone can check afterwards.
1 · The work
It starts with something a company has to resolve
A booking, a sale, a change, a request or a problem. The company already knows how to do it, in its own systems and under its own rules. What changes is who asks.
Retail
Move the delivery of an order to another day
Inside the company: check the route and the stock, change the date in the order system.
Hotels
Book two nights, or hold a booking for a late arrival
Inside the company: quote the current rate, hold the room, record the guarantee.
Distribution
Buy thirty units at the volume price
Inside the company: apply the discount policy, issue the quote, create the order.
Healthcare
Reschedule an appointment
Inside the company: find a free slot with the same professional and update the schedule.
Utilities and telecom
Report an outage at home and follow it up
Inside the company: open the ticket, assign a visit, report each change of state.
Insurance
Open a claim after an accident
Inside the company: check the policy, register the claim, ask for what is missing.
2 · Who asks
More and more, it is the person's own agent
The person talks to their agent, on the phone or in a chat. The agent goes to the company to ask for something, to pick up a request already under way, or to answer when the company needs a decision. The company did not build that agent and cannot see its conversation.
Before it acts, the company needs four answers, and so does anyone who checks the work later:
- 1Who asks, and on whose behalf?
- 2What may that agent do here, and until when?
- 3Which exact terms were accepted, and how?
- 4What ran, and what did the company's system show afterwards?
- Asks
«Move my order to Wednesday.» The agent starts a request with the company.
agent → company - Continues
Days later it comes back to the same request, and the company recognizes it.
agent → company - Answers
The company needs a decision and asks the agent, within what the person allowed.
company → agent
3 · What VXP adds
A relationship, exact conditions and evidence
VXP does not replace how the company works. It gives the agent and the company a common way to agree on what may be done, to do it exactly once, and to prove it.
-
Relationship
The person decides what the agent may do
The person links their account and authorizes the agent with the company: which operations, on which resource, up to what limit, until when. They can revoke it. Within that agreement the company can also start a request toward the agent.
VXP Relationship
-
Conditions
The company proposes exact terms, and runs them once
Nothing runs until one exact revision of the terms is accepted. Then it runs once, under the company's own rules. Every implementation meets the operation requirements O1 to O7.
Operation requirements
-
Evidence
Each step leaves a signed statement
The request, the terms, the approval and how it was given, the execution and what the company's system showed afterwards, each signed and linked to the one before. Anyone can check the chain.
VXP Proof
Its own profile. VXP has a native profile that needs no other protocol: discovery on the company's domain, the agent's own identity, permission per request, operations, Proof and Relationship.
Optional interoperability. For agents that already speak Poppy or PACT, a company can also publish those adapters, on the same issuer. VXP was created by SOVRAS; anyone can implement it.
4 · One operation, step by step
A person asks their agent to move a delivery
Order P-1042 at a test hardware store, Ferretería Demo. Each step says what happens; open the messages only if you want to see them. Captured from the reference implementation running the native profile alone, on the evening of 22 October 2026.
captured · native profile
Hosts are shown as store.example and agent.example, and long tokens are shortened. Entry-path labels are explained in Conformance.
5 · VXP Proof
Six signed statements, each pointing to the one before
The proof of the operation above. Two roles sign: the company signs the terms it offered and the result it declares; the operator, which runs the operation for the company, signs what it received, executed and read back. Choose a statement to inspect it, then try to alter it.
6 · VXP Relationship
An agreement the person authorized, so the company can ask too
In the same consent as the order, the person allowed the store to propose delivery changes to their agent, twice a day at most, for one hour. Within that agreement the store started a request, and the agent answered within what was authorized.
7 · Demonstrations
See it run, and check it yourself
With live agents
On 21 October 2026, personal agents came in through the Poppy adapter, among them Nova AI, SOVRAS's personal agent in beta, and a third-party web agent, Grok, through the companies' web pages. They moved deliveries, bought and booked with a test store and a test hotel, and the hotel asked a guest's agent to keep or release a booking.
What they did, with its evidence8 · Documentation
Everything needed to implement and check it
Docs
Guides for companies, personal agents and verifiers, from first request to proof.
Specification
The normative text, with stable anchors and MUST, SHOULD and MAY.
Architecture
Participants, identities, entry paths and how the parts fit.
Verifier
Check a proof in the browser, with valid and tampered examples.
Conformance
Test vectors, suites, commands and the results they produced.
Implement
Step by step for companies, agent platforms and verifiers, and how to take part.