Pay-per-call API to mint $SerWTF meme tokens on Base via x402 micropayments
What it does
x402.ser-api.wtf is an x402-enabled API that lets callers mint $SerWTF tokens by paying USDC on the Base network. The service exposes four POST endpoints: the root endpoint (which itself is paywalled), a `/mint` endpoint for minting $SerWTF tokens (100 tokens per call), a `/mint-1000` endpoint described as a "Premium Cope & Hopium Service" (presumably minting 1,000 tokens), and a `/data` endpoint providing "NGMI Analytics." Payment is handled via the x402 protocol using USDC (contract 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913) on Base, with a max amount of 1,000,000 units (1 USDC at 6 decimals) for the root endpoint.
The API is built with FastAPI (OpenAPI 3.1.0) and self-describes as "The first BSC-backed API that rewards poor financial decisions built by AI." Documentation is available at the `/docs` Swagger UI endpoint. Response schemas are largely empty in the OpenAPI spec, though the x402 challenge's outputSchema indicates responses return a JSON object with `message` (string) and `data` (object) fields. No request body fields are documented for any endpoint. The project appears to be a meme/novelty token minting service rather than a serious financial product.
Capabilities
Use cases
- —Mint $SerWTF meme tokens programmatically via a single API call
- —Access NGMI analytics data through the /data endpoint
- —Demonstrate x402 micropayment-gated API consumption on Base
Fit
Best for
- —Developers experimenting with x402 payment protocol on Base
- —Meme token enthusiasts wanting programmatic minting
- —Agents exploring pay-per-call crypto token APIs
Not for
- —Serious DeFi or financial applications
- —Users seeking well-documented, production-grade token APIs
- —Anyone needing non-USDC or non-Base payment options
Quick start
curl -X POST https://x402.ser-api.wtf/mint \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402-payment-header>"Example
Request
{
"url": "https://x402.ser-api.wtf/mint",
"body": {},
"method": "POST",
"headers": {
"X-PAYMENT": "<x402-payment-token>",
"Content-Type": "application/json"
}
}Response
{
"data": {},
"message": "Successfully minted 100 $SerWTF tokens"
}Endpoint
Quality
The endpoint is live and returns a valid 402 challenge with an outputSchema, and an OpenAPI spec is available. However, response schemas in the OpenAPI spec are empty, request bodies are undocumented, there are no usage examples, pricing details beyond the root endpoint's maxAmountRequired are absent, and the project is clearly a novelty/meme service with minimal documentation. The example response is inferred, not sourced.
Warnings
- —Response schemas in OpenAPI spec are empty for all endpoints
- —No request body documentation for any endpoint
- —Pricing (maxAmountRequired) is only confirmed for the root endpoint; other endpoints may differ
- —This is a meme/novelty token project — not a serious financial service
- —The API self-description references 'BSC-backed' but the x402 challenge specifies the Base network, which is a discrepancy
- —Example response JSON is inferred from outputSchema, not from an actual observed response
Citations
- —The root endpoint returns a 402 challenge requesting USDC on Base with maxAmountRequired of 1000000https://x402.ser-api.wtf/
- —The API exposes four POST endpoints: /, /mint, /data, /mint-1000https://x402.ser-api.wtf/docs
- —OpenAPI version is 3.1.0 and the API describes itself as 'The first BSC-backed API that rewards poor financial decisions built by AI'https://x402.ser-api.wtf/openapi.json
- —Payment asset is USDC at contract 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Base networkhttps://x402.ser-api.wtf/
- —The outputSchema indicates responses contain message (string) and data (object) fieldshttps://x402.ser-api.wtf/