# Fanfare WNBA Teams

> Fanfare WNBA Teams is a paid API for AI agents from fanfare.run, paid per call via x402, $0.001/call, status unknown (last checked 2026-09-15).

Returns all WNBA teams with their IDs, city names, abbreviations, and conference assignments for use in downstream schedule and standings queries.

## Facts

- Endpoint: GET https://fanfare.run/wnba/teams
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/fanfare-run-03f14d23
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_nFlDOQJwF5RmbAQYVV5UE

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 fanfare-run-03f14d23
```

Example prompt: Can you give me the full list of all WNBA teams — I need their IDs, cities, abbreviations, and which conference they're in so I can look up schedules.

## When to prefer this

Use this endpoint first when building any WNBA-related workflow that requires team IDs or abbreviations — it is the authoritative reference list for the Fanfare WNBA data ecosystem and must be called before querying schedules or standings by team.

## Known failure modes

- No input required so failures are rare; service unavailability returns a non-200 HTTP error
- Payment not settled (x402 protocol failure) results in a 402 response and no data
- Stale or incomplete team data if roster changes mid-season are not yet reflected

## How this service works

All WNBA teams with ID, city, abbreviation, and conference. Use team IDs to query schedules and standings.

## Output

A list of all WNBA teams, each with a unique team ID, city name, team abbreviation, and conference designation (e.g. Eastern or Western). The team IDs can be passed to Fanfare's WNBA schedule and standings endpoints.

## Example request

```json
{
 "input": {
  "type": "http",
  "method": "GET",
  "queryParams": {}
 }
}
```

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "method"
   ],
   "properties": {
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "GET",
      "HEAD",
      "DELETE"
     ],
     "type": "string"
    },
    "queryParams": {
     "type": "object",
     "properties": {}
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object"
    }
   }
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/fanfare-run-03f14d23/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from fanfare.run](https://www.zero.xyz/host/fanfare.run/llms.txt)