01.cash
A USD-denominated service credit you can spend with infr and approved Pute partners. Dots provides required wallet identity, compliance, funding, and merchant withdrawals; Pute itself is not an open-loop payment method or a crypto token.
The stack — anything in, compute out
card · bank · Venmo · Revolut · Wise · Cash App · USDC · Lightning · gift
↓ normalize USD
01.cash ← universal inbound primitive (PUTE layer)
↓ 1:1 credit
Pute ← prepaid compute balance
↓ debit + 2% routed
compute ← /api/v/* · GPU · trainers · self-host 01.cash is the normalization layer: every rail adapter converts inbound value to a single USD ledger entry before it becomes Pute. PayPal and Venmo don't plug in directly — they arrive via Peer ZKP2P (Venmo, Revolut, Wise, Cash App) or card onramps, then credit the same balance.
What the partner network means
- Required identity — Privy is the login and every production user activates a linked Dots financial profile.
- Closed acceptance — Pute can be spent only through infr APIs with approved merchants.
- Service credit — consumer Pute is not withdrawable or accepted outside the partner network.
- Merchant settlement — captured sales become merchant payable earnings, which can be batched to the merchant's Dots wallet.
How it works
- Card via Stripe → 01.cash → Pute (~3% Stripe fee net out)
- P2P fiat via Peer ZKP2P (Venmo, Revolut, Wise, Cash App…) → USDC → 01.cash → Pute
- USDC on Base via Tempo / x402 → 01.cash → Pute (1:1)
- Crypto onramps (Coinbase / MoonPay / Stripe Crypto) → USDC → 01.cash → Pute
- Lightning for micropayments < $1 → 01.cash → Pute
- Gift code redemption (any user → any user)
- Spend on approved inference routed through
/api/v/[model]or a Pute partner - Transfer to another Pute account (P2P)
- Issue a gift code redeemable by anyone
- Consumer credits are not cash-withdrawable; approved merchant earnings have a separate Dots withdrawal path.
Why it isn't a stablecoin
Pute is a prepaid voucher for routed compute. You buy credits, you spend credits on inference, credits are denominated in USD for sanity, and they cannot be redeemed back to fiat. The legal category is the same as Steam Wallet, App Store credit, AWS prepaid credits, or a Costco gift card — not a currency, not a stablecoin, not a security. The "Pute" name and coin imagery are branding; the underlying instrument is a restricted partner-network service-credit ledger.
This is the path that keeps infr out of MiCA (EU), the GENIUS Act (US), state money-transmitter licensing, and securities regulators without jurisdiction-specific legal review. There is no yield, peg arbitrage, or token to trade. Production withdrawals require Dots approval and payments counsel review.
Aggregate float — why this is interesting unit-economically
Every dollar of Pute sitting in the ledger is working capital for infr until it's spent. Most users top up in bigger chunks than they spend in any given week — so the float compounds:
- Cash float income — short-term Treasuries on the float (Stripe Treasury / Mercury Treasury) at ~5% APR, on top of the 2% per-call fee.
- Network effects — the more users hold Pute, the easier it is to introduce P2P transfers + gift codes + team pools (because internal transfers don't touch external rails and so don't cost us a Stripe fee).
- Fee compression — at scale, the 2% routing fee can drop because the per-call infrastructure cost goes down. We never need to touch the credit denomination to reduce price.
Legal posture in one paragraph
Pute is restricted prepaid access to services sold by infr and approved partners. Consumer credits are not cash-withdrawable and do not bear interest. Merchant payables and external Dots wallet funds are separate balances. Final classification depends on the live program structure and legal review.
Not investment advice. infr does not issue any token, security, or stablecoin. Your purchase of Pute is a purchase of service credits — same legal class as a Costco gift card. The "universal computer coin" framing is a brand and a UX, not a financial instrument.