Your agent can decide.It still cannot pay.
It can read the contract, compare the suppliers and work out what the invoice should be. Then it stops, because nothing in the payments stack was built for a counterparty that is not a person, so you gave it your card, and put yourself back in the loop it was supposed to replace.
Five things you wired up so it could spend
A company card in the agent's config
Anything it has to buy
One limit for every agent, and no way to scope it to one
An approval step in Slack
Letting it spend above nothing
The agent idles until somebody answers
A payments table you wrote yourself
Working out afterwards what it spent
The statement names the vendor, never which agent
The provider's sandbox
Proving the flow end to end
Returns a 200 and settles nothing
A fresh integration, per agent
Every new agent that needs to pay
Weeks each, and none of them compose
All five rest on an assumption nobody has had to state before: there is a person behind every instruction, because liability needs somewhere to land. Your agent has no legal identity, so the industry's reflex is to put a human back in the loop — which works, and destroys the reason for building the agent. The cost is not the card's FX. It is that you shipped something that can decide at three in the morning and then has to wait until you are awake.
The same loop, your amounts
Four positions, and they do not change from one life to the next. What changes is the currency, the cadence and the size — which is the point: this is one system, not a product per problem.
The balance the agent draws on is opened by you and bounded by you: what it may spend, on what, until when. That is a mandate. A card in a config file is a credential, and the difference is that a mandate can be narrowed without being revoked.
$12,000 a month, the limit set once
The inference bill, the data vendor in Berlin, the contractor in Pune, or another agent that did a piece of the work. Each one a payment made inside the ceiling, with the agent that made it attached to the record.
EUR and INR out, metered per call
On every other page in this section Clark sits in the middle and connects the two ends. Here it is the thing itself: your agent adds the MCP endpoint as a server, discovers the tools and calls them, the same way it connects to anything else. The endpoint and its client config are the most real artefact on any of these pages — what sits behind the tools is not settling money yet.
https://clark.kryptonfund.com/mcp, paste-ready
Between the top-up and the invoice, the balance sits. Under the same mandate it can be allocated rather than idle. This is the smallest position on any page here and the shortest horizon: days, not quarters, and it is worth reading at that size.
~$6,000 average, days at a time
What changes for you
You bound the spending, not the access
A ceiling and a set of permitted counterparties is a smaller thing to reason about than a credential with your name on it. You can tighten it after a bad week without taking the agent offline, and you can give a second agent a different one.
You stop being the approval step
Human-in-the-loop stops being the mechanism and becomes an option you turn on for the payments that warrant it. The agent runs at the hours you built it to run at, which is the whole reason it exists.
Every payment has an agent's name on it
Calls are metered and attributed, so what an agent spent is a query rather than a reconstruction from a card statement. When you run four of them, you can tell which one is expensive.
One month, for one agent with a spending ceiling
Atlas is a procurement agent you shipped. It buys inference, renews a data licence from a vendor in Berlin, and settles small pieces of work with a contractor in Pune and with two other agents. You gave it a $12,000 monthly ceiling; about $9,000 of that crosses a currency pair.
It pays on a card shared with three other agents. The card's conversion takes roughly $315 of that $9,000, the statement cannot tell you which agent spent what, and anything over the limit waits in a Slack thread until you approve it.
Atlas connects to Clark over MCP and settles the same payments as EUR and INR pairs at the cost quoted before they move, about $36. The unspent balance is allocated against the next invoice date rather than sitting at zero, and each call is metered at the intended $0.02.
$315 of conversion becomes $36, the idle balance contributes about $22, and 1,200 metered calls cost about $24: $277 a month, net of what the runtime charges, for one agent. The approval thread is the part you actually get back.
Legacy costs above are figured at 3.5%, the midpoint of the 3–5% a cross-border payment loses today. Krypton’s are figured at 0.4%, the midpoint of the 0.3–0.5% the mechanism is designed to cost. Balances that would otherwise sit idle are figured at an illustrative 4.5% a year — a rate used to size the gap, not one any vault offers.
The MCP endpoint is real and you can point an agent at it today. The payment, allocation and settlement behind those tools are not licensed or live anywhere, the Clark Developer Platform and the agent marketplace are twelve-month items, and the $0.02 per invocation is the price this is intended to carry rather than a bill anyone has been sent.
