Covenant x402

Open-source infrastructure for serving AI agents on-chain.

[Covenant x402 @Convenantx402]

Installed one markdown skill into Claude Code.

The agent hit a live gateway, decoded an HTTP 402 challenge (0.01 USDG · Robinhood Chain 4663), and explained the full x402 payment flow - without touching a wallet.

Then I tested the credential vault: stored a secret, sent it as {{demo_key}} through the broker, and got back [REDACTED:demo_key]. The plaintext never reached the model.

Three things proved in one session:
→ Agents can discover and understand paid APIs from a skill alone
→ x402 payment rails work on Robinhood Chain with USDG
→ Secrets stay encrypted server-side - the model only sees placeholders

Open source. MIT. Live gateway.

Install Skill : https://t.co/rS0TiyBc9j
Clone & Run : https://t.co/bkIcIGHYgp

[Covenant x402 @Convenantx402]

Covenant is open-source infrastructure for agent payments.

not built for one agent. not built for one app.

built for every agent that needs to pay for something onchain. any agent can use Covenant to:

→ discover paid endpoints
→ receive x402 payment requirements
→ authorize USDG payments
→ settle on Robinhood Chain,Base,Arbitrum,Ethereum
→ access paid resources
→ use vaulted credentials without exposing secrets

developers can self-host the gateway, add their own paid endpoints, and let agents pay programmatically.
agent → x402 → USDG → settlement → resource
that's the primitive.

- open source
- MIT
- self-hostable
- no telemetry

we're building the payment rails agents can actually use.

https://t.co/bkIcIGHYgp

[Covenant x402 @Convenantx402]

Covenant 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.

[Covenant x402 @Convenantx402]

we've just burned 37M worth of the tokens from several buybacks! tx proof : https://t.co/k1t4QBLSgq

we’re building Covenant for the long game!

Covenant is not just x402 endpoint, but the payment infrastructure agents can actually use to discover services, pay, access APIs, handle credentials and build onchain reputation.

we're exploring things like agent & provider reputation, staking/deposits, marketplace access, priority routing, fee discounts, premium infrastructure and eventually agent-to-agent coordination.

so you wouldn't hold $COVENANT just to pay for an API USDG does that. you'd use $COVENANT to participate in and access the infrastructure being built around the x402 economy.

we're still shipping the core rails first, so we'd rather make each utility real before turning it into a promise.

[Covenant x402 @Convenantx402]

Huge update is coming into Covenant on the next week! (Tomorrow)

thanks for always supporting the project, Covenantx402 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.

[HenryVu @Henry_VuQuangDu]

I found out something really crazy: there are two $COVENANT tokens.

One is sitting at a $21M MC (yes, $21 million!), while the one I support has only a $16K MC (just $16 thousand!).

But you might end up buying the scam one, the one with the $21M MC

Here is why: 👇

[Covenant x402 @Convenantx402]

Install the skill into a Claude Code project, then let the agent inspect a live 402 before any payment is approved:

git clone https://t.co/bkIcIGHYgp
cd covenant
mkdir -p .claude/skills/covenant-x402
cp skill/SKILL.md .claude/skills/covenant-x402/SKILL.md
claude

Discovery is read-only. Agent keys, vault secrets, wallet creation, and USDG settlement remain explicit actions.

[Covenant x402 @Convenantx402]

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.

[Covenant x402 @Convenantx402]

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.

https://t.co/E8viH6ORMv

[Covenant x402 @Convenantx402]

Day 2 Since $COVENANT went live on @ponsdotfamily.

Our x402 service just got high traffics earlier today! we've reached:

> 5paid APIs registered
> 73 402 payment gates hit
> 16 + 23vault secrets + brokered calls

Gate any API. Agents pay in USDG on Robinhood Chain. Credentials stay in the vault, never the model. Open source, MIT, zero telemetry.

[Covenant x402 @Convenantx402]

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 https://t.co/bkIcIGHYgp. Any agent can install the skill and pay.

[Covenant x402 @Convenantx402]

Covenant 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.

- https://t.co/DG6dzdnXeY 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.

Covenant is open source, MIT licensed, and self-hostable in minutes.

Live: https://t.co/E8viH6ORMv
Gateway: https://t.co/EJYS2Bf6jE
Code: https://t.co/bkIcIGHYgp

[Covenant x402 @Convenantx402]

Serve agents. Get paid per call.

Wire your endpoint in minutes. Settlement in USDG on Robinhood Chain.

Explore app : https://t.co/AUesq0Au5b
Read docs : https://t.co/H8wBVgHib8

[Covenant x402 @Convenantx402]

Hood Morning!

[Covenant x402 @Convenantx402]

Build for agents. Prove it is real."

Install the skill and let an agent discover, pay, and verify — or open the console and watch it happen live.

https://t.co/MdL9CEzpZV

[Covenant x402 @Convenantx402]

x402 is a payment standard, not a product pitch. This is the rails — for anyone serving agents.

[Covenant x402 @Convenantx402]

appreciate it! we’re building Covenant for the long game — not just x402 endpoint, but the payment infrastructure agents can actually use to discover services, pay, access APIs, handle credentials and build onchain reputation.

[Sukuna Crypto @Sukuna_Crypt0]

ath 120k, now sitting at 17k but dev still cooking, i think can hit ath atleast.

$CONVENANT
0x2eef2a627ac024cb9f545f6193b1940f0416a1de

[Covenant x402 @Convenantx402]

6Hours after $Covenant bonded on @ponsdotfamily.

Our x402 service just got high traffics at this beginning.

> 5 paid APIs registered
> 77 402 payment gates hit
> 16 + 23vault secrets + brokered calls

350+ holders reached! Gate any API. Agents pay in USDG on Robinhood Chain. Credentials stay in the vault, never the model. Open source, MIT, zero telemetry.

[Covenant x402 @Convenantx402]

// agent.ts — no secrets in your agent at all
const GATEWAY = 'https://t.co/Zf1KNshOBe' // public gateway (VPS)

// 1. store the secret once (value never returned)
await fetch(GATEWAY + '/vault/entries', {
method: 'POST',
headers: { 'content-type': 'application/json', Authorization: 'Bearer cvn_…' },
body: JSON.stringify({ name: 'llm_api_key', value: https://t.co/gE6YjT2dxv_SECRET })
})

// 2. your agent only ever writes the placeholder — the gateway
// substitutes the real value server-side and scrubs every readback
const r = await fetch(GATEWAY + '/vault/broker', {
method: 'POST',
headers: { 'content-type': 'application/json', Authorization: 'Bearer cvn_…' },
body: JSON.stringify({ text: 'Authorization: Bearer {{llm_api_key}}' })
})
// r.body = "Authorization: Bearer [REDACTED:llm_api_key]" — nothing to leak.

[Covenant x402 @Convenantx402]

Two lines in your agent.

Point your agent's requests at the vault proxy — credentials get attached on the way out, never on the way in.