Sluzen: No pay, no data.

How you start

Keep your API. Set one price.

Your API stays on the server you already run. You do not rewrite it. Sluzen can sit in front of that URL, or settle the HTTP 402 your server already returns.

Use the origin you have
Point a public path on Sluzen at the URL you already serve. An unpaid call gets HTTP 402 from Sluzen and never reaches you. After the XRP Ledger confirms payment, Sluzen forwards the request and returns your response.
If callers should stay on your https URL, register that URL to store the price. The Sluzen 402 comes from the snippet you paste on that server. Your server asks Sluzen to settle only after your handler succeeds, then returns the body. If you skip settle, the caller is not charged.
On a proxy route you can charge only if your API responds OK. Sluzen calls your API before it submits the payment. The signed payment stays on Sluzen. A response outside 2xx is not charged. A 2xx body is returned after the ledger confirms.
Compare trust by mode →
Unlock with the key you received
There is no public signup. Paste the issuer key, accept the terms, and you are in. A facilitator resource, or a proxy route that charges only after your API responds OK, also needs the rail terms.
Open the console →
Set price and where you get paid
Default: one price per route in XRP to your classic XRPL address. You may instead opt into allowlisted RLUSD on XRPL or canonical USDC on Base (compatible with HTTP 402 settlement verification on Base for canonical USDC).

What you pay, and what you do not

Three layers. You set one.

Your price: You set itCallers pay it on every settled call. Default XRP and allowlisted RLUSD land on your XRPL address. Canonical Base USDC lands on your EIP-55 0x… address.
Network fee: The network sets itOn XRPL routes, callers pay ledger dust. On Base USDC routes, callers pay ETH gas. Not you. Not Sluzen.
Sluzen take: You pay this0.8% of settled volume, from prepaid XRP 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 are issued privately. After you unlock, you see your own prepaid capacity for the commission. Your price still settles to you.

How Sluzen works →

Callers

They pay. Then they get the payload.

You do not run their wallet. On the default proxy they pay the amount it states, then the payload comes through the Sluzen gate after the ledger confirms, and the product gives you a snippet for that path. On a facilitator resource they stay on your https URL, and your server settles only after the handler succeeds.

Price a route →

Integrators

Evaluate the rail without an issuer key

Hit the public demo for HTTP 402, open OpenAPI on this origin, then check Proof and Live. The short path is on Developers.

Developers →

First questions

What is Sluzen?

On the default route, Sluzen is the payment gate in front of the HTTP API you already run. You set the price. Callers pay that price in XRP by default; the XRP Ledger confirms payment to your address, then your API answers. You may instead opt into allowlisted RLUSD on XRPL or canonical USDC on Base; the 0.8% platform take still comes from prepaid XRP credits. The other two ways to sell a call are in the questions below.

How do I start?

Your API stays on the server you already run. Sluzen does not host it, and you do not rewrite it. On the default route you enter that server’s URL. Callers use the public path you set on Sluzen. Sluzen forwards a call to your server only after the ledger confirms payment.

You open the console with the email on your issuer file (magic link) or the issuer key shown once at onboard. There is no signup form on this site. Default price is XRP (minimum 0.01 XRP per call on mainnet; off mainnet the console may allow 0.001 XRP) to a classic XRPL address (starts with r). You may instead opt into allowlisted RLUSD on XRPL or canonical USDC on Base; the 0.8% platform take still comes from prepaid XRP credits. Sluzen is not paid the request price. If your API already returns HTTP 402, or you charge only when your API responds OK, the order is different.

What if my API already returns 402? →

Open the console →

Why "No pay, no data"?

On the default route, your API answers after the XRP Ledger confirms payment. An unpaid call gets HTTP 402 from Sluzen and never reaches your API.

Read the gate →

Do I sign up here?

No. This is not a public signup. Primary unlock is an email magic link to the billing address on your issuer file. Pasting the issuer key is secondary. Callers of your API do not create an account here. They call the route, pay, and receive the response.

Open the console →

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 on XRPL routes, or ETH gas on Base USDC routes. That 0.8% is not added to their price. Prepaid credits stay in XRP drops even when the request price is allowlisted RLUSD or canonical Base USDC.

A new production key may receive a one-time Introductory Fee Waiver: 100% of that 0.8% for a fixed window. It is not withdrawable. After the window, the take resumes from prepaid capacity.

How fees work →

Why is the minimum 0.01 XRP?

On mainnet, a new route must be priced at least 0.01 XRP (10 000 drops). Off mainnet (testnet or unknown, from the proxy health environment) the create minimum is 0.001 XRP (1 000 drops). That floor is in XRP drops, not dollars. Routes already stored below the current create floor still sell; create is what the floor blocks.

Many agent runtimes cap spend near $0.01 per call. That cap is theirs, not Sluzen’s. When XRP is above about $1, 0.01 XRP can sit above a $0.01 cap (illustrative only: at about $2/XRP, 0.01 XRP is about $0.02). Raise the caller’s cap, or price in drops the caller can spend. Do not treat 0.01 XRP as “under $0.01”.

How fees and settlement work →

Where does my price settle?

Default: your classic XRPL address (the one you set on the route). Allowlisted RLUSD also settles to a classic r… address. Canonical Base USDC settles to the EIP-55 0x… address on that route. Sluzen does not receive the request price. The 0.8% platform take is billed from prepaid XRP credits (not redeemable, not withdrawable).

What happens when a caller hits my route?

On the default route, if the call has not been paid, Sluzen answers with HTTP 402 and the price. It does not return your data, and it does not send the call to your API. The caller pays that price in XRP to your address, and signs the payment in their own software. Sluzen submits that already-signed payment and waits for the XRP Ledger to confirm it. After confirmation, Sluzen forwards the request to your API and returns your API’s response.

If your API already returns HTTP 402, or you charge only when your API responds OK, that order does not apply. Who the caller trusts on each mode is in the trust table.

What if my API already returns 402? →

Compare trust by mode →

Who does the caller trust?

On the default proxy, Sluzen does not forward to the origin until the XRP Ledger returns tesSUCCESS. The caller pays the issuer address on-chain. Delivery on that path follows the ledger confirmation.

On a facilitator resource, the caller stays on the issuer https URL. If the issuer never settles, the caller is not charged. After tesSUCCESS there is no refund. The caller depends on the issuer to settle after a successful handler, and on Sluzen being available for that settle, unless they check the payment on-chain with verifyBuyerPayment in @sluzen/sdk (or an explorer).

Compare trust by mode →

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.

How Sluzen works →

Do I paste a wallet seed?

No. Never paste a seed into sluzen.network. You only set the address that receives payment. Callers sign the XRP payment in their own software, on their own machine. Their seed never comes to this site.

Settled in XRP: What does that mean?

XRP drops are the default request-price unit and the only prepaid unit for the 0.8% take. XRP Ledger is the primary rail. Opt-in product Amounts also include allowlisted RLUSD on XRPL and canonical USDC on Base; those still debit take from XRP prepaid credits.

Is this Testnet?

The paid-call count on Live comes from the proxy’s public live feed. That feed states which XRP Ledger network the proxy is connected to: testnet, mainnet, or unknown. This site does not hardcode one of those words. The 0.8% share is charged only when the proxy is on mainnet. On testnet, and when the network is unknown, that share is not charged.

See the count →

What if my API already returns 402?

Register that https URL to store the price. The Sluzen 402 comes from the snippet you paste on that server. Your server asks Sluzen to verify the signed payment, runs the handler, and asks Sluzen to settle only if the handler succeeded. Return the body only after settle. If you skip settle, the caller is not charged. The caller depends on you to settle after success, and on Sluzen being available for that settle, unless they verify the payment on-chain. After the ledger confirms, there is no refund. If the handler already changed state and the submit then fails, that work stays unpaid.

Who the caller trusts →

A route that still sits on Sluzen can opt in to the same idea: Sluzen calls your API before it submits. The signed payment stays on Sluzen. A failed response is not charged. If your API already changed state and the submit then fails, that work stays unpaid. The default route still waits for the ledger before it calls you.

How do I see paid calls?

Settled-call count and the full feed are on Live. Both use the same public totals from the proxy.

Can I try Sluzen without an issuer key?

Yes for the public demo. Call the investor-demo path on the API host and expect HTTP 402 with the payment headers. OpenAPI is on this site. Proof shows one allowlisted settlement hash. Live shows aggregate counts. There is no signup form.

Developers →

OpenAPI →

Proof →

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.

How Sluzen works →