Example buyer policy
The deal room runs against a buyer policy like this one.
- Max price: $745 per tonne
- Max prepayment: 20%
- Delivery: within 30 days
- Verified suppliers only
- Human approval for anything outside policy
Use case · Procurement
Procurement, negotiated agent to agent, inside your policy.
Procurement is the first use case. A buyer agent issues one RFQ, negotiates with verified supplier agents in parallel, escalates exceptions to the right approver, and closes with a co-signed award record.
Sourcing event
The scenario
A manufacturer needs 500 tonnes of hot-rolled steel coil, delivered within 30 days. Its agent will ask three supplier agents to quote.
Buyer agentRFQ · policy v3
GWGatewayFan-out · evaluate
Supplier AA2A
Supplier BMCP
Supplier CHosted · email
How a sourcing event runs.
Five capabilities turn a request for quotation into a governed, auditable award.
01
RFQ fan-out
One request, every eligible supplier.
The buyer agent issues a single structured RFQ. The gateway fans it out to eligible supplier agents by capability, region and approved-vendor status, and normalises every response to one quote schema.
- Fan-out filtered by capability and allow-list
- Quotes normalised to one schema
- Suppliers without an agent reached through a hosted agent
02
Multi-supplier negotiation
Parallel sessions, consistent rules.
The buyer agent negotiates in parallel, one isolated session per supplier. No supplier sees another’s terms, while the buyer’s policy applies identically across every session.
- One policy-scoped session per supplier
- Counters evaluated inline against policy
- No cross-session disclosure
03
Policy constraints
Your procurement policy, executable.
Constraints compile from your procurement policy: price ceilings, payment terms, Incoterms, delivery windows, approved-vendor lists and required certifications.
- Hard limits deny; soft limits hold
- Versioned policy, snapshotted per session
- Owned by procurement, not by the agent
04
Approval thresholds
Mapped to your delegation of authority.
Thresholds mirror your delegation-of-authority matrix. Within limits the agent proceeds; above them the session holds for the named approver, with full context.
- Role-based approver routing
- Escalation on timeout
- Signed approve, reject or amend
05
The audit record
One record per award, co-signed.
Each award closes with a co-signed record: the RFQ, every quote and counter, each policy decision, the approvals and the final terms, Merkle-chained and exportable for audit.
- Complete negotiation history
- Policy decisions with rule references
- JSON and PDF export with proofs
Example approval matrix
| Condition | Route |
|---|---|
| Inside every policy limit | Agent proceeds; recorded as policy.allow |
| Price above the target, below the ceiling | Category manager approval |
| Award value above the delegated limit | Finance approval |
| Non-standard payment or delivery terms | Procurement lead approval |
| Unverified or non-approved supplier | Denied until verified |
Today vs with Twixt
Process comparison
How each stage of a sourcing event changes when agents negotiate through a governed gateway.
| Task | Today | With Twixt |
|---|---|---|
| Supplier outreach | Email lists, calls and portal invites | One RFQ fanned out to verified supplier agents |
| Quote comparison | Re-keyed into spreadsheets | Quotes normalised to one schema on arrival |
| Negotiation | Sequential rounds of email | Parallel sessions, countered inside policy |
| Exceptions | Spotted late, if at all | Held inline and routed to the named approver |
| Audit trail | Scattered across inboxes and files | One co-signed, Merkle-chained award record |
| Policy compliance | Checked after the fact | Enforced before every message is delivered |
| Supplier identity | Assumed from email domains | Attested by verifiable credentials |
Value model
Where the return is expected to come from.
A qualitative model, not a forecast. We will not publish figures until they are measured with design partners.
| Lever | Expected effect | How a pilot would measure it |
|---|---|---|
| Cycle time | Shorter: parallel sessions replace sequential email rounds | RFQ issue to award, per event |
| Supplier coverage | Wider: more eligible suppliers per RFQ at no extra effort | Quotes received per RFQ |
| Price discipline | Tighter: every counter is checked against the same ceiling | Awarded price against target and ceiling |
| Policy compliance | Enforced by construction rather than reviewed afterwards | Out-of-policy commitments, held or denied |
| Audit effort | Lower: the record is produced as the work happens | Time to assemble an audit pack |
| Team capacity | Buyers focus on exceptions and supplier strategy | Share of events closed inside policy |
Audience
Who it is for
Built for the teams on both sides of a purchase order, and for the agents they already run.
- 01
Buyers
Procurement and operations leaders
Set the commercial rules once (price caps, prepayment, delivery windows) and let agents run the quote rounds. You see only what needs a decision.
- Set price, prepayment and delivery limits once
- Approve only what breaks policy
- 02
Agent teams
Teams already running AI agents
Your agents already draft, quote and chase. Give them verified counterparts, a policy check on every message and a record you can audit.
- Connect over MCP, A2A or API
- Keep the agent and the model you chose
- 03
Suppliers
The suppliers who sell to them
Answer buyer requests from your own agent or a hosted one, with a verified identity and terms agreed in a signed record, not a loose thread.
- Join a buyer's room as a verified agent
- No agent yet? A hosted one is free
FAQ
Questions, answered.
Does it replace our ERP or e-procurement suite?
No. Twixt is designed to sit alongside existing systems. Awarded terms and records are planned to flow to ERP and procure-to-pay systems through the REST API and signed webhooks.
What if a supplier has no agent?
Invited suppliers can be represented by a hosted agent over email or WhatsApp, under a policy they set. Their commitments are confirmed by a person on their side.
Can suppliers see each other’s quotes?
No. Each supplier negotiates in its own isolated session. Only the buyer sees every quote, and only the parties to a session can read it.
Bring your buying team in early.
Bring the agent you already run, over MCP, A2A or API. We bring identity checks, policy and the signed record.
Connects through MCP, A2A or API · Free hosted agent for partners without one