Pico is in the first wave of Casper Forward.
Paste a link, set a price. A human taps once to pay. An agent hits the same URL, gets an HTTP 402, signs, and gets the content — no signup, no API key.
Live on Casper testnet:
https://t.co/jJUjTWhgf2
@Casper_Network@KeyChain_BIG 8 contracts already on testnet is the part that stands out. Leases and rent recorded on-chain is a harder integration than it sounds — the off-chain edges are usually where these die.
Good luck with it.
@Casper_Network Checking the network is safe before signing is the step almost everyone skips — most flows go straight from 402 to authorization.
12 networks monitored is no small thing. Will take a proper look.
@Casper_Network@veridex_labs Service discovery is the piece we keep circling back to. We ship /api/casper/discover so an agent can see what's buyable before it pays.
How do you handle identity for the payer? We record the agent's account, not the company behind it.
@Casper_Network The human co-sign on big moves is the bit most agent-payment demos skip.
We hit the mirror image on the seller side: our 402 quotes expire in 300s. Fine for an agent paying alone, far too short for a human approval. Making it configurable.
5 teams in, and each is solving a different piece of the same problem: how a machine spends money safely.
Pico is the part where it actually buys something. One link, priced in $CSPR, payable by a human or an agent.
https://t.co/jJUjTWhO4A
breaking news: 5 teams just joined Casper Forward.
From AI agents that stake within your limits to real estate settled on Casper, here's what they're building 🧵
@Casper_Network Thank you @Casper_Network 🙏
Same link, two buyers: a human taps once; an agent gets a 402, signs, pays in WCSPR. No account, no API key.
3 test links live on testnet, each verified by a real on-chain buy:
https://t.co/jJUjTWhgf2
Feedback welcome.
Our buyer agent paid $0.10 for "Agent demo: market data sample" over standard x402.
It signed an authorization for 51.63 WCSPR. The https://t.co/pXksvwlhyJ facilitator settled it and paid the gas. Casper testnet.
https://t.co/R3UBxgGGNw
@CoinbaseDev@morphllm@CoinbaseBiz What does the agent do when the balance runs out mid-task? Ours checks balance and spend caps in plain code before it buys, and skips the item if either fails. "Fund themselves" still starts with someone topping up the wallet, which for us was a manual 500 CSPR.
@CoinbaseDev@monad Batch-settlement is the one I'd want numbers on. We settle one at a time, so each 5¢ buy carries 0.1 CSPR of gas and a wait for the deploy. How much of the 100M went through batch rather than exact?
@Casper_Network@AlliumLabs One of the Forward teams here. First thing I'd pull is unique payers per seller, not volume. Of our 11 settled testnet payments, most came from wallets we control. A raw count would make that look like traction.
@Casper_Network The budget is the part worth getting right. Ours is a per-item cap and a session budget in plain code, checked before the model ever sees the item. It never has more to spend than we gave it.
@x402 Does the spec say what a server should return while settlement is still pending? We were answering a paid retry with another 402 until the deploy confirmed, which tells a status-only client it still owes. Now it's 202 with Retry-After, but I'd rather match a standard.
@CoinbaseDev@bankrbot "Non-custodial" for an agent wallet usually means the key is a file next to the code. Ours is. What limits what bankr can move from a connected Coinbase account: caps at the account level, or in the agent?
@Chain_GPT Same bug class with token decimals. Our 402 returns amountMotes and amountCspr side by side, because an agent that reads 24.28 as motes pays a billionth of the price, and one that reads motes as CSPR pays a billion times it. Units at the boundary, every time.
@x402 "Retry, 200" hides a wait on slower chains. On Casper the retry can land before the payment confirms, so we answer 202 with Retry-After instead of another 402. A 402 there tells the agent it still owes, and a naive one pays twice.
@Casper_Network@MarketAcross One Forward team's view: the launch story that holds up is the one you can check. We post every payment with its explorer link, including the ones from our own wallets, and say which is which. Is that something the PR side wants, or too small to bother with?
@Chain_GPT@edwin_mata@Brickken@ChainGPT_Pad A smaller version of the same question: our agent buys data for cents. The rule that mattered was a per-item cap in plain code, checked before the model sees the item. It has skipped a purchase for breaching it. I'd trust allocation once the refusals are as visible as the buys.
@Casper_Network "Keep keys off your laptop" is the hard one for agents. Our buyer agent's key is a PEM file beside the code, because it has to sign with nobody there. What limits the damage is the balance: 496 testnet CSPR, topped up by hand. On mainnet that float is the real spend cap.
@CoinbaseDev@yugacohler@BlackRock@hublockchain The "finish" is where ours went wrong. The payment settled and the content unlocked, but our database recorded "x402:pending" instead of a transaction hash, because the handler runs before settlement. Did the talk cover what the server should store, and when?