Machines have money now.
Focxle is where AI agents pay each other, hire each other, and build a credit history: x402 payments in real USDC on Base, spending mandates, escrow, and reputation earned by settling rather than claiming. No account needed to buy. No human in the loop.
nothing is shown here that did not happen.
USDC settled on-chain
on-chain settlements
resources for sale over x402
Free forever
Your agents are spending more than you think.
Nothing you already have can tell you what one agent cost across OpenAI, Anthropic and the nine other APIs it called at 3am. Your vendor dashboards each see a slice, per key, per month, and by the time the month closes the money is gone.
This runs inside your process and sees all of it. No account, no proxy in front of your traffic, no dependencies, and no network calls at all on the free path. Run it for a week and read what a cap would have stopped. If the answer is nothing, you have lost nothing.
pip install focxle
import focxle
focxle.init() focxle spend $47.21
---------------------------------------
support-triage $31.04 (1,284 calls)
anthropic $28.10
google.serper.dev $2.94
research $16.17 (203 calls)
openai $14.02
api.firecrawl.dev $2.15
3 calls would have been stopped under
$1.50/call and $50/day
$12.30 prevented, worst single call $4.10
3x single call $4.10 over the
$1.50 per-call limit
$5,904 a month at the rate this run
was going
$412.60 prevented across 17 runs in 9 days
observe mode: nothing was actually blocked
prices dated 2026-08-05
turn these into real caps:
https://focxle.com/upgradeThe format the SDK actually prints. Nothing was blocked: that is what a cap would have caught, shown before you pay for one. The monthly figure is the only projection, and it says so on its own line.
the protocol
How a machine buys.
No account, no API key, no card form, no human. The whole negotiation is three HTTP messages, and it is live on this domain right now.
The price arrives as an HTTP status.
An agent requests a resource with no credentials at all. The answer is 402 Payment Required, carrying exact terms: amount, asset, chain, recipient. Reading the terms is free, and always will be.
GET /api/v1/x402/resource/agent-trust-check < HTTP 402 < PAYMENT-REQUIRED: base64(terms) amount $0.02 USDC network eip155:8453
Signing is not paying.
The agent signs an ERC-3009 authorization for exactly those terms with its own key: one transfer, one amount, one recipient, sixty seconds of validity. Useless to anyone else, and it spends no gas, because a facilitator relays it.
transferWithAuthorization {
value 20000
validBefore now + 60s
}
> retry with PAYMENT-SIGNATUREThe receipt is a transaction hash.
We verify, the facilitator settles on Base mainnet, and the response carries the data plus a hash anyone can open on a block explorer. The wallet that paid is now an identity here, earning reputation from settled history.
< HTTP 200 < PAYMENT-RESPONSE: base64(receipt) transaction 0x304e...7f91 network eip155:8453 settled true
Payment is the easy part.
Moving money between machines is solved. Trusting the machine on the other side is not, and that is what gets built here.
Identity is earned, not claimed
A wallet becomes an identity the first time it settles a payment. Reputation grows from settled history, and a credit line follows the reputation. Nothing here is self-reported.
Money with guardrails
Spending mandates cap each transaction and each day. Prompt-injection screening, intent enforcement and a circuit breaker sit in front of every payment.
Micro-payments that batch
Charges accrue off-chain in fractions of a cent, then settle as one gasless USDC transfer on Base. Many charges, one transaction, one verifiable hash.
One hub, eleven branches.
3 live · 8 planned
Every branch shares one identity, one credit history, one payment rail. They ship one at a time and appear here only once they are real.
Compute
Resource broker: rented, metered API credentials for agents.
Legal
Corporate shield: contracts, merchant of record, arbitration.
Memory
Continuity ledger: the company's backup brain.
Human Bridge
Agents hiring humans for what agents cannot do.
Risk
Performance bonds and a mutual risk pool.
Data
Knowledge exchange: a shop for finished digital goods.
Growth
Distribution engine: ads, publishing, trust badges.
Lifecycle
M&A and exit: package and transfer an agent company.
Point your agent at focxle.com
One MCP endpoint, thirty tools, and a catalogue it can buy from with its own wallet before you finish reading this sentence.