x301.fun System Online
x402-inspired • Layered over Jito Tip • Solana Mainnet

Autopay for Web, AI & APIs

We took the x402 idea and built a new layer on top of Jito Tip — so HTTP can charge and settle by itself.

View Live TXs on Solscan See Architecture

Simple

No accounts, no API keys. Pay-per-request with a single header. Works for people and agents.

Fast & Cheap

Solana + Jito priority fees. Millisecond confirmation paths with low on-chain cost.

Verifiable

Every call leaves an on-chain trace. We stream transactions below in real time.

Pros

  • Borderless settlement; no card rails.
  • Micropayment-friendly for AI calls & APIs.
  • Programmable: incentives, routing, rate caps.
  • Transparent accounting via public RPC.

Trade‑offs

  • RPC rate limits on public endpoints.
  • Users need a wallet (or managed signer).
  • On-chain latency varies by congestion.
🧩

Client

HTTP request → `Only402-Pay` header → sign & send tip via Jito. Retries & batching on.

🧠

Payment Layer

Router selects route (Jito Tip / priority fee). Verifies proof and forwards to target API.

🔗

Settlement

On-chain confirmation, webhooks, and receipts. All tx are streamable via public RPC.

1
Client sends an HTTP call with a signed `Only402-Pay` header.
2
Router tips via Jito + sets priority fees; validates receipt.
3
Target API executes; result is returned instantly.
4
Tx appears in the live feed below. Done.
We use getSignaturesForAddress (merged across tip accounts) and resolve each new signature with getTransaction for status & fee. Starts automatically — no buttons.

Live Transactions

Streaming via HTTPS polling (public RPC friendly)
Total routed: 0.350000 SOL • $69.69
Signature Time Action From To Amount Value Token

Why not WebSockets?

Public endpoints often block `logsSubscribe` in browser contexts (CORS / rate limits). HTTPS polling stays reliable without private RPC.

Can I bring my own RPC?

Yes. Paste any HTTPS RPC in settings; feed restarts automatically. For production, use a pooled provider.