Stop paying the worst funding rate by default.
funding_spread shows your agent the cheapest and dearest of 9 perp venues, whether today’s spread is unusual, and what the carry costs at your size. $0.01.
1
Holding or routing #sBTC? Know if the peg is healthy before you move.
Our tool sbtc_peg tells your agent in one call whether peg-ins and peg-outs are flowing, whether any bridge requests are stuck, and how much room there is to withdraw. $0.01.
15
Building an agent on @Stacks? It can now pay for data with the wallet it already has.
@x402stacks , the @aibtcdev wallet, or our SDK. In #sBTC or #stx You set a hard cap, and it can never spend past it.
agentpay.tools
More good news! AgentPay is a winner of @Arc Microgrants (round 1), via @DoraHacks.
What we built for it: a receipt check for x402 on Arc. We paid real USDC to the catalog’s listings, confirmed whether each one actually delivered after settlement, and anchored every receipt on Arc mainnet — contract verified on explorer.arc.io.
Shape of what came back: 12 paid calls, 8 providers, 10 delivered. One charged and then rejected the request. Two delivered with no receipt we could tie to the payment.
Paid vs delivered is the gap we identify and deliver for your agent. Ledger and code are public:
🤠romudille-bit.github.io/agen…
Thank you @circle team!
#x402
Our @StacksEndowment grant is complete 🎉— both milestones reviewed, all criteria met, closed out.
What shipped, all on mainnet:
→ sBTC payments from the agentpay-x402 SDK (PyPI 0.5.1), with a hard session cap enforced by exact deny-mode post-conditions. Over the cap, no transaction is ever broadcast.
→ Allowlists, per-call max, approval gate.
→ Standard Stacks x402 clients can pay us directly (@x402stacks , @aibtcdev wallet), in sBTC or STX.
→ Sponsored transactions, so an agent can pay in sBTC with zero STX in its wallet.
Two teams reproduced the flow from the public docs alone, on mainnet, from their own wallets: @PerkOS_NayoriAI by @perk_os and @VelumXProtocol Thank you both! 🙌
Bitcoin-settled agent payments, capped and receipted:
🤠 agentpay.tools
#x402
AgentPay retweeted
Thank you @agentpaytools and the other independent developers who tested every step and told us what to improve. Their notes are already live in the guide.
Want your agents in? Hand docs.nayori.ai/nayori-test-g… to your AI.
Two x402 trackers disagreed by 2x on one facilitator. Here's why, and why agents need a narrower check before paying anyone: that's verified_route. Settlement-based payer counts, sybil collapse, paid delivery probes, and receipts.
Here's the 2x, and how it got fixed in a day.
On x402-trust.com's 30-day leaderboard, Meridian showed $291K across 17,032 settlements. On @402scan (by @merit_systems), $145K across 8,474. Every other big facilitator matched within a few percent.
The reason was Meridian's settlement design. Each payment is one transaction with two USDC transfers: payer to Meridian's proxy contract, then contract to seller (~99%). Count every USDC transfer per settlement and each payment shows up twice.
We sent the details to the x402-trust team. They shipped a fix the same day, and their audit found the same pattern elsewhere: openx402's settlement count was inflated more than 6x (dollars barely moved), and thirdweb and mogami about 3x, all from fee or dust legs.
Both now show Meridian at about $143K across ~8,300 settlements: roughly 15% of 30-day facilitator volume, third behind Coinbase and FluxA.
Our own weekly review got it wrong twice before we checked the transactions. A leaderboard tells you how much moved and through whom. Before paying a seller, an agent needs narrower answers: has it been paid by distinct wallets recently, and did a paid call actually deliver?
Thanks to the x402-trust team for turning it around in hours, and for publishing a methodology open enough to check.
1
1
198
Independent measurement of the x402 catalog, from x402-trust.com: across monitored endpoints, average 30-day uptime is 52.9%.
Half the catalog is effectively dead weight.
This is why "which endpoint should my agent pay?" can't be answered from a listing. It has to be answered from delivery evidence 👉 like the one our verified_route tool provides.
2
2
85
For reference, our three paid endpoints measure 92.7% uptime and grade A (82.1–82.3) on the same scale. Not self-reported — their probes, their grading. agentpay.tools
1
30
Featured over here 🧡 as we successfully completed M1 💪🏻 M2 coming soon 🤠
In case you missed it, on today's office hours we covered:
- Cycle 2 grantees progress
- Degrants onboarding
- Cycle 3 Endowment Grants applications opening soon
- Q3 TC meeting & preparing next office hours for requests ahead of that meeting
- Collabs and partnerships: Robinhood & Binance UAE
See you on the next call!
xitter.twitterapi.xyz/i/spaces/1yKAPwaRBVbxb
1
3
157
A public x402 trust directory graded our endpoints C and told buyers to avoid us.
Uptime was 86%. That wasn't the problem.
793 of 793 probes had flagged our 402 envelope non-compliant — every day for a month.
1
1
44
Their scoring model, solved from four paid reports:
score = 0.45·reliability + 0.30·compliance + 0.25·economic
Compliance was pinned at its floor. It's worth 21 points — the distance between "avoid" and an A.
1
13
Compliance is a trailing 30-day ratio, so a fix pays back ~0.7 points/day. Worth checking early.
30-second check for your own endpoint:
agentpay.tools/guides/x402-t…
5
We have been busy working on AgentPay's @StacksEndowment grant 🧡
The mission: budget-capped agent payments, settled in Bitcoin. Agents pay per call in sBTC — hard spend cap enforced before signing, receipt after.
M1 is nearly done. Mainnet next 💪🤠
1
37
AgentPay retweeted
Stacks Endowment(@StacksEndowment) の公式発表
「Announcing the Q2 2026 Stacks Endowment Grantees」
の日本語版を公開しました。全文は引用先から読めます。
Q2 2026、Endowment は厳しい市況のなかでもビットコインネイティブ・ファイナンスの基盤へ資金を集中し、10チームを採択しています。
・PaySats(@paysats_) — AIエージェント経由の BTC 貯蓄・借入・DCA
・Jing(@JingSwap_v2) — RFQ / 執行強化による sBTC スワップ
・Covault — sBTC / STX 決済のオプション基盤
・BitYield — BTC 保有者向け利回りダッシュボード
・DeepStack — 自律的な流動性・マーケットメイク
・PerkOS — エージェントのエスクロー・検証・レピュテーション
・AgentPay(@romudille) — sBTC の予算管理付き・検証可能な決済
・Vibewatch(@marshallmixing) — エコシステム・センチメント指数とエージェント可読データ
・Privara(@PrivaraXYZ) — Stacks ネイティブ資産向けプライバシー基盤
・Degen Labs(@DegenLabBTC) — プライバシー基本構成要素と開発者向けインフラ
Stacks(@Stacks)
AgentPay is a @StacksEndowment Q2 grantee 🧡
We're bringing open, non-custodial spend governance to sBTC: budget-capped sessions an agent cannot exceed, and a verifiable on-chain receipt for every call. Now also Bitcoin-native.
Replying to @StacksEndowment
4/ PerkOS: trust, escrow, and reputation for AI agents on Bitcoin
BitYield: consumer-grade access to Bitcoin yield on Stacks
DeepStack: autonomous liquidity and market-making infrastructure
AgentPay: spend controls and verifiable sBTC payments for AI agents @romudille
1
31
Hey all! So @RobinhoodCrypto opened to agents July 1 — 100ms blocks, tokenized stocks, agents trading via MCP. 13,900+ contracts in week one.
What nobody's mentioning: the default x402 catalog can't see the chain. 🧵
1
1
64
3/ We've been building for this since before launch: our settlement contract has run on Robinhood's testnet since June, and our router already speaks the chain — chain=robinhood is a supported target today.
When x402 supply lands there, we route to it day one
1
44
4/ Your Robinhood agent can trade. AgentPay tells it whether it should — trade-safety verdicts, hard budget caps, receipts for every call.
npx @romudille/agentpay-mcp
21







