New — x797 protocol • Solana mainnet • Jito‑routed

Charge & settle inside HTTP.

We rebuilt the x402 idea from scratch and launched x797: a protocol where requests carry a signed payment header. Our dedicated x797 nodes accept the call, route a chain tip/priority fee (currently via Jito), verify the proof, and forward to the target API.

View on Solscan See the flow

Payment header

Only402-Pay: tip=Jito; proof=...

x797 node validates ➜ routes ➜ responds

Simple by design

No accounts, no API keys. Add a single Only402-Pay header. Works for humans and agents.

Fast & affordable

Solana + Jito tips / priority fees. Predictable low latency and on‑chain cost.

Verifiable forever

Every call leaves a public trail. We show a live stream below.

Programmable routes

Incentives, rate caps, destination routing — all handled at the x797 node.

The protocol flow

Client Sends an HTTP request with a signed Only402-Pay header (retries & batching supported).
x797 node Chooses a route (Bribery amount / Jito tip / priority fee), validates the proof, then forwards to the target API.
Settlement On‑chain confirmation, webhooks, and receipts. Everything streamable from public RPC.

Pros

Borderless settlement, no card rails.
Micropayments for LLM calls & metered APIs.
Transparent accounting via public RPC.

Trade‑offs

Public RPC rate limits exist.
Users need a wallet (or managed signer).
Latency varies with network congestion.

Live Transactions

Fake demo feed that starts at 0.100000 SOL and adds micro‑amounts every tick.

Total routed: 0.100000 SOL • $20.00

Demo mode (fake) RPC (HTTPS) Tip accounts Auto refresh (5s)

Signature	Time	Status	From	To	Amount	Value	Token

Why not WebSockets?

Public endpoints often block logsSubscribe in browsers (CORS / limits). HTTPS polling stays reliable without private RPC.

Can I bring my own RPC?

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