x402-native API for Tempo payment data
PayMetrics is a wallet-based API and MCP gateway for Tempo payment data. The public production path is simple and explicit: discover payment terms, pay on-chain, verify once, then spend wallet credits on GraphQL and paid endpoints.
0.001 PathUSD increments and stay visible through /credits/{address} and X-Credits-Remaining.1. GET https://api.paymetrics.xyz/.well-known/x402
2. Send PathUSD or USDC.e on Tempo
3. POST https://api.paymetrics.xyz/verify-payment
4. GET https://api.paymetrics.xyz/credits/0xYourWallet
5. POST https://api.paymetrics.xyz/graphql
Headers:
X-Wallet: 0xYourWallet
Content-Type: application/json
Base top-up rate:
0.001 PathUSD = 1 credit
Paid response signal:
X-Credits-Remaining: 999
One product, one public onboarding story
PayMetrics is not positioned here as a generic SDK, a public API-key product, or a broad analytics demo. The public wedge is x402-native access to Tempo payment data with one verified activation flow.
Wallet-based access
Discover terms at /.well-known/x402, pay on Tempo, verify with /verify-payment, and spend credits with X-Wallet.
Tempo payment data
The primary public paid surface today is GraphQL on /graphql, backed by Tempo payment data and credit accounting.
MCP-compatible integration
MCP metadata lives at /mcp and the live tool catalog at /mcp/tools. Tool names and docs match the live gateway surface.
Discover -> pay -> verify -> query -> see credits
This is the public activation path repeated across the landing page, docs, OpenAPI, and MCP references. No extra branches, no hidden install step, and no unsupported package claims.
https://api.paymetrics.xyz/.well-known/x402 to get recipient, chain, accepted tokens, and pricing.
PathUSD or USDC.e on Tempo to 0x9B374df0806884aE8CaDE82422c5e244cA1cee4a. Base crediting is proportional: 0.001 PathUSD = 1 credit.
/verify-payment with the payment txHash. The gateway credits the paying wallet.
/credits/{address} to confirm active credits before the first paid call.
/graphql with X-Wallet. Successful paid responses expose remaining balance via X-Credits-Remaining.
curl -i https://api.paymetrics.xyz/graphql \
-X POST \
-H "Content-Type: application/json" \
-H "X-Wallet: 0xYourWallet" \
-d '{
"query": "query RecentTransfers { transfers(first: 3, orderBy: timestamp, orderDirection: desc) { id timestamp amount } }"
}'
HTTP/1.1 200 OK
X-Credits-Remaining: 999
Pricing and units match the live gateway
The public unit is credits. Base top-ups are proportional and credited in whole units with
floor rounding: 0.001 PathUSD = 1 credit. One paid GraphQL request costs one credit.
Qualifying top-ups of 10 PathUSD or more receive a 20% bonus.
1 PathUSD and 10 PathUSD tiers are reference examples on top of the same
proportional base rate.
Live MCP metadata and live tool names
The MCP section now mirrors the live server. No outdated tool names, no invented SDK wrapper, and no stale examples from older docs.
Metadata
GET https://api.paymetrics.xyz/mcp for server metadata and transport details.
Tool catalog
GET https://api.paymetrics.xyz/mcp/tools for the live tool list and compatibility aliases.
JSON-RPC endpoint
POST https://api.paymetrics.xyz/mcp with initialize, tools/list, and tools/call.
get_credit_score
get_fraud_risk
get_oracle_explain
get_oracle_verification_status
get_registry_code_status
get_history
get_leaderboard
ai_analyze
check_rate_limit