$TRIBUTE x402 payment rails for agents. 0xd41a1dc8a42e429a66d6ac479e6f8ebf96d6eab0
Joined September 2026
- Tweets105
- Following5
- Followers213
- Likes114
Pinned Tweet
We are officially live on @ponsdotfamily Introducing Tribute x402 payment rails for agents.
Paid endpoints in USDG over x402 — instant settlement on Robinhood Chain. The same gateway brokers agent credentials through a live vault, model-proof by design. Open source, MIT.
Gate an endpoint. Vault a secret. One process.
The gateway is a single zero-dependency Node service: read-only RPC proxy, x402 gates, credential vault, agent wallets, on-chain settlement. Clone it and run — MIT, no telemetry, 21-check smoke test included.
• Instant USDG settlement · chain 4663
• Nonce-replay-guarded, tx-anchored
• Paid sessions — settle once, call N times
• Self-host in minutes from GitHub
Clone & Run : github.com/tributelab/tribut…
CA : 0xD41A1DC8A42E429A66d6AC479E6F8Ebf96d6eAb0
tributex402.com/
Serve agents. Get paid per call.
Wire your endpoint in minutes. Settlement in USDG on Robinhood Chain.
Explore app : tributex402.com/#/app
Read docs : tributex402.com/#/docs
The gateway is a single zero-dependency Node service: read-only RPC proxy, x402 gates, credential vault, agent wallets, on-chain settlement. Clone it and run — MIT, no telemetry, 25-check smoke test included.
> Instant USDG settlement · chain 4663
> x402 v2 + Bazaar discovery, dual-served with v1
> Nonce-replay-guarded, tx-anchored
> Paid sessions — settle once, call N times
> Self-host in minutes from GitHub
Clone & Run : github.com/tributelab/tribut…
TRIBUTE is now multichain.
Agents paying for APIs shouldn’t need to care which chain settles the call. As of today, the same x402 flow runs across:
- Robinhood Chain 4663 (USDG, the original rail)
- Ethereum mainnet (native USDC)
- Base (native USDC)
- Arbitrum One (native USDC)
One signed EIP-712 PaymentIntent. One endpoint. The chain is now a parameter, not a rewrite.
How it works:
1. The agent hits an endpoint and receives a 402 with the price, asset, and spender for the selected chain.
2. The agent signs a PaymentIntent in that chain’s domain.
3. The gateway verifies the signature, balance, and allowance, executes `transferFrom` on-chain, and mints a receipt.
4. The receipt unlocks the resource - per-call or a 100-call session, just like before.
The boring but important part is what we did before touching money:
• Every USDC address was verified on-chain via `eth_call` before shipping. No explorer copy-paste.
• BNB Chain was evaluated and rejected. The “USDC” there is bridged, uses 18 decimals instead of 6, and has no EIP-3009. Mixing that into 6-decimal payment logic is how silent wrong-amount bugs happen. It stays out until it’s audited end to end.
• The production DB was migrated atomically. Nonce replay protection and settlement history carried over in a single transaction, then tested against real production data before deploy.
• Chain binding is enforced everywhere. A receipt settled on Ethereum cannot unlock a Base-selected resource, even if the client lies in the intent. Settlement rejects resource/chain mismatches before any transfer.
• `intent.to` and the amount must match the gateway’s quoted price. No paying yourself 1 wei to unlock a route.
• `/chains` exposes live readiness for every rail: RPC status, block height, and settlement-wallet gas. The UI blocks payments on rails that can’t actually broadcast. No fake green dots.
Also live: the marketplace is no longer an empty shell.
The first real listing is a Coinbase-powered ETH/USD spot price feed with pay-per-call access, server-side fee splits for sellers, and a full refund if the seller endpoint fails.
Status right now:
31/31 gateway checks passing.
Frontend rebuilt.
Everything deployed.
Robinhood Chain is fully settled and ready.
Ethereum, Base, and Arbitrum RPCs are green and will go live for settlement as soon as the facilitator wallet is funded with gas on each chain.
The UI shows that honestly instead of pretending everything is ready when it isn’t.
Payment infrastructure for agents shouldn’t be a waitlist.
TRIBUTE is open source, MIT licensed, and self-hostable in minutes.
Live: tributex402.com
Gateway: api-gw.tributex402.com
Code: github.com/tributelab/tribut…
TRIBUTE is now multichain.
Agents paying for APIs shouldn’t need to care which chain settles the call. As of today, the same x402 flow runs across:
- Robinhood Chain 4663 (USDG, the original rail)
- Ethereum mainnet (native USDC)
- Base (native USDC)
- Arbitrum One (native USDC)
One signed EIP-712 PaymentIntent. One endpoint. The chain is now a parameter, not a rewrite.
How it works:
1. The agent hits an endpoint and receives a 402 with the price, asset, and spender for the selected chain.
2. The agent signs a PaymentIntent in that chain’s domain.
3. The gateway verifies the signature, balance, and allowance, executes `transferFrom` on-chain, and mints a receipt.
4. The receipt unlocks the resource - per-call or a 100-call session, just like before.
The boring but important part is what we did before touching money:
• Every USDC address was verified on-chain via `eth_call` before shipping. No explorer copy-paste.
• BNB Chain was evaluated and rejected. The “USDC” there is bridged, uses 18 decimals instead of 6, and has no EIP-3009. Mixing that into 6-decimal payment logic is how silent wrong-amount bugs happen. It stays out until it’s audited end to end.
• The production DB was migrated atomically. Nonce replay protection and settlement history carried over in a single transaction, then tested against real production data before deploy.
• Chain binding is enforced everywhere. A receipt settled on Ethereum cannot unlock a Base-selected resource, even if the client lies in the intent. Settlement rejects resource/chain mismatches before any transfer.
• `intent.to` and the amount must match the gateway’s quoted price. No paying yourself 1 wei to unlock a route.
• `/chains` exposes live readiness for every rail: RPC status, block height, and settlement-wallet gas. The UI blocks payments on rails that can’t actually broadcast. No fake green dots.
Also live: the marketplace is no longer an empty shell.
The first real listing is a Coinbase-powered ETH/USD spot price feed with pay-per-call access, server-side fee splits for sellers, and a full refund if the seller endpoint fails.
Status right now:
31/31 gateway checks passing.
Frontend rebuilt.
Everything deployed.
Robinhood Chain is fully settled and ready.
Ethereum, Base, and Arbitrum RPCs are green and will go live for settlement as soon as the facilitator wallet is funded with gas on each chain.
The UI shows that honestly instead of pretending everything is ready when it isn’t.
Payment infrastructure for agents shouldn’t be a waitlist.
TRIBUTE is open source, MIT licensed, and self-hostable in minutes.
Live: tributex402.com
Gateway: api-gw.tributex402.com
Code: github.com/tributelab/tribut…
Huge update is coming intro Tribute on the next week!
thanks for always supporting the project, Tribute x402 payment rails for agents. Paid endpoints in USDG over x402 v2 — instant settlement on Robinhood Chain. The same gateway brokers agent credentials through a live vault, model-proof by design. Open source, MIT.
402 is a payment standard, not a product pitch. This is the rails — for anyone serving agents.
1. Payments, not promises
Every call is metered and paid — per-request USDG settlement over x402, or one settlement for a whole session. No credits, no subscriptions.
2. Model-proof vault
Agent credentials never enter a prompt or context window. The vault substitutes and scrubs server-side; the model only ever sees [REDACTED].
3. Identity with receipts
Per-agent wallets, API keys, and a reputation score built from settled payments — every point anchored to a verifiable transaction hash.
4. Open source, MIT
Gateway, kit, tests and the agent skill — all public at github.com/tributelab/tribut…. Any agent can install the skill and pay.
Tribute app has been updated to v2.
explore and try any feature that accessible : tributex402.com/#/app
v1 and v2, served on every call — not one or the other
Every paid route answers a 402 with the legacy v1 JSON body and a spec-compliant v2 header, encoded with the official @x402/core codec. Old integrations keep working; new scanners and facilitators that expect v2 see it immediately.
v1 · legacy, still served
>> JSON body challenge
>> maxAmountRequired field
>> OpenAPI-only discovery hack
v2 · current spec
>> Payment-Required header (base64)
>> amoun field, scheme-agnostic
>> extensions.bazaar — first-class discovery
One paid call → fully measured.
This is the actual TRIBUTE gateway on this server — paid-API registry, x402 gate, and the agent credential vault — reporting live. Fresh counters are honest counters: every number here maps to a real event you can trigger in the Console.
> 5 paid APIs registered
> 80 402 payment gates hit
> 9 + 14vault secrets + brokered calls
The gateway is a single zero-dependency Node service: read-only RPC proxy, x402 gates, credential vault, agent wallets, on-chain settlement. Clone it and run — MIT, no telemetry, 24-check smoke test included.
> Instant USDG settlement · chain 4663
> x402 v2 + Bazaar discovery, dual-served with v1
> Nonce-replay-guarded, tx-anchored
> Paid sessions — settle once, call N times
> Self-host in minutes from GitHub
Clone & Run : github.com/tributelab/tribut…
appreciate it! we’re building TRIBUTE for the long game — not just another x402 endpoint, but the payment infrastructure agents can actually use to discover services, pay, access APIs, handle credentials and build onchain reputation.
we’ve also already burned 18.5% of the total $TRIBUTE supply.
more rails, more integrations, more agents, more real onchain activity. we’re just getting started.
Tribute v2 now is live : tributex402.com
$TRIBUTE x402 payment rails for agents.
Paid endpoints in USDG over x402 v2 — instant settlement on Robinhood Chain. The same gateway brokers agent credentials through a live vault, model-proof by design. Open source, MIT.
TRIBUTE gateway just shipped a real backend upgrade — two parts, both substantial.
1. Protocol: migrated x402 from v1-only to genuine v1+v2 dual-mode. Not a relabel — real v2 payment headers with amount fields, object-shaped resources, and Bazaar discovery extensions baked into every 402 challenge. v1 callers keep working exactly as before, zero downtime, zero breaking changes. Full test suite expanded and passing 24/24 after the cutover.
2. Storage: every piece of stateful data in the gateway — agent credentials, API keys, agent wallets, paid sessions, reputation scores, on-chain settlement history — used to live in flat JSON files that got fully rewritten on every single transaction. That's O(n) write cost per mutation, no indexing, no real crash safety beyond a tmp-file-rename trick.
Migrated the entire persistence layer to SQLite with WAL mode. Indexed lookups instead of full in-memory scans. O(1) writes regardless of how much history has accumulated. Ran a full production data migration before cutover — every settlement, every credential, every agent wallet carried over with zero data loss, verified byte-for-byte against pre-migration health checks.
Neither of these is user-facing. No new button, no new page. But it's the difference between a payment rail that demos well and one that actually holds up as real volume runs through it.
TRIBUTE x402 update: we found out why TRIBUTE couldn't register on x402scan.com.
it wasn't our endpoint.
it wasn't the x402 implementation.
the issue is on the validator side: x402scan currently uses a blockchain whitelist, and Robinhood Chain (4663) isn't supported yet.
so even though TRIBUTE returns a valid x402 response, the validator rejects it and shows:
“No valid x402 response found.”
we traced the issue directly in the x402scan source code, built a patch that allows chains outside the current whitelist to be validated, and submitted it upstream as PR #1193.
so the fix belongs on the x402scan side, not TRIBUTE.
we're keeping the rails live and will keep pushing until Robinhood Chain is properly recognized by the broader x402 ecosystem.
TRIBUTE is ready.
now we're helping the tooling catch up.
TRIBUTE x402 FLOW : One paid call → fully measured.
> 5paid APIs registered
> 75 402 payment gates hit
> 9 + 14vault secrets + brokered calls
This is the actual TRIBUTE gateway on this server — paid-API registry, x402 gate, and the agent credential vault — reporting live. Fresh counters are honest counters: every number here maps to a real event you can trigger in the Console.
tributex402.com/
Pay an API in 3 clicks. What you're paying for, and what comes back.
1. Open Paid APIs and hit PAY on any route.
2. Your wallet asks for two signatures: an approve (lets the facilitator move your USDG) and a payment intent (free, EIP-712).
3. The gateway settles on-chain and returns the paid payload — real headlines, pools and signals — with the tx hash.
you can also wire your own agent, The product ships as a skill + example code.
Give your agent the skill file and it can pay APIs autonomously: git clone github.com/tributelab/tribut…
cd tribute && npm i
node examples/pay.js # 402 → sign → settle → content
Agent keys mint right here in the sidebar — they unlock the vault, wallets and per-key analytics.
we've been a little quiet lately.
not because we're slowing down — we're heads down building the x402 scanner for TRIBUTE.
the goal is to make agent payment activity easier to discover, track, and understand across the network.
we're still shipping updates whenever we can, and we'll keep pushing as hard as possible without sacrificing the quality of what we're building.
and yes, buybacks are still part of the plan.