Pay-per-call NGMI analytics endpoint on Base via x402 micropayments
What it does
The /data endpoint on x402.ser-api.wtf returns "NGMI Analytics" data when called via HTTP POST with an x402 payment header. It is part of the $SerWTF API, a small novelty API that gates every route behind x402 micropayments on the Base network using USDC.
The endpoint accepts a POST request with no required body fields and returns a JSON object containing a "message" string. Payment is required via the X-PAYMENT header using the x402 "exact" scheme on Base mainnet, with a max cost of 5,000,000 units of USDC (0x8335…2913), which corresponds to 5 USDC given USDC's 6 decimal places. The payment timeout is 300 seconds.
Documentation is minimal — the OpenAPI spec lists four endpoints (/, /mint, /data, /mint-1000) all gated behind x402 challenges, but none include request or response schemas beyond an empty object. The API self-describes as "the first BSC-backed API that rewards poor financial decisions built by AI." There is no detailed documentation, no usage examples, and no information about what the returned analytics data actually contains. Prospective callers should be aware that the actual utility and data quality of the response are unknown.
Capabilities
Use cases
- —Fetching novelty NGMI analytics data via micropayment
- —Experimenting with x402 payment-gated API calls on Base
- —Integrating pay-per-call crypto data into agent workflows
Fit
Best for
- —Developers exploring x402 micropayment protocol integrations
- —Agents that can pay USDC on Base for per-call data access
- —Novelty or experimental crypto analytics consumption
Not for
- —Production analytics requiring documented, reliable data schemas
- —Users who need free or subscription-based API access
- —Anyone expecting detailed or institutional-grade financial data
Quick start
curl -X POST https://x402.ser-api.wtf/data \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402-payment-token>"Example
Request
{
"url": "https://x402.ser-api.wtf/data",
"body": {},
"method": "POST",
"headers": {
"X-PAYMENT": "<x402-payment-token>",
"Content-Type": "application/json"
}
}Response
{
"message": "<NGMI analytics data string>"
}Endpoint
Quality
The endpoint is live and returns a valid x402 challenge, but documentation is extremely sparse. There are no request or response schema details, no examples of actual returned data, and the API's self-description is tongue-in-cheek with no serious documentation. The output schema only specifies a single 'message' string field. The actual content and utility of the analytics data is unknown.
Warnings
- —No response examples or detailed schema available — actual data content is unknown
- —API self-describes as rewarding 'poor financial decisions' — treat as novelty/experimental
- —5 USDC per call is relatively expensive for an undocumented endpoint
- —No pricing page, README, or supplementary documentation exists
- —Output schema is minimal: only a single 'message' string field is documented
Citations
- —The /data endpoint returns a 402 challenge requiring USDC payment on Base with maxAmountRequired of 5000000https://x402.ser-api.wtf/data
- —The API describes itself as 'The first BSC-backed API that rewards poor financial decisions built by AI'https://x402.ser-api.wtf/docs
- —The OpenAPI spec lists four POST endpoints: /, /mint, /data, /mint-1000https://x402.ser-api.wtf/openapi.json
- —The /data endpoint operation is described as 'NGMI Analytics'https://x402.ser-api.wtf/docs