Pinned Tweet
AI agents paying for APIs is only one part of the puzzle.
What happens after the payment?
With Covenant, we're building around the full workflow:
→ Discover paid APIs
→ Pay through x402
→ Access credentials securely
→ Build verifiable onchain reputation
We recently tested this end to end with @TokyoFuturo : an agent paid 0.05 USDG for live crew intel through our marketplace, received the data, and used it in a separate game workflow. robinhoodchain.blockscout.co…
robinhoodchain.blockscout.co…
robinhoodchain.blockscout.co…
Would love to explore how Covenant's marketplace and reputation layer could work alongside the broader x402 ecosystem.
Building in the open. 🤝@PayAINetwork
8
17
699
Since opening the project as open source from day one, @HeyResearch has become our first ecosystem participant.
We're glad to have them involved as we continue building multi-chain x402 payment rails and infrastructure for AI agents.
Open source means more than making the code public. It's about giving others the chance to explore, contribute, build on top of it, and grow the ecosystem together.
Welcome to Covenant, @HeyResearch
Gate any API. Agents pay in USDG on Robinhood Chain. Credentials stay in the vault, never the model. Open source, MIT, zero tele
github.com/covenantx402/cove…
Day 14 of $COVENANT x402 payment rails
for agents.
→ 77 402 payments gate hits
→ 73 on-chain · approve+transferFrom
→ 2.08 USDG settled
→ 12 known agents
→ 29 vault secrets
→ 18 brokered calls
→ 5 paid APIs
→ 9 live routes
→ 13 Events · 24h
Gate any API. Agents pay in USDG on Robinhood Chain. Credentials stay in the vault, never the model. Open source, MIT, zero telemetry.
covenantx402.com
1
5
324
Covenant x402 retweeted
gm to the
agent enjoyers
defi enjoyers
memestock enjoyers
meme enjoyers
gm to the entire pons family
Covenant marketplace already live, and external APIs are already getting paid calls.
current snapshot on Robinhood Chain:
→ 3 APIs listed
→ 5 settled purchases
→ 0.200 USDG in seller payouts
→ 95% of each call goes to sellers
@TokyoFuturo crew intel is already live at 0.05 USDG per call, with 4 paid calls recorded.
anyone can list an API with a wallet signature. no account needed.
we're building toward a marketplace where agents can discover services, pay for data, and use APIs without the usual friction.
covenantx402.com/#/app
9
12
505
Hey @PayAINetwork team.
We've been building Covenant, an open-source x402 marketplace focused on agent-to-API payments, secure credential handling, and onchain agent reputation.
We've been testing real paid API workflows with Tokyo Futuro on Robinhood Chain, including an agent paying for live game intel and receiving the data through our gateway.
I'd love to explore a technical integration with PayAI as a facilitator option on supported networks, with Covenant handling the marketplace, credential layer, and agent reputation.
I think there's an interesting opportunity to connect payment infrastructure with the services and workflows agents actually use.
Would your team be open to a short technical discussion or joint demo? Happy to share the implementation and transaction receipts.
covenantx402.com
🧵 Weekly Recap — Oct 25
Mastercard built agent payments on x402. Circle taught Claude Code to charge in USDC. Solana got ~150ms finality.
And outside agents started buying from Kognai’s swarm.
The big names built the rails. The agents used them. Here’s the week 👇
5
12
624
One early example is @TokyoFuturo, an agentic game on Robinhood Chain that provides live city intelligence to agents through paid x402 endpoints.
Its marketplace listings include:
> Tokyo Futuro crew intel — 0.05 USDG per call.
> Tokyo Futuro raid planner — 0.10 USDG per call.
The endpoints return JSON based on public onchain city data, including information about crews, districts, and raids.
The integration has moved beyond a listing announcement. Tokyo Futuro reported testing a paid request through Covenant, with an approval transaction, a settlement transaction, and the resulting intelligence delivered to the agent.
The teams have also run a broader demonstration in which an agent paid for crew intelligence, read the response, and then played Tokyo Futuro's daily Trial as a separate step.
In the reported run, the agent completed the Trial called “The Stockroom Haul” with a score of 1,000 and a perfect result.
This is an important distinction: the paid intelligence supports the agent's decision-making, while the Trial remains a separate game activity. The example demonstrates a practical workflow connecting a paid API to a subsequent agent action.
The next opportunity is to make this kind of interaction easier for other service providers and agents to reproduce, with transaction receipts and execution logs to support the demonstration.
covenantx402.com/#/app
Instead of every agent needing a custom integration with every provider, the marketplace provides a common place to find services and access their payment requirements.
Covenant's dashboard showed three open API listings, five settled purchases, and 0.200 USDG in seller payouts. The marketplace displayed a 5% platform fee, with 95% of each call going to sellers.
These are live dashboard figures from a particular point in time, not fixed totals.
2
2
382
Instead of every agent needing a custom integration with every provider, the marketplace provides a common place to find services and access their payment requirements.
Covenant's dashboard showed three open API listings, five settled purchases, and 0.200 USDG in seller payouts. The marketplace displayed a 5% platform fee, with 95% of each call going to sellers.
These are live dashboard figures from a particular point in time, not fixed totals.
This is why onchain verification matters.
We’re reviewing Covenant’s settlement data openly, separating internal tests from external usage, and working to keep the public numbers accurate.
Respect to everyone checking the data and holding us accountable!
Covenant x402's settlements, checked on chain, shared with them privately first.
Robinhood Chain, to 23 Oct: 124 settlements, 3.30 USDG
• 87 are Covenant paying itself (Sep tests): 1.66 USDG
• 37 from outside wallets: 1.64 USDG, including 21 since launch (0.37 USDG from 5 wallets)
Their new proof page lists 69. It misses 52 self-tests and 3 outside payments (0.07 USDG), and says 35 self-tests where its breakdown adds to 32.
Since then, to today: 3 more outside settlements (0.03 USDG) from 1 new wallet.
Credit to them for publishing a ledger that can be checked.
1
4
351
Day 7 of $COVENANT x402 payment rails
for agents.
→ 73 402 payments gate hits
→ 69 on-chain · approve+transferFrom
→ 2.04 USDG settled
→ 11 known agents
→ 29 vault secrets
→ 18 brokered calls
→ 5 paid APIs
→ 9 live routes
→ 53 Events · 24h
Gate any API. Agents pay in USDG on Robinhood Chain. Credentials stay in the vault, never the model. Open source, MIT, zero telemetry.
3
264
Payment infrastructure becomes more useful when agents have services worth paying for.
That's why Covenant includes an API marketplace where external sellers can list paid endpoints.
Sellers can create listings through the gateway's listing flow using a wallet signature, without needing a traditional marketplace account. Buyers can discover available services, fund their buyer balance with USDG, and call APIs using an API key.
The marketplace is designed to make paid services easier to discover and consume programmatically.
Covenant marketplace is live, and external APIs are already getting paid calls.
current snapshot on Robinhood Chain:
→ 3 APIs listed
→ 5 settled purchases
→ 0.200 USDG in seller payouts
→ 95% of each call goes to sellers
@TokyoFuturo crew intel is already live at 0.05 USDG per call, with 4 paid calls recorded.
anyone can list an API with a wallet signature. no account needed.
we're building toward a marketplace where agents can discover services, pay for data, and use APIs without the usual friction.
covenantx402.com/#/app
3
220
Covenant's payment flow is designed to connect API access with onchain settlement.
On Robinhood Chain, the implementation uses an approval and transferFrom-based settlement flow rather than assuming that every token supports the same authorization mechanism.
The payment process involves the payer authorizing the required token allowance, signing the relevant payment intent, and having the facilitator validate and execute the settlement.
The facilitator can check the payment parameters, signature, balance, allowance, validity window, and replay protection before moving funds.
Once the settlement succeeds, the requested resource can be delivered.
The distinction matters: receiving a payment challenge is not the same as completing a payment. A successful paid request should be backed by a valid settlement and the corresponding service response.
Covenant also supports paid API sessions, where a single payment can authorize multiple calls within the session's rules. This can reduce the overhead of settling every request independently.
The intention is to make paid API access practical for agents that need to make repeated calls while preserving a verifiable payment record.
4
190
Traditional API integrations usually assume a human is behind the process.
Someone creates an account, obtains an API key, configures billing, and decides which services an application can access.
That model becomes more complicated when an AI agent needs to discover and use services dynamically.
An agent might need live market data, specialized research, private API access, or information from another agent-operated service. If every new integration requires a human to manually configure payment and access, autonomy becomes limited.
Covenant uses x402, a payment protocol built around HTTP's 402 Payment Required response, to support a different workflow.
A service can communicate that payment is required, provide payment instructions, and make its resource available after the payment has been settled.
A typical interaction looks like this:
- An agent requests a paid resource.
- The gateway returns an HTTP 402 response with-payment requirements.
- The agent follows the payment flow using the supported payment method.
- The payment is verified and settled.
- The agent receives the requested resource.
This allows payment requirements to become part of an API interaction instead of requiring every service to build a completely separate billing experience.
For Covenant, the initial focus is USDG payments on Robinhood Chain, which uses chain ID 4663.
1
8
403
Think a number is wrong?
Open a public challenge on GitHub (a free GitHub account is needed). Paste your own count and how you got it, and we will answer in the same thread with transaction hashes.
Every settlement, with a hash.
Each settlement is one successful payment with a transaction hash. Nothing here comes from wallet activity or estimates.
> 69 settlements
> 2.04USDG settled
> 34 external payers
> 35 self-tests
covenantx402.com/#/proof
6
287
Every settlement, with a hash.
Each settlement is one successful payment with a transaction hash. Nothing here comes from wallet activity or estimates.
> 69 settlements
> 2.04USDG settled
> 34 external payers
> 35 self-tests
covenantx402.com/#/proof
Hit a paid API. See the 402.
Pick a route and send a real, unpaid request to the live gateway. It answers with a payment requirement. Nothing is charged.
6
259
COVENANT update: you can now verify everything we claim.
This release was built around one question: Can you verify it yourself?
Here’s what shipped.
1. PROOF PAGE
Every settlement now has its own proof page with the tx hash, split between external payers and self-tests.
Click **“Verify on-chain”** and your browser queries a public Robinhood Chain node for every payment:
Did it succeed?
Did the exact amount move between the expected wallets?
Our servers are not involved in that check.
2. RECEIPTS
Every settlement has its own receipt with the payer, amount, verification button, and share card.
Paste any tx hash into the lookup to see whether it is a COVENANT settlement — and what type.
(TRY IT — NO WALLET REQUIRED)
Pick any paid API on the landing page and send an unpaid request to the live gateway.
You’ll get a real HTTP 402 response with the price, network, and payee.
There’s also a **“Pay for real”** button that settles $0.01 USDG from our demo wallet.
Those payments are labeled **“live demo”** in the ledger and never counted as usage.
3. RUN IT IN YOUR TERMINAL
```bash
curl -O covenantx402.com/verify-ledg…
node verify-ledger.mjs
```
No dependencies.
It exits non-zero if any settlement does not match the chain, so you can also run it in CI.
4. FOR SELLERS
List-your-API now includes a live test step before you sign.
You can see exactly how your endpoint responds and how much you would keep per call.
Listings also get a **“settled via COVENANT”** badge for your README, generated from the real ledger and counting external payments only.
5. STATUS
A 30-day uptime strip is now live.
Recording started today, so most bars are grey.
We do not backfill history we did not record.
>> CONSOLE + MCP
The console now has:
• Proof — ledger, verification, tx lookup
• Receipt links in Billing
• Uptime in Status
MCP 0.3.1 adds:
• `covenant_audit`
• `covenant_audit_snapshot`
Agents can read the same numbers.
**WHAT WE HAVE NOT PROVEN**
We have not proven that our external payers are independent customers.
Volume is still small and early.
That’s the point of this release:
You can check the claims yourself instead of taking our word for them.













