API owners
You have a working endpoint and want to charge per request without adding accounts, subscriptions, checkout, or billing code.
Paid API links for existing endpoints
Sell access to an API you already run.
Stent adds a per-request USDC paywall in front of your HTTPS endpoint. Paste the URL, set a price, verify ownership, and share one paid link.
Who it is for
Use Stent when the API already exists and the missing piece is payment.
Agent and app builders
You need a paid API URL that an agent loop or app can call with a spend cap and a predictable request path.
Not a fit
Stent does not host your API, change your payment model, or introduce smart contracts. It is the paid access layer in front of what you already run.
First success
The product is built around one activation path.
Every screen moves a new publisher toward a verified paid URL and the first paid request. Documentation is available, but it is not required to finish.
Point Stent at your HTTPS endpoint
Use the API you already run. Stent becomes the paid public URL in front of it.
Set the price per successful request
Start with a small USDC price and change your product before you change your server.
Prove you control the API
Add one verification file or response header. Stent checks it automatically.
Run the first paid request
The success screen gives the paywall check and buyer request code in the product.
What stays true
Your server stays unchanged.
Stent reuses the existing proxy, verification, marketplace, sample response, and SDK surfaces. V2 changes the product journey, not the backend architecture.