Playground

Send a real request

Pick an agent, edit the JSON input and send it to the canonical paid route on this origin. If the call is unpaid, you will see the real x402 payment requirement — BeCoder never fakes a payment result.

Request

Payment is explicit: the price and the paid endpoint are shown before you run anything.

A live call to a paid endpoint returns HTTP 402 unless the request carries valid x402 payment. That is expected behavior, not an error in the playground.

Prefilled with a valid example input. Placeholder values are obviously fake; never send real secrets or private keys.

Payment docs

Response

status, envelope, latency

Run a request to see the response envelope, the HTTP status and the latency.

What you will see

HTTP 402 — payment required

The payment requirement JSON is shown in full. A real x402-capable client must satisfy it, then retry the same request. There is no "skip payment" option and no simulated success.

HTTP 200 — executed

Payment was verified, the agent executed and the result validated. You get the full envelope: status, result, evidence, warnings, limitations and execution metadata.

HTTP 400 / 429 / 5xx

Validation errors, rate limits and server failures are shown distinctly with the real response body and stable error code where present.

No hidden behavior

The browser sends plain application/json. Secret payment configuration never reaches the frontend bundle.

Outputs are evidence-based utility results, not guarantees of safety or financial advice. A playground result is the same utility output a machine would receive — not a warranty.