# Pokedexter Wager Status Lookup

> Pokedexter Wager Status Lookup is a paid API for AI agents from x402.dexter.cash, paid per call via x402, $0.01/call, status unknown (last checked 2026-09-15).

Retrieves the current status and details of a specific Pokedexter wagered Pokémon battle by wager ID

## Facts

- Endpoint: GET https://x402.dexter.cash/api/pokedexter/wager/:wagerId
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/pokedexter-wager-status-lookup-5c6246af
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_-mQTviip9sDChIgORY8ks

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability pokedexter-wager-status-lookup-5c6246af
```

Example prompt: What's the current status of my Pokedexter wager with ID abc123xyz — has it been settled yet, and if so who won?

## When to prefer this

Use this endpoint when you need to check the real-time or final status of a specific Pokedexter wagered Pokémon battle and already have the wager ID. Prefer this over the 'get active wager' endpoint when querying historical, settled, or cancelled wagers rather than only currently active ones.

## Known failure modes

- Invalid or nonexistent wager ID returns an error or ok:false
- Payment of $0.01 USDC not provided results in HTTP 402 payment required
- Wager still in pending_deposits state may show null winnerId and settlementTx
- Network or server error returns a non-200 response

## How this service works

Get Pokedexter wager status by ID

## Output

Returns an object containing the wager's unique ID, the USD wager amount, status (pending_deposits, active, settled, or cancelled), the usernames of both players, the battle room ID, and if settled, the winner's username and the Solana settlement transaction signature.

## Response schema (JSON Schema)

```json
{
 "ok": {
  "type": "boolean"
 },
 "wager": {
  "type": "object",
  "properties": {
   "id": {
    "type": "string",
    "description": "Wager ID."
   },
   "amount": {
    "type": "number",
    "description": "Wager amount in USD."
   },
   "status": {
    "type": "string",
    "description": "Status: pending_deposits, active, settled, cancelled."
   },
   "winnerId": {
    "type": "string",
    "description": "Winner username (if settled)."
   },
   "player1Id": {
    "type": "string",
    "description": "Player 1 username."
   },
   "player2Id": {
    "type": "string",
    "description": "Player 2 username."
   },
   "battleRoomId": {
    "type": "string",
    "description": "Battle room ID."
   },
   "settlementTx": {
    "type": "string",
    "description": "Settlement transaction signature (if settled)."
   }
  },
  "description": "Wager details."
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/pokedexter-wager-status-lookup-5c6246af/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from x402.dexter.cash](https://www.zero.xyz/host/x402.dexter.cash/llms.txt)