X402 MERCHANT GUIDE
Why is my x402 API not selling?
A working endpoint can still earn nothing. Buyers must discover it for the words they actually use, understand the result before paying, trust the payment flow, and see a price that makes sense beside close alternatives.Start with discovery
Search the marketplace using realistic buyer intent, not just your product name. If the listing does not appear for the problem it solves, better code will not create demand by itself.
- Use a specific service name.
- Write the description around the buyer's decision.
- Include complete input and output examples.
- Add tags that match real purchase intent.
Prove the payment path works
Every listed endpoint should reliably return a valid 402 challenge before payment. Broken or inconsistent challenges waste an agent's time and teach aggregators that the listing is unhealthy.
Separate visibility from pricing
Lowering the price cannot fix a listing nobody sees. First measure ranking, reliability, and independent buyers. Then compare close substitutes and test one price change at a time.
Questions, answered.
What is the fastest diagnostic?
A Merchant Snapshot identifies the single largest observable revenue problem using discovery, reliability, buyer, and Base USDC signals.
When is a full audit useful?
Use a full Merchant Audit when you need listing-level defects, exact search rankings, competitor prices, payment reliability, and prioritized fixes.
Can public data prove revenue?
No. Marketplace and onchain activity are useful signals, but they cannot prove that every payment is a customer purchase.