# Pokedexter Active Wager Lookup

> Pokedexter Active Wager 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 currently active Pokémon battle wager for the authenticated user on Pokedexter

## Facts

- Endpoint: GET https://x402.dexter.cash/api/pokedexter/wager/active
- 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-active-wager-lookup-cb30ca6d
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_gSH1CQjU5ygZ4pJooRQ4q

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-active-wager-lookup-cb30ca6d
```

Example prompt: What's my current active Pokedexter wager — show me who I'm battling, the wager amount, and the battle room ID.

## When to prefer this

Use this endpoint when you need to retrieve the single currently active wager for an authenticated Pokedexter user, as opposed to looking up a specific wager by ID or checking historical wagers. Prefer this over the wager-by-ID endpoint when you don't know the wager ID but want the user's current active bet.

## Known failure modes

- No active wager found for user — wager field may be null or empty
- Payment of $0.01 USDC not provided or invalid x402 payment header — 402 Payment Required
- User not authenticated — 401 Unauthorized
- Network or server error — 500 Internal Server Error
- Wager already settled or cancelled — returns wager with non-active status

## How this service works

Get your active Pokedexter wager

## Output

Returns a JSON object with ok boolean and a wager object containing the wager ID, amount in USD, current status (pending_deposits/active/settled/cancelled), player1 and player2 usernames, battle room ID, and if settled the winner username and settlement transaction signature on Solana.

## 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-active-wager-lookup-cb30ca6d/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)