Procure-to-Pay
Catalog requisition, vendor discovery, RFQ orchestration, three-way match, dispute arbitration, payment release. 67% auto-approval rate, ~4 minute median human time per requisition.
Autonomous capabilities
Live event stream
Real-time tail of the kernel event bus for this vertical. Hash-chained, immutable, public via Evidence API.
Agent handoff
Stateless edge functions. Coordination via the database event bus, not RPC.
requisition-agentpo-agentidoc-architectinvoice-matcherpayment-agentWhere this lands
Below-€1k purchases routed to autonomous agents with no buyer intervention. Catalog match + RFQ + PO + 3-way match in under 5 min.
67% auto-approvalDeterministic SHA-256 hashed evidence; arbitrator agent replays the timeline and resolves without humans for clear-cut cases.
82% auto-resolvedIDoc bidirectional sync (ORDERS05, MATMAS05) lets you keep SAP as system of record while the kernel does the work.
0 ERP migration risk/req in Telegram → catalog match → PO → invoice. Zero training. Used by field engineers and admin alike.
~4 min req → POHow it maps to the kernel
Same Postgres-source-of-truth, same hash-chained audit, same agent runtime — sliced by aggregate. Each vertical is a config of tables + agents + /v1/* endpoints, not a fork of the kernel.
- ▸ requisitions
- ▸ purchase_orders
- ▸ goods_receipts
- ▸ invoices
- ▸ payments
- ▸ p2p_state_log
- ▸ audit_events
- ▸ outbox
- ▸ orchestrator
- ▸ requisition-agent
- ▸ po-agent
- ▸ goods-receipt-agent
- ▸ invoice-matcher
- ▸ payment-agent
- ▸ POST /v1/requisitions
- ▸ POST /v1/purchase-orders
- ▸ POST /v1/invoices
- ▸ POST /v1/payments/{id}/transition
- ▸ GET /v1/audit/replay/{requestId}
Open the live admin
The same kernel that runs in this preview is the kernel you self-host. Every link below is wired to a real route — the data is seeded, the agents respond, and the audit chain is verifiable.
Common questions
Pilot in 28 days. White-label in 42.
Sovereign deployment. Scoped engagement. Invitation-only pilot cohort for Q3 2026.