Ralio runs procurement and payment agents that source vendors, compare pricing, and execute purchases across external B2B marketplaces. Humanos sits at the merchant boundary and verifies every transaction before it executes.
Procurement and payment agents source vendors, compare pricing, and execute purchases across external B2B marketplaces.
Humanos sits at the merchant boundary and verifies every transaction before it executes — identity, scope, counterparty, amount, validity.
Agents now transact with external counterparties. Merchants, marketplaces, processors, and acquirers do not trust the agent’s runtime — and runtime guardrails alone cannot prove a human authorized the action.
Decisions are defined in one system. Agents execute in another. Settlement happens across merchants, processors, and networks the customer does not control. Nothing answers, in real time, whether a specific transaction was actually authorized by a human.
Authorization is local application state. External counterparties cannot verify the agent acted within scope. Audits reconstruct trails after the fact. Every new integration restarts the work.
When the merchant accepts an agent transaction, Humanos verifies the mandate live — identity, scope, counterparty, amount, validity — and returns a deterministic decision before settlement.
Within mandate, within constraints, within validity. The merchant settles. A Proof is attached to the transaction — portable, verifiable by any party.
Out of scope, expired, or revoked. Humanos requests step-up approval in real time (SMS, API), updates the mandate, and resumes once authorization is valid.
Five stages in chronological order. The animation on the right is the exact flow from our product page — adapted to Ralio’s €23,840.00 procurement order, settled at techsupply.eu.
Finance lead authorizes scope, counterparties, ceiling, and validity. Humanos issues a machine-verifiable mandate — signed once, reusable across every merchant that verifies.
Ralio runtime sources vendors, compares pricing, and assembles the procurement order. The agent attaches the mandate to its outbound request as x-humanos-mandate.
At checkout, the merchant calls humanos.verify() directly against the mandate — not against Ralio’s runtime. Identity, scope, counterparty, amount, and validity are checked in 82 ms.
Authorized → payment settles. Not authorized → merchant declines deterministically. For Ralio’s out-of-scope attempts (a €50,000 server rack), Humanos blocks at the boundary and triggers real-time step-up authorization.
Every transaction emits a cryptographic Proof — attached to the settlement, portable forever. Auditors, processors, and acquirers verify the Proof directly against Humanos; nothing reconstructs trails from internal logs.
Nothing settles on assumption. The verify call is non-optional and inline — at the merchant boundary, not just inside the agent.
Issue once, verify anywhere. The same mandate works across merchants, processors, networks, and acquirers.
Merchants check authority against Humanos. They do not have to trust Ralio’s runtime or your audit logs.
Each transaction emits a cryptographic Proof attached to the settlement. Auditors query; they don’t reconstruct.
Issue a new mandate. Revoke the old one. Effective immediately, everywhere a system verifies.
Out-of-scope action? Humanos collects approval (SMS, API, KYC) and resumes execution once the mandate is updated.
Issue once. Verify anywhere — merchants, processors, networks, acquirers.
External parties check authority directly, without trusting the agent’s runtime.
No new logic per venue. The integration is the verify() call.
The more systems verify against Humanos, the more valuable each mandate becomes.
Source vendors and execute purchases across external B2B marketplaces — hardware, software, services.
Buy on marketplaces and aggregators with authorization the marketplace itself can verify before clearing the order.
Card networks and acquirers verify agent-initiated charges against a human mandate before authorizing the transaction.
Agents acting across partner systems — verified by every system they touch, not just the issuing runtime.
Human authorizes scope. Humanos issues a machine-verifiable mandate, reusable across every system that verifies.
Any external system runs humanos.verify(). Deterministic yes / no.
Out of scope? Request step-up authorization from the human principal in real time — API, SMS, or email.
Cryptographic Proof per action. Auditable forever. Verifiable by anyone.
At that moment, authorization must be verified, the decision must be deterministic, and the outcome must be provable. Everything else follows.
Across organizations, marketplaces, processors, and networks.
No trust in the agent provider required.
Anyone can verify it. Forever.
