Build a data service. Get paid for every request.
If you can build an API, you can run it on Pocket Network. Publish it once, and AI agents, MCP clients, and apps can call it through any portal that lists it, while the network meters every request and pays you on-chain. You don’t need to build billing, keys, or customer accounts.
Any service that answers HTTP with data
Pocket serves HTTP request-and-response services of any kind, written in any language.
Data APIs and aggregators
Market data, public records, research indexes, and anything else you can serve as an API.
LLM inference and embeddings
Models behind an HTTP endpoint, priced per request.
Document and web tools
Extraction, conversion, search, and rendering services.
MCP servers
Tools that agents call directly, served across the network.
The Agentic Portal already lists services for finance, research, government data, security, compliance, health, and the web.
The one hard rule
Every response is a JSON object, including errors. If your service returns HTML, CSV, or anything else, wrap it in a string field. Gateways score responses by their first byte, so anything that doesn’t start with { or [ counts as a failed request.
Partly supported: WebSocket, gRPC, and streaming (SSE) services also run on Pocket, but they need extra setup. The docs cover it.
From idea to paid service
-
Build
Design your endpoints, write the service, and describe it in a service card: the metadata that tells agents and gateways what it does. Claude, with the Service Builder skill, can do most of this with you, from checking that your service ID isn’t taken to generating the card.
-
Test on Beta TestNet
Get free test POKT from the Beta faucet, register your service on Beta, bring it online, and send real requests through the network before anything costs real POKT.
-
Go live on MainNet
Register on MainNet, stake your supplier, and start serving. PSM4Win turns each step into a button.
-
Verify
Run the service audit. It checks your service against the Agentic Portal’s acceptance rules on the live network: the same checks the reviewers run.
-
Get listed and get paid
Submit your service to the portal. Once it’s listed, agents can find it, try it, and call it, and every request you serve is paid on-chain.
Pick your tools
PSM4Win
For Windows 10 or 11, with Docker Desktop
Writes your service card, registers the service, sets up your server as a supplier, stakes, and tests real requests. Every step is a button.
With Claude: turn on the Claude integration and Claude can drive the app with you. Every transaction or signature is confirmed in the app window first.
Claude + the Service Builder skill
For any OS where you work with Claude
Guides you through the whole workflow and generates what you need: the card, pricing, deployment files, and test and audit commands.
With Claude: Claude is the interface. Use the Pocket MCP server alongside it for live network data.
The skill and PSM4Win work together: many developers design and build with the skill, then deploy with PSM4Win.
Get paid twice: as the builder and as the operator
You set the price. You price your service in compute units per request (CUPR) when you register it. Compute units have a fixed dollar value on Pocket, $1 per billion, so your price stays stable in dollars even when POKT moves. For example, a service priced at 100,000 compute units per request is worth $0.0001 per request.
Every request is split on-chain. When a session’s requests are settled in the claim and proof cycle, the value is distributed by the network’s published rules:
| Role | Share of each settled request | Who it is |
|---|---|---|
| Supplier (operator) | 79% | Whoever runs the servers that answered the request |
| Service owner | 2.5% | Whoever registered the service, no matter who served the request |
| Network (block producers and the DAO) | 18.5% | Keeps the network running |
Build once, earn on every request. At launch you’re usually both owner and operator, so you earn both shares. As your service grows and other operators start serving it, you keep earning the owner’s share on every request they serve.
Portal prices are separate. Each portal sets its own price to agents. Your earnings come from the network at the compute-unit price you set, whichever portal the requests come through.
Shares are governance parameters, read from Pocket Network MainNet once a day. Last read: 27 Sep 2026.
Registering and staking
Deploying on MainNet means registering your service and staking a supplier to serve it. The tooling walks you through both, and you’ll test everything on Beta first.
| Current value | Notes | |
|---|---|---|
| Service registration fee | 1,000 POKT | One-time, per service. |
| Supplier stake (minimum) | 59,500 POKT | Bonded, not spent. You get it back after an unbonding period if you stop serving. |
| Test application stake (minimum) | 1,000 POKT | Used to send test requests to your own service. |
Values are read from Pocket Network MainNet once a day. Last read: 27 Sep 2026.
Need POKT?
What the Agentic Portal lists
Anyone can publish a service to Pocket Network. Each portal chooses which services it lists. The Pocket Network Foundation’s Agentic Portal lists services that:
Are new
Not substantially the same as a service already listed.
Aren't about Pocket itself
Pocket’s own blockchain data is already available at data.pocket.network.
Serve lawful content
Nothing intended to distribute internationally illegal content.
Pass the audit
Including at least one settled claim on MainNet.
Staying listed: services with no requests for more than 30 days may be delisted.
Growing a service
Most services launch with a single supplier: the builder, running it themselves. As demand grows, other operators can stake to serve your service too. That spreads the load, adds capacity, and keeps it available when any one server goes down. You can track your service, its suppliers, and its claims on the Pocket explorer.
Questions developers ask
Do I need to know blockchain development?
No. You build a normal HTTP service. The tooling handles the on-chain steps (registering, staking, and claims), and Claude can walk you through anything unfamiliar.
Do I earn if someone else runs my service?
Yes. The service owner, meaning whoever registered it, receives 2.5% of every settled request on that service, whichever supplier served it. Other operators serving your service increase your earnings.
Can someone else operate my service?
Yes. Any operator can stake to serve a registered service, and you earn the owner's share on the requests they serve. Most services start with their builder as the only operator.
Is the registration fee refundable?
No, it's a one-time fee per service. The supplier stake is different: it's bonded, not spent, and returned after unbonding.
How do agents find my service?
Through portals. Once listed on the Agentic Portal, your service appears in its catalogue and its MCP server, llms.txt, and OpenAPI index, and gets a service page with a "Try it" button.
What happens if my service goes down?
Requests fail over to other suppliers if there are any; with one supplier, calls fail until you're back. Unreliable services can fail portal checks, so plan to monitor your backend.
Where are the full technical docs?
At docs.pocket.network/services: overview, registration, and deployment. Services docs →
Ready to ship?
Start on Beta today. Your first service can be live on the network in an afternoon.