Proof, not projection
Paid calls on this rail. Counted by the proxy. Nothing else.
Paid callsN/A
Sluzen
No pay, no data.
Agents pay. Then your API answers.Settled in XRP.
Your API only answers after the ledger confirms payment. Unpaid calls never reach you.
Your compute is not a free sample. Get paid when agents use your data, models, or tools.
No pay, no data.
Your API only answers after the ledger confirms payment. Unpaid calls never reach you.
Your compute is not a free sample. Get paid when agents use your data, models, or tools.
How you start
Keep your API. Set one price.
Sluzen sits in front of the origin you already run. You do not rewrite the product. Callers never talk to you unpaid.
- Use the origin you have
Point a public route at the URL you already serve.
- Unlock with the key you received
There is no public signup. Paste the issuer key, accept the terms, and you are in.
Open product → - Set price and where you get paid
One number per route. That amount settles to your XRPL address — not to Sluzen.
What you pay — and what you do not
Three layers. You set one.
- Your price
- You set itCallers pay it on every settled call. It lands on your XRPL address.
- Ledger fee
- The XRP Ledger sets itCallers pay network dust. Not you. Not Sluzen.
- Sluzen take
- You pay this0.8% of settled volume, from prepaid credits, on mainnet only. Not added to the caller’s price.
Platform take
On mainnet you are billed 0.8% of settled request-price volume from call 1, from non-refundable API fee credits. Testnet does not levy.
Keys and credits are issued privately — not in this public UI. Your price still settles to you.
Callers
They pay. Then they get the payload.
You do not run their wallet. They hit your priced route, pay the amount it states, and ingest the response. After you register a route, the product gives you a snippet to share.
First questions
What is this?
Sluzen sits in front of your HTTP API. Callers pay. You set the price. The XRP Ledger settles. Then your origin answers.
How do I start?
Keep your origin. Unlock the product with the issuer key you received. Set one price per route and the XRPL address where you get paid. The request price settles to you, not to Sluzen.
Why "No pay, no data"?
Your API only answers after the ledger confirms payment. Unpaid calls never reach you.
Do I sign up here?
No. This is not a public signup. You unlock the product with the key the operator issued after your issuer file. Callers do not create an account.
What do I pay Sluzen?
0.8% of settled volume, from non-refundable API fee credits, on mainnet only. Callers pay your request price plus ledger dust. That 0.8% is not added to their price.
Where does my price settle?
To your classic XRPL address — the one you set on the route. Sluzen does not receive that payment. The 0.8% platform take is billed from prepaid credits: not redeemable, not withdrawable.
What happens when a caller hits my route?
If unpaid, the route states its price (HTTP 402), not a payload. They pay. The ledger confirms. Then Sluzen forwards the request to your origin.
Is this a wallet, an exchange, or a marketplace?
No. Sluzen is a payment rail in front of the API you already run. You are not opening a wallet here. Callers keep their own seed. The request price settles to you, not to Sluzen.
Do I paste a wallet seed?
No. Never paste a seed into sluzen.network. You set a receive address. Callers sign on their side.
Settled in XRP — what does that mean?
XRP is the settlement unit. XRP Ledger is the rail. Not a company logo. Not a banner.
Is this Testnet?
The live feed reports the environment the proxy is on — testnet or mainnet. The 0.8% share is levied only on mainnet.
How do I see paid calls?
Settled-call count on this page. Full feed on Live. Both bind to the same public totals — nothing else is invented.
Where are the terms?
How Sluzen works, the Terms of Service, and the Privacy Policy are on this site. Using the product means you accept the terms.