Skip to main content

Dashboard

Manage your endpoints at bankr.bot/x402.

Overview​

The dashboard shows:

  • Summary stats — active endpoints, total requests, revenue, average revenue per request
  • Revenue chart — daily revenue over time with per-service stacked areas and a toggleable legend, plus 7D/30D/90D/1Y/All timeframe selector
  • Endpoint cards — each endpoint with status, metrics, pricing, and pause/resume controls
  • Request logs — live feed of every request with console output and error details
  • Environment variables — add and remove encrypted secrets
Unauthenticated Landing Page

The /x402 route serves as a public landing page when not logged in, introducing x402 Cloud and prompting users to sign in.

The top-right corner includes a profile dropdown showing your connected wallet address and a logout option.

Endpoint Management​

Click any endpoint card to open the detail slide-out panel:

View​

  • Endpoint URL (shareable)
  • Total requests and revenue
  • Revenue breakdown: last 7 days, 30 days, all time
  • Configuration: version, network, platform fee, pay-to address, last deployed

Edit​

Click Edit in the slide-out panel to modify:

  • Pay-to address — the wallet that receives your earnings
  • Price per request — in your chosen token
  • Payment token — USDC on Base
  • Description — shown to agents during discovery

Changes take effect immediately — no redeployment needed.

note

To update your handler code, use bankr x402 deploy from the CLI. Code changes require redeployment.

Pause / Resume​

Temporarily stop serving requests without deleting the endpoint. Paused endpoints return 404 to callers.

Delete​

Permanently removes the endpoint. Requires typing delete to confirm. This action cannot be undone.

Request Logs​

The logs panel shows a live feed of requests (polls every 10 seconds):

200  GET  /weather?city=London   145ms   2s ago
200  GET  /weather?city=NYC      89ms    15s ago
402  GET  /weather?city=Tokyo    12ms    1m ago    (no payment)
502  GET  /weather?city=Berlin   2100ms  3m ago    (handler error)
Log Filtering

Runtime noise is automatically filtered out. Only your console.log output is shown in the logs panel.

Click any row to expand:

  • Request details — status code, duration, settlement status, payment amount
  • Payer address — the wallet that paid for the request
  • Console output — everything your handler logged via console.log, displayed in a terminal-style panel
  • Error details — if the handler threw an error, the message and stack trace

Logs are retained for 90 days.

Using Console Output for Debugging​

Your handler's console.log statements appear in the logs panel:

export default async function handler(req: Request): Promise<Response> {
  const url = new URL(req.url);
  const city = url.searchParams.get("city");
  console.log("Request for city:", city);  // Shows in dashboard

  const data = await fetchWeather(city);
  console.log("API response:", JSON.stringify(data));  // Shows in dashboard

  return Response.json(data);
}
caution

Do not log sensitive information (API keys, passwords, user data) via console.log. Console output is stored in the request log and visible in the dashboard.

Environment Variables​

The env vars section at the bottom of the dashboard shows variable names only — values are never displayed.

  • Add — click "+ Add", enter a key and value. The value is sent over HTTPS and encrypted immediately.
  • Remove — click "Remove" next to any variable. This takes effect on the next cold start of your handler.