# Ticketmaster Attraction Details by ID

> Ticketmaster Attraction Details by ID is a paid API for AI agents from stabletickets.dev, paid per call via x402, $0.01/call, status unknown (last checked 2026-09-14).

Fetches full details for a specific Ticketmaster attraction (artist, team, or performer) given its attraction ID

## Facts

- Endpoint: POST https://stabletickets.dev/api/attractions/details
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/stabletickets-dev-479a33d3
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap__JKZ9quWPnztdC37F0KLs

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 stabletickets-dev-479a33d3 -d '<json body>'
```

Example prompt: Can you pull up the full Ticketmaster attraction profile for attraction ID K8vZ917G7f0 — I want their genre, classification, images, and any social links they have listed?

## When to prefer this

Use this endpoint when you already have a Ticketmaster attraction ID and need full details — name, classification, images, and social links. Prefer this over the search endpoint when the ID is known. Use the search endpoint first to discover the ID if you only have a name or keyword.

## Known failure modes

- Invalid or non-existent attraction ID returns a 404 or error response
- Malformed request body returns a 400 bad request
- Network timeout or Ticketmaster API downtime returns a 5xx error
- Payment failure (x402) if USDC balance is insufficient

## How this service works

Get Ticketmaster attraction details by attraction ID

## Output

Returns detailed attraction data from Ticketmaster including the attraction's name, type, classifications (segment, genre, subgenre), images in various sizes, external links (homepage, social media), and upcoming events count.

## Example request

```json
{
 "id": "K8vZ917G7f0",
 "domain": "ticketmaster.com",
 "locale": "*"
}
```

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "id": {
   "type": "string",
   "minLength": 1,
   "description": "Ticketmaster entity ID"
  },
  "domain": {
   "anyOf": [
    {
     "type": "string"
    },
    {
     "type": "array",
     "items": {
      "type": "string"
     }
    }
   ],
   "description": "Single value, comma-separated values, or string array"
  },
  "locale": {
   "type": "string",
   "default": "*"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/stabletickets-dev-479a33d3/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from stabletickets.dev](https://www.zero.xyz/host/stabletickets.dev/llms.txt)