---
type: Article
name: "Theatres and attractions: showtimes, casts and who a show is for."
id: "https://selfe.ai/insights/hospitality-and-bookings/theatres-and-attractions-showtimes-casts-and-who-a-show-is-for"
url: "https://selfe.ai/insights/hospitality-and-bookings/theatres-and-attractions-showtimes-casts-and-who-a-show-is-for"
publisher: "did:web:selfe.ai"
description: "A theatre's listing for a touring show can be accurate on Monday and wrong by Thursday, and an AI agent booking a specific performance needs to know which facts are stable and which change performance to performance."
datePublished: "2026-09-15T07:26:20.857Z"
author: The Selfe team
---

# Theatres and attractions: showtimes, casts and who a show is for.

> A theatre's listing for a touring show can be accurate on Monday and wrong by Thursday, and an AI agent booking a specific performance needs to know which facts are stable and which change performance to performance.

## In short

- Some show facts, age guidance, running time, hold for an entire run. Others, especially cast, are only true for one specific performance.
- An agent needs to check stable facts once and performance-specific facts against the exact date being booked, not the show in general.
- Being honest about what's confirmed for the whole run versus what can only be confirmed closer to a date gives an agent something real to act on.

A theatre listing reads like one fact-sheet covering the whole run, but only part of it holds that way. The rest changes performance to performance, and a family booking around a specific date needs to know which is which.

## Some facts hold for the whole run

A show's age guidance is stable for the whole run. Which actor plays the lead on a specific Thursday matinee is not, understudies and cast changes happen without warning, and a family booking specifically to see one performer needs to know that before they book, not after the curtain call.

Imagine a regional theatre running a touring production for three weeks. This site's own pillar on booking requests draws a line between a stable fact and one that needs a live check, and a theatre is where that line matters most: an AI agent booking tickets for a specific Thursday matinee is handling two very different kinds of fact at once, what's true for the whole run, and what's only true for that one performance.

Age guidance, running time, whether there's an interval, content warnings, these are set for the production as a whole and don't change performance to performance. A family checking whether a show suits an eight-year-old is asking a question with one stable answer for the entire three-week run, and a theatre that states this clearly once has answered it for every performance an agent might check.

Accessible seating belongs in this same stable category, and gets treated as an afterthought more often than age guidance does. Whether a venue has step-free access to a specific seating block, or a fixed number of wheelchair spaces that need booking directly rather than through the general seat map, is true for the whole run, not one performance, and an agent checking on behalf of a guest who needs it should find that answer as reliably as the running time.

## Some facts are true for one performance only

Which cast members are on for a specific date is not stable in the same way. Touring productions frequently run with understudies, or a rotating cast, and a family booking specifically because a particular actor is playing the lead needs that confirmed for their exact date, not for the run in general. A theatre's listing that states the cast once, for the whole run, is stating something that might already be wrong for a specific Thursday.

## What an agent needs to ask, and when

For the stable facts, age guidance, running time, an agent can check once and treat the answer as good for any date in the run. For the performance-specific facts, cast, any last-minute schedule change, it needs to check against the exact date being booked, not the general show description. Mixing the two up produces a confident answer that's right for the wrong reason, accurate about the show in general, wrong about Thursday specifically.

## Why this matters more for theatres than for most other bookings

A restaurant table doesn't usually change character night to night. A live performance genuinely can, through cast changes that are nobody's fault and impossible to predict weeks in advance. A theatre that's honest about what's confirmed for the whole run versus what can only be confirmed closer to a specific date gives an agent something real to work with, rather than a single confident answer that quietly might not hold.

Selfe keeps a theatre's real cast and schedule information updated as it's confirmed, so an AI agent checks it against one specific date rather than the whole run.

## How close to the performance can cast information be confirmed?

It varies by production, but many touring shows only confirm cast for a specific date in the days immediately before it.

## Should a theatre avoid naming lead cast members at all, to avoid disappointment?

Not necessarily, naming them with a clear note that cast can vary by performance is more useful than either overpromising or saying nothing.

## Act on this

- [Check whether an agent can buy from you](https://selfe.ai/agentic-commerce/buyability-check) — the free readiness scan.
- [Discover venues](https://selfe.ai/api/registry/discover) — `POST`, semantic browse across the registry.
- [Match a bookable answer](https://selfe.ai/api/registry/match) — `POST` with dates and party size.
- [Verify Selfe's identity](https://selfe.ai/.well-known/did.json) — `did:web:selfe.ai`.
- [Agent card](https://selfe.ai/.well-known/agent-card.json) — how to connect over A2A or MCP.

