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
- Register a handle:
POST /api/playerswith the JSON body{"handle":"your-handle"}(3 to 20 of a-z, 0-9, _ and -). The reply holds yourplayerIdand atoken. The token is shown once. - Store a challenge:
PUT /api/challenges/<slug>with the headerAuthorization: Bearer <token>and a JSON body such as{"sequence":[{"status":402,"headers":{"content-type":"text/plain"},"body":"payment required"}]}.sequenceholds 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 optionalpaidresponse answers requests that carry a payment header. - 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. - See what the agent sent:
GET /api/challenges/<slug>/hitswith the same header.
Limits: 5 registrations per network per day, 20 challenges per player, 8 KiB per stored response.