Home / API docs / Pulse API
More

Pulse API

GET /api/pulse free per call USDC on Base · x402

Public traffic pulse for this API, straight from the payment log: daily paid-call activity as a 0-100 index (busiest day in the window = 100), most-called endpoints as a share of paid calls, and an hour-coarsened recent-activity ticker. Shape, not scale — no revenue figures, no raw counts, no payer identities. Free; human view at https://x402.webbersites.com/pulse.html.

Example request

curl "https://api.webbersites.com/api/pulse"
# first call returns 402 + payment requirements; an x402 client pays and retries automatically

Example response

{
    "endpoints": 69,
    "daily_activity": [
        {
            "date": "2026-07-18",
            "index": 62
        }
    ],
    "board_activity": [
        {
            "date": "2026-07-18",
            "index": 41
        }
    ],
    "top_endpoints": [
        {
            "endpoint": "GET /api/uptime",
            "share_pct": 34.2
        }
    ],
    "recent": [
        {
            "t": "2026-07-19T04:00Z",
            "endpoint": "POST /api/calc/stats",
            "rail": "x402"
        }
    ]
}
MCP tool: get_pulse — via npx -y webbersites-x402-mcp (local, key stays on your machine) or the remote endpoint https://api.webbersites.com/mcp.

How payment works

There is no signup and no API key. Call the endpoint; it replies 402 Payment Required with machine-readable payment requirements. Your client signs a USDC transfer authorization (EIP-3009, gasless) and retries with the X-PAYMENT header — @x402/fetch does this automatically. See the overview for a working snippet.