One event model for authority, money movement and the ledger.
Requests, approvals, compliance checks, conversions and journal entries share one structure. Build against the same objects your finance team reviews, with the same rules enforced underneath.
Self-custodyHuman-approved executionMulti-entity
Six surfaces over one object model.
query: software_spend by dept, Q3
rows: 6 · sources: ledger, cards, agents · quality: complete
Growth26,100
Engineering22,740
Operations15,160
Other 3 teams20,210
ledgercardsagent_walletserp_sync
period=2026-Q3 · entity=all · 1 of 6 teams paid mostly by agentsAgentic CFOGrounded queries over ledger, bank and wallet data, with data-quality status.
→Research agent23 days476.40 USDC
AI Payment SystemScoped agents, wallets and cards.
Agent wallet1,196.40Fees3.60Bank1,200.00✓ Reconciled
Accounting IntegrationDouble-entry ledger with sync connectors.
You send10,000.00 USDFee30.00 USDYou receive9,970.00 USDC
On/Off-RampQuote, route, settle, journal.
prioritycostmin_received9,962.10 USDC
SwappingRoute type plus cost and speed.
TaxationCalculations traceable to transactions and rule versions. Submission stays human.
✓ Collected✓ PreparedIn reviewFiled by you
Every request passes through the same five layers.
Approval thresholds by amount.
A 4,000 USDC payment needs 2 of 3 finance approvers.tiers=[1000,25000] → tier_2
Things the platform is built never to do.
Start with one entity, one rule and a test agent.
A single-founder company works as-is, with you as the only approver. When you add entities, clone the configuration and every call inherits it.