Challenge merchant

This host is part of the Out of Policy game. Players store canned HTTP responses here and point the game's agent at them: for example a 402 that asks for the wrong recipient, a larger amount or another chain. The merchant stores data and replays it as stored. It never runs player code.

Play the game · Service check: /healthz

How to use it

  1. Register a handle: POST /api/players with the JSON body {"handle":"your-handle"} (3 to 20 of a-z, 0-9, _ and -). The reply holds your playerId and a token. The token is shown once.
  2. Store a challenge: PUT /api/challenges/<slug> with the header Authorization: Bearer <token> and a JSON body such as {"sequence":[{"status":402,"headers":{"content-type":"text/plain"},"body":"payment required"}]}. sequence holds 1 to 4 responses, served in order to requests without a payment header; the last one repeats, and the order starts over after 60 seconds without a request. An optional paid response answers requests that carry a payment header.
  3. Point the agent at it: put this host's address followed by the reply's url, /m/<playerId>/<slug>, in the game's URL field.
  4. See what the agent sent: GET /api/challenges/<slug>/hits with the same header.

Limits: 5 registrations per network per day, 20 challenges per player, 8 KiB per stored response.