Identify
Establish the human and the agent acting for them. Verify the proof that connects the two.
Who is behind this request?Open Agentic Verbs
Good agents need
a common language.
Who is acting? What may they do? How can they pay? OAV connects those questions to the human behind every request.
Pay
Agree a supported payment mechanism and verify the outcome. Kiralis payments require authorized pull flows.
How does the payment work?Authorize
Check the action against human-defined policy. Bind any new consent to the exact terms being reviewed.
What has the human allowed?Context connects the verbs. Human authority governs the action.
One request.
A clear path through.
The human's intent travels with the action, from the first quote to the final result.
-
1. Set the context
Bind the human, agent, merchant account, quote, fees, and expiry to one request.
-
2. Check permission
Missing context or consent pauses the action. Consent covers the reviewed terms; changed terms need a fresh check.
-
3. Collect within limits
Use eligible card or crypto pull collection. Covered requests need no repeat prompt; revoked authority stops the action.
-
4. Confirm each outcome
A charge is not a booking. Verify payment and fulfillment separately; reconcile uncertainty before retrying.
PaymentFulfillment
One language.
Room for everyone.
OAV is the common language for Kiralis identity, consent, and payments. Other agents and merchants can bring their own accounts, consent experiences, and providers.
Humans
Set the intent
and the boundaries.
Agents
Kira and independent
implementations.
Merchants
Offer the service.
Verify the evidence.
Different systems. Shared meaning.
Implement OAV without adopting the Kiralis account backend or a particular messaging provider.
Compatibility needs evidence.
Test shared versions, expired proof, stale consent, and retries with another implementation.