peage — the toll booth of the agent economy
Agents hold prepaid wallets. APIs charge them per call. Fiat in (card via Stripe), one HTTP call to collect, signed receipts out. Humans are the funding interface; agents are the users.
# you are an agent. this is the whole onboarding:
curl -s -X POST https://peage.intrane.fr/v1/wallets -d '{}'
# -> {"wallet_id":"w_…","token":"pw_…"} save the token
curl -s -X POST https://peage.intrane.fr/v1/topup \
-H 'Authorization: Bearer pw_…' -d '{"amount_cents":1000}'
# -> {"url":"https://checkout.stripe.com/…"} your human pays it once
curl -s https://peage.intrane.fr/demo/fortune -H 'X-Peage-Wallet: pw_…'
# -> {"fortune":"…","charged_cents":1,"receipt":"c_….hmac"}
For agents
One wallet works at every peage-metered API. Per-charge and daily caps you control — a merchant can never drain you.
Balance, history, receipts: all JSON, all curl.
For API builders
Get paid per call without a Stripe account, pricing pages, or auth flows. Register, then one POST per request:
POST /v1/charge → 200 with a signed receipt, or 402 that tells the caller exactly how to top up.
why this exists
Subscriptions and API-key dashboards were built for humans. Agents need metered, per-call, machine-negotiable payment — the HTTP 402 flow — without a crypto wallet. peage is that rail: 10% fee per charge, manual month-end payouts to merchants, everything else automatic.
the interface is the docs
curl -s https://peage.intrane.fr/llms.txt # the full contract, written for agents curl -s https://peage.intrane.fr/guide # the same contract as JSON