← Back home · Compare
Njord vs x402 (HTTP 402 stablecoin payments)
Agentic-payments standard: the HTTP 402 revival for stablecoin, per-request payments between agents and services
x402 and Njord are aimed at the same 2026 narrative — autonomous agents that pay on-chain without a human approving each transfer — from different layers. x402 is a per-request wire protocol: two parties, pay-as-you-call. Njord is a funded, multi-party escrow that settles per verified action, with fee splitting, budget ceilings, and a public ledger. They are complementary: a 402 response could settle against a Njord escrow, giving an agent a capped budget it cannot overspend.
| Feature | Njord | x402 (HTTP 402 stablecoin payments) | Advantage |
|---|---|---|---|
| Layer | On-chain escrow program (multi-party) | HTTP wire protocol (two-party) | Comparable |
| Budget model | Pre-funded escrow with a hard ceiling | Pay-per-request; no shared budget | Njord |
| Multi-party payout | Native — funder / agent / bridge split | No — client pays server directly | Njord |
| Settlement asset | USDC / SOL on Solana | Stablecoins (chain-dependent) | Comparable |
| Per-tx cost | ~$0.00025 | Chain-dependent (often higher on EVM L2s) | Njord |
| Audit trail | Public on-chain accounts per action | Depends on the implementation | Njord |
| Fraud / dispute handling | Stake-backed challenge window + tiers | Not in scope | Njord |
| Maturity | Devnet live; agent API on roadmap | Spec + tooling shipping | x402 (HTTP 402 stablecoin payments) |
Pick Njord when
- ▸You need a funded budget an agent cannot overspend, not an open-ended pay-per-call wire
- ▸You need to split a payout across more than two parties (funder, agent, service, bridge)
- ▸You want every action recorded on a public, auditable ledger for reconciliation and dispute
- ▸You want the escrow, fraud-challenge, and reputation machinery that a bare payment protocol does not provide
Pick x402 (HTTP 402 stablecoin payments) when
- ▸You just need a client to pay a server per HTTP request, two-party, with no notion of a campaign or budget
- ▸You want a thin, transport-level standard rather than an on-chain escrow program
- ▸You are settling on an EVM chain or a stablecoin rail x402 already targets
- ▸You need it in production today — x402 tooling is shipping while Njord mainnet is pending
Still deciding?
Most teams run more than one rail in parallel during a transition. Try Njord behind a feature flag for the affiliate segment where latency-to-cash matters most and keep x402 (HTTP 402 stablecoin payments) for the rest.