Kordio Control
Your software asks before it spends. You get
allowed, requires_approval, or denied in
the same request, naming the rule that decided, plus a signed grant your executor can verify
without trusting the caller that carries it. Kordio Control, in early access.Start here if something other than a person can start a payment or a paid API call on
your behalf.Ledger
Double-entry accounting over HTTP. Post balanced transactions, read balances and
statements at any instant, and reconcile against the outside world. Debits equal credits
per currency or the write is rejected.Start here if you need an auditable record of what money meant, separate from
whatever moved it.
The call each one is about
One call from each, so you can recognize which one you need.Which credential do I have?
The most common way to arrive here is holding a string somebody else generated.Using both?
Start with spend control. Where the ledger is enabled, the reservations it takes are mirrored into the books as balanced postings: each workspace owns its books and each agent owns an account inside them. You do not write those postings yourself, and you do not need to read the ledger docs to ship the control layer. Control decides what may happen; Ledger records what did. They are two API surfaces with their own authentication, which is why they have their own reference sections.Check Billing in the console for what your workspace has today,
including whether the ledger projection is on.
New to the problem, not the API?
Where Kordio fits
What sits between an agent and a payment rail, and who each half of this is for.
Where a control layer fits
Why a prompt, a hard-coded cap, and a card limit each stop short.