Turn any endpoint into a paid product.
Paste your API URL, set a tiny per-request price, and launch. We handle the x402 payment wall, settlement, public listing, and usage analytics.
Launch your next API.
Bring your endpoint. Make it a product.
Your wallet signature proves ownership. Publishing does not move funds.
Useful APIs.
Pay as you call.
Discover developer tools built for humans, apps, and autonomous agents. No subscriptions. No API-key checkout.
Choose an API.
Pay, run, done.
Call a live Olanas API directly from the website. You see the exact token, amount, and recipient before your wallet opens.
Install. Set limits. Ask.
Use Codex or Claude to discover an API, pay from your local Olanas wallet, and return the result in chat.
Release preview: the updated wallet package and durable-order backend must be published together before this workflow is ready for mainnet use.
- 01Install the local walletConnect Olanas Payments MCP to your desktop AI client.
- 02Fund & set limitsEnable a bounded session in your local wallet UI.
- 03Ask for an APIThe agent pays automatically only within your policy.
- 04Get the resultRead the response in chat and track the original order.
Setup instructions for Codex and Claude
1. Install on your computer
You need Node.js 22 or newer and Git. Run this in your terminal, not in agent chat. Install the selected desktop app or CLI first.
npx --yes github:olanass/web#olanas-payments-mcp install --client codex --auto-config --network mainnet --launchpad https://olanas.xyz
Have the Codex CLI available for automatic registration. If it is not found, the installer prints a manual MCP configuration.
The installer creates or reuses its own encrypted local wallet. It does not import your existing browser wallet, fund the account, or enable spending. Protect the local configuration and owner-password file.
2. Open, fund, authorize
Restart your AI client and ask: Use olanas-payments to show my wallet. Open the complete private wallet link it returns, including its #token. Do not share that link.
Use a dedicated wallet and verify the displayed mainnet network before funding it with the required payment token and ETH for gas. Enter the owner password only in the local wallet UI.
Choose a budget, duration, and Standard or Fast fees. Review the per-call and gas caps, optionally restrict services and recipients, then enable the session. Fast fees never change the API price and do not guarantee faster confirmation.
3. Ask your agent
This is an example request, not a promise that the service is available. Review it before sending. Each new purchase needs its own request ID; retries must keep the original.
Use olanas-payments to find Startup Pitch Scorer. Inspect its current input requirements and price. If it is available and within my enabled wallet policy, call it once using POST with {"name":"Olanas","pitch":"A marketplace where AI agents discover and pay APIs using crypto."}. Choose a unique requestId for this purchase and reuse it on retries. Check the same order until its saved result is available. If owner action is needed or delivery is uncertain, stop and tell me. Do not create a replacement payment.
4. Follow the original order
The agent uses request_paid_api and reads the result with get_payment_status. The wallet shows authorization, payment confirmation, and saved response separately. Confirmed payment does not guarantee a successful API response.
With an active local signing session, eligible payments need no per-payment wallet popup. Your AI client may still ask permission to use tools. Browser-wallet mode remains manual. Restarting the companion disables autonomous spending until you authorize a session again.
If something needs attention
- Tools missing: restart the desktop client; check its MCP settings and the installer output. This is a local stdio integration, not a generic web-chat connector.
- Wallet link does not open: ask for a fresh complete link. Do not start a second companion on the same port.
- Insufficient funds or expired session: inspect the local wallet. Ask the agent to retry the same request ID only after resolving it.
- Rejected or uncertain delivery: do not pay again. Review the original order and use owner recovery only when appropriate.
- Order API unavailable: stop; the website and installed companion may be on different releases.
Never paste a private key, seed phrase, or owner password into chat or this website. Installation and enabling spending are separate actions. Limits are enforced by the local companion, not by an on-chain spending contract.
Payments from this browser
No paid API calls from this browser yet.
WeatherAI
AI-ready weather data API
curl -i -X POST "https://example.com/x402/weather-ai"
const result = await agent.call("weather-ai", { body: { input: "hello" } });- ✓Direct settlementEvery payment goes to the creator wallet.
- ✓Replay protectedOne payment proof invokes one API request.
- ✓Public metricsUsage and revenue are transparently reported.
Sell files with a simple payment link.
Upload a file or paste private content, choose a price, and publish a wallet-signed x402 link. Buyers unlock the original content after payment.
Loading Content...
Fetching paywall metadata from Robinhood Chain...
My projects
Your launched APIs and paywalled files in one place.
| Service | Price | Requests | Revenue | Status | Actions |
|---|---|---|---|---|---|
| Connect your wallet to view API services. | |||||
| Title / Asset | Price | Views | Sales | Revenue | Created | Actions |
|---|---|---|---|---|---|---|
| Connect your wallet to view your paywalled links. | ||||||