For platforms
Embed the verifier and the request in your own product.
You serve merchants, agents or finance teams of your own. Enruta becomes the authorization and evidence layer under your product: the same mandate, the same record, the same verifier, with your customers’ policies isolated from one another. Priced by the record, never by the flow.
What you hold
The customer. Enruta holds the authorization and the evidence.
| Detail | |
|---|---|
| Other people’s customers and orders | You hold the relationship; Enruta supplies the authorization and the evidence layer under it. |
| Objects | A white-label verifier; embedded request_payment and verify_record; a dispute field feed |
| Interfaces | White-label SDK and embed interfaces, planned for 2027; the REST API, the MCP server and the open verifier today |
| Billed by | Records, in volume |
Three embeds
Three buyers, three contracts, all on the price list.
The embed interfaces and the white-label SDK are planned for 2027. The prices are published now so nobody has to ask.
| Counterparty | What is embedded | Price | Status |
|---|---|---|---|
| PSPs, acquirers, orchestrators | A white-label verifier; request_payment and verify_record in your SDK; the mandate id written into your metadata or your universal token | From $60,000 a year for at least 1M records, then $0.01 to $0.03 a record | Planned, 2027 |
| Dispute-service providers | Records mapped to your order, additional_evidence and a policies[] entry of type agent_mandate | 10 to 20 % of your success fee, or $5 to $15 a record; the field feed is free from the first quarter of 2027 | Field feed from Q1 2027 |
| Procurement, AP and agent platforms | request_payment embedded; per-client policy isolation | From $60,000 a year, or per seat by client count | Planned, 2027 |
Available now
Everything that is open is already usable in your product.
| Piece | What it is | Where |
|---|---|---|
| The verifier | enruta-verify is open source (Apache-2.0), dependency-free and free forever; run it in your product today on any record a customer hands you | Verification |
| The record schema | enruta/0.2, published with a JSON Schema and test vectors | Evidence Record schema |
| The API and the MCP server | Everything an agent or a merchant can do, callable from your own systems with your customers’ keys | API, MCP tools |
| The dispute packet | Six export formats today, including payloads shaped for dispute vendors | Dispute packet exports |
| The conformance suite | runConformance in @enruta/sdk; the badge JSON is public | Conformance and badge |
One clause
Evidence absent is adverse.
Platform contracts carry one clause: in a dispute, a party that cannot produce a verifiable record defers to the party that can. It turns the record from useful into required, without waiting for a network rule, and it works because the verifier is open and the record is readable by every party without an Enruta account.
The embed contracts open in 2027. The open pieces are yours today.
A small number of finance teams and agent vendors are shaping the first records with us. If your agents already pay, or are about to, write to us.
hello@enruta.ai