Introducing x402-token-rail: a simple way for Solana x402 APIs to accept their own token as a payment rail, offer token-paid discounts, and unlock holder-only perks for agents.
The goal is simple: make a Solana token useful inside the x402 economy by giving agents a reason to pay with it and keep holding it.
We built this while adding x402 to Claw Hunter's agent-facing bounty intelligence APIs. If agents are paying for API calls, a project's token should be able to participate in that flow instead of sitting outside the product loop.
If x402 already opened up a whole new agentic customer base for our API, why can't x402 open up a whole new agentic holder base for our token?
Why token rails matter
@x402 makes it easy for agents to pay APIs per request. That unlocks a new surface for agent commerce: data, tools, inference, and other paid resources that agents can call directly.
Most of these flows should still center around USDC. It is clean, neutral, and easy to price around. But neutral settlement does not give agents a reason to touch a project's own token. That is the gap x402-token-rail is meant to fill — not by replacing USDC, but by adding a second rail beside it.
For agent-facing APIs, this is especially interesting because API usage is often repeated. An agent may call the same endpoint many times while researching, ranking, creating, trading, submitting, or executing. If a token lowers the cost of those repeated calls or improves the quality of the response, the utility becomes much more concrete.
Agents do not care about token utility in the abstract. They care about whether something improves their cost, access, or output quality. That is where token rails become useful.
The first implementation: Claw Hunter
We built this because we needed it ourselves.
Claw Hunter is building bounty intelligence and execution tools for agents. Agents can pay supported endpoints in $CLAWHUNTER for 10% off, while agents holding more than 100,000 $CLAWHUNTER can unlock better access, including smarter models and richer bounty intelligence data.
Under the hood, we use @PayAINetwork as our facilitator, @x402scan for agent discovery, and UsePod for inference. Those pieces helped shape how we think about x402 APIs: payments, discovery, cost structure, and token incentives all need to work together if agents are going to use these endpoints repeatedly.
Turning agent customers into token holders
This pattern is not specific to Claw Hunter. Any Solana project with an x402 API can add its token as a second rail beside USDC.
The main opportunity is that x402 turns agents into repeat API customers. If an agent is calling your endpoint over and over, it can start making economic decisions around that endpoint: which rail is cheaper, which asset improves access, and whether holding the token leads to better responses.
That is where token rails matter. They let the same agent that already pays your API with USDC discover a reason to pay with your token instead, or keep holding it because the endpoint gives them more when they do.
Easy to add to existing x402 APIs
x402-token-rail is not meant to be a heavy framework. It is a small, reusable starting point for projects that already have paid Solana x402 endpoints.
The repo includes the core token-rail primitives, a reference implementation, and an agent-facing SKILL.md that can help wire the pattern into an existing x402 API codebase. It also includes discovery guidance for docs, llms.txt, and openapi.json, because a token rail only creates demand if agents can discover it.
Agents need to know what token is accepted, what discount exists, what holder threshold unlocks perks, and what changes when they qualify.
A shared list of token-enabled x402 APIs
We created a list of x402 APIs that accept project tokens as payment, starting with Claw Hunter. If your project implements a token rail, open a PR and add it to the list.
We want the repo to become a simple map of Solana x402 APIs where project tokens are actually usable by agents.
x402 gives agents a way to pay. Token rails give agents a reason to use and hold project tokens.
x402-token-rail is open source here:
https://github.com/clawhunter/x402-token-rail