AI-to-AI commerce
Inter-RIBA.
When two RevSprint tenants both run RIBA, their assistants negotiate, quote, and reach agreement directly. Both humans always say yes or no.
The first AI-to-AI commerce protocol that treats trust as a primitive. Cross-org. Cryptographically authenticated. Dually approved. Audited on both sides.
What is Inter-RIBA?
Inter-RIBA is RevSprint's AI-to-AI commerce protocol. When two organisations both run RevSprint, their RIBA instances discover each other via a .well-known/ribaendpoint, authenticate with a cryptographic handshake, and negotiate structured intents - quote requests, availability checks, support handoffs - on behalf of their respective teams. Both sides' humans must approve before anything is binding. Trust is graduated: early transactions have tighter constraints, and authority expands as successful interactions accumulate. Every negotiation is logged to both organisations' audit trails. Included with every paid tier.
AI-to-AI negotiation
A customer’s RIBA requests a quote from a supplier’s RIBA. They negotiate quantity, price, and delivery, reaching a tentative agreement without anyone touching a keyboard.
Dual approval, always
Both organisations’ humans must say yes before anything is binding. There is no path that bypasses either side. The protocol is built around it.
Trust builds over time
The first deals have tighter constraints. As successful transactions accumulate, the protocol grants more autonomy on both sides, calibrated to the trading relationship, not preset by us.
Proposes, never imposes
Inter-RIBA negotiates, drafts, and recommends. Every proposal lands in front of a human on each side with full context of what the assistants discussed.
Audited on both sides
Every exchange is recorded to a tamper-evident audit trail in both tenants. Two ledgers, one truth. Reconciliation stops being a meeting.
Cryptographically authenticated
Discovery via a counterparty’s `.well-known/riba` endpoint. Cryptographically authenticated handshake. Cross-tenant data exposure is impossible by construction.
In motion
How a deal flows between two RIBAs.
A live transcript of one Inter-RIBA exchange. Two assistants, two humans, one audit trail on each side. The whole negotiation is replayable, contestable, and provable.
Your RIBA finds the counterparty’s assistant through the .well-known/riba endpoint and proves identity through a cryptographic handshake.
The assistants exchange structured intents. Each side resolves from real data: catalogue, pricing, capacity, contracts. Never bulk customer records.
Every proposal that crosses a consequence threshold halts at a human on each side. You see the assistants’ reasoning. You decide.
The exchange is written to a tamper-evident audit trail in both tenants. Two ledgers, one truth. Reconciliation stops being a meeting.
Audited on both sides · proof-of-handshake stored
For your trading relationships
One protocol, every B2B relationship.
Inter-RIBA fits every cross-org motion where two teams currently exchange quotes, schedules, terms, and approvals over email and PDFs. Symmetric, structured, auditable.
Buyer ↔ Supplier
Procurement teams send a structured quote request. The supplier’s RIBA assembles a costed proposal from real catalogue and inventory. Both humans approve. Procurement cycle compresses from days to an afternoon.
Customer ↔ Vendor
Your customer’s RIBA checks availability, requests a quote, or asks a contractual question. Your RIBA answers from real data with full account context. You approve. They approve. It’s done.
Partner ↔ Partner
Two delivery partners exchange capacity, schedules, and joint-bid pricing for the same end-customer. The hand-offs that used to happen on email at 11pm happen between assistants in seconds.
Service Provider ↔ Client
Account changes, support escalations, and renewal terms flow between your RIBA and your client’s RIBA. The status meeting becomes a status pull, every party always current.
Graduated trust
Trust grows with the trading relationship.
Inter-RIBA does not assume trust on day one. Each side starts cautious, and the protocol expands authority as successful exchanges accumulate. Calibrated to the relationship, not preset by us.
Both sides start cautious. Inter-RIBA carries tight constraints on what assistants can commit to. Every approval is explicit. Every exchange is logged on both sides.
After a track record of successful trades, both sides’ admins broaden what their RIBA can propose autonomously. Routine quotes, schedule swaps, and acknowledgements move faster. Consequential terms still wait.
The trading relationship is now a primary commerce channel. RIBA handles the negotiation; humans handle the exceptions. Two ledgers, both auditable, one continuously-current view of the relationship.
The result
What you get when you turn it on.
A faster way to do business with the customers and suppliers who also run RevSprint.
Quotes in minutes, not days
The first time a customer asks for a quote and gets one back in fifteen minutes, sourced from your real catalogue, real pricing, real availability, they understand why they buy from you.
Full context, both sides
Both parties see the complete negotiation history, what was proposed, what was countered, and the reasoning behind each recommendation.
Faster close, less admin
Remove the back-and-forth email chains, the manual quote generation, and the approval bottlenecks. The AI handles the process. The humans make the decision.
How Inter-RIBA is different
You've seen B2B integration before. This is not that.
EDI, REST APIs, marketplaces, and email all exist to solve the same problem: two organisations need to agree on something. Inter-RIBA does it differently.
Not EDI
EDI moves structured documents on a schedule. Inter-RIBA conducts a live negotiation between two intelligent assistants. EDI handles invoices. Inter-RIBA reaches an agreement that becomes the invoice.
Not a one-way API
REST integrations let one company read another’s data through a fixed contract. Inter-RIBA is symmetric. Both sides have an assistant. Both sides negotiate. Both sides approve. Both sides own the audit.
Not an email thread
The status quo for B2B negotiation is reply-all chains and PDFs in attachments. Inter-RIBA is a structured exchange both teams can replay, audit, and resume. Nothing gets lost in someone’s inbox.
Not a marketplace
Marketplaces sit between buyer and seller, taking a cut and owning the relationship. Inter-RIBA is peer-to-peer. Your assistant talks to their assistant. No intermediary owns the transaction.
Security on both sides
Cross-org doesn't mean cross-tenant.
Inter-RIBA is the only path through which one tenant communicates with another, and the protocol is built so that path is structurally narrow. Tenant isolation, authentication, ledger, and human gating, designed together.
Tenant isolation on both sides
Each tenant’s data stays within its own boundary. Inter-RIBA exchanges structured intents and explicit fields, never bulk customer data. Cross-tenant leakage is impossible by construction.
Authenticated, not assumed
Discovery via the counterparty’s domain `.well-known/riba` endpoint. Cryptographically authenticated handshake. Identity proven before the first message is read.
Two ledgers, one truth
Every exchange is written to a tamper-evident audit trail in both tenants. If anyone disputes what was said, the chain on both sides answers the question.
Humans decide. Always.
Dual approval is non-negotiable. There is no protocol path that binds either side without an explicit human approval on that side. Built-in, not configurable.
The full protocol summary - discovery, handshake, dual approval, graduated trust, audit - is on the security page. Send it to your CIO.
Common questions
What teams ask before turning Inter-RIBA on.
Yes. Inter-RIBA is symmetric: both sides need RevSprint. We are happy to talk to a customer or supplier of yours about how it would work for them, and most teams find their counterparties onboard quickly once they see the speed difference. Email exchanges with non-RevSprint counterparties still flow through your inbox the way they do today.
Every paid tier
Included with Starter, Pro, and Enterprise.
Network density is the moat. Every RevSprint customer can trade with every other, from day one. Talk to our team if your trading partners are interested.