> For the complete documentation index, see [llms.txt](https://parad0xlabs.gitbook.io/parad0xlabs-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://parad0xlabs.gitbook.io/parad0xlabs-docs/dna-x402-payment-rail/make-money.md).
# Monetize
***
## 1. Sell API Access Per Call
If you have any skill, model, data feed, or service: wrap it with x402 middleware. Set your price per call — anywhere from $0.0001 to $100, you decide. Anyone can call it and pay in USDC (a dollar-pegged digital currency) directly to your Solana wallet.
No Stripe account. No monthly invoicing. No chargebacks. Payment arrives before your server does any work.
**Exactly how it works:**
1. You write the service (trading signals, a data scraper, an AI model, anything).
2. You add x402 middleware — roughly 10 lines of code.
3. You set a price. Example: $0.01 per call.
4. You publish the URL.
5. Someone calls your URL, their client sends $0.01 in USDC, your server checks the payment, responds with the data.
6. Money is in your wallet. Done.
**Real examples and math:**
* Trading signals at $0.01/call — 10,000 calls/day = $100/day = $3,000/month
* Weather data at $0.001/call — 1M calls/day = $1,000/day
* AI image generation at $0.05/call — 500 calls/day = $25/day
* Legal document analysis at $1/call — 100 calls/day = $100/day
You set the price. You own the wallet. No middleman takes a cut of your revenue.
***
## 2. Run an x402 Facilitator
Facilitators sit between the person paying and the server receiving payment. Their job is to verify that a payment receipt is real before the server does any work.
Facilitators charge a basis-point fee — meaning a fraction of a percent — per transaction. At volume, this adds up fast.
**Exactly how it works:**
1. You run a facilitator node (an always-on server that checks payment receipts).
2. API providers register with your facilitator to use your verification service.
3. Every time a payment flows through your facilitator, you collect a small fee.
4. You never touch the product being sold. You just verify the money.
**The math:**
* 0.1% fee on $50,000/month in volume through your facilitator = $50/month
* 0.1% fee on $5M/month = $5,000/month
* The x402 network already processes \~$50M in total volume. You are tapping into existing flow.
This is the same business model as Visa or Stripe — but permissionless. No one needs to approve you. You just run the node.
***
## 3. Build x402-Gated Products
Subscription paywalls have friction: sign up, enter credit card, commit to a monthly fee. Most people leave. Micropayment paywalls remove all of that. Pay per piece. No commitment.
**Exactly how it works:**
1. You build content or a tool — articles, answers, reports, analysis.
2. You gate it with x402. Set a price per access. Example: $0.001 per article.
3. Reader clicks your link. Their wallet pays $0.001 automatically.
4. They read the article. You get paid.
No login required. No subscription form. No abandoned carts. The payment happens in the same moment as the request.
**Real examples and math:**
* News site at $0.001/article — 100,000 reads/day = $100/day = $3,000/month
* AI Q\&A at $0.01/answer — 10,000 questions/day = $100/day
* Financial data at $0.05/report — 1,000 reports/day = $50/day
Readers only pay for what they actually consume. That removes the biggest reason people avoid paywalls.
***
## 4. Agent-to-Agent Revenue
This is the new part. AI agents (automated software that makes decisions and takes actions) can pay each other for services — no human involved in the transaction.
You build an agent that does something useful: summarizes documents, checks prices, translates text, generates code. Other agents discover your agent, call it, and pay via x402. Your agent earns money while you sleep.
**Exactly how it works:**
1. You build an AI agent that provides a service.
2. You wrap it with x402. Set a price per call.
3. Other AI agents — running on other people's infrastructure, for other businesses — discover your agent and pay it automatically when they need the service.
4. USDC accumulates in your wallet. No human on either side needs to initiate anything.
**Why this matters:**
The agent calls your service, pays $0.01, gets the result, continues its task. Happens thousands of times per day. You never see it. You just check your wallet balance.
This is not theoretical. The x402 network has processed \~165 million transactions. Automated systems are already paying automated systems at scale.
***
## The Numbers
x402 live network stats at time of writing:
* \~165 million transactions processed
* \~$50 million total volume
* Solana handles 70% of monthly volume (Solana is a fast, low-fee blockchain — transaction costs are fractions of a cent, which is why micropayments work here and not elsewhere)
The infrastructure is already built and handling real scale. You are not betting on something that might work. You are plugging a service into a payment network that is already running.
***
## Where to Start
If you have one hour:
1. Pick the simplest service you can build — even just wrapping an existing API you already use.
2. Set up a Solana wallet (Phantom or Backpack — free, takes 5 minutes).
3. Add x402 middleware to your server.
4. Deploy it.
5. Set your price. Publish the URL.
You do not need permission. You do not need a bank account or a business entity. You need a laptop, a service idea, and a wallet address.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://parad0xlabs.gitbook.io/parad0xlabs-docs/dna-x402-payment-rail/make-money.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.