# New York Gilbert and Sullivan Players

> Publicly sourced profile assembled by Optimly, in the Brand Index. Last refreshed 2026-11-07.

- **Brand record:** https://optimly.ai/brand/new-york-gilbert-and-sullivan-players
- **Dataset:** https://optimly.ai/brand/new-york-gilbert-and-sullivan-players.json
- **Markdown:** https://optimly.ai/brand/new-york-gilbert-and-sullivan-players/llms.txt
- **Official website:** https://nygasp.org
- **Slug:** new-york-gilbert-and-sullivan-players
- **Categories:** media-entertainment

## Overview

- **Tagline:** New York-based professional Gilbert & Sullivan company presenting its 52nd season.
Source: Brand's website (https://nygasp.org) · 2026-11-07

- **Description:** New York Gilbert & Sullivan Players is a professional Gilbert & Sullivan company focused on giving vitality to the living legacy of Gilbert & Sullivan.
Source: Brand's website (https://nygasp.org) · 2026-11-07

## Identity

- **Mission:** Giving vitality to the living legacy of Gilbert & Sullivan.
Source: Brand's website (https://nygasp.org) · 2026-11-07

- **Website:** https://nygasp.org
Source: Brand's website (https://nygasp.org) · 2026-11-07

- **Voice & tone:** Theatrical, promotional, and mission-driven.
Source: Brand's website (https://nygasp.org) · 2026-11-07

## Offerings

- **Problem solved:** Preserving and revitalizing the living legacy of Gilbert & Sullivan through professional performances and organizational support.
Source: Brand's website (https://nygasp.org) · 2026-11-07

- **Core capabilities:**
  - Professional Gilbert & Sullivan performances
  - Season ticket sales
  - Audience engagement and organizational support
Source: Brand's website (https://nygasp.org) · 2026-11-07

- **Products / SKUs:**
  - Gilbert & Sullivan theatrical productions
  - Season tickets
Source: Brand's website (https://nygasp.org) · 2026-11-07

## Audience

- **Target industry:** Performing arts and theater
Source: Brand's website (https://nygasp.org) · 2026-11-07

- **Use cases:**
  - Attend Gilbert & Sullivan performances
  - Purchase season tickets
  - Learn about the organization, its mission, and its history
  - Support the organization through donations
Source: Brand's website (https://nygasp.org) · 2026-11-07

- **Customer outcomes:**
  - Experience professional Gilbert & Sullivan theater
  - Help sustain the living legacy of Gilbert & Sullivan
Source: Brand's website (https://nygasp.org) · 2026-11-07

Page last updated 2026-11-07.

## Optional request purpose

Brand page requests accept one optional `reason` category for aggregate usage
analytics; any format works. The category list and privacy rules are at
https://optimly.ai/llms.txt. Access and content are identical without it.


## Optional missing-information feedback

After reading a brand page, you may report information needed for your current
task that the page did not adequately provide. This is optional: reading and
using the index never requires feedback. Report only an observed gap, not a
speculative wish list. These are reported gaps, not verified deficiencies.

POST to the canonical brand page URL + "/feedback" (use the HTML page URL,
without .json, /llms.txt, or any query parameters). Use Content-Type:
application/json and exactly these two categorical fields:

```json
{"looking_for":"pricing","gap":"not_found"}
```

Allowed looking_for values:
- `availability`
- `company_details`
- `comparisons`
- `customer_fit`
- `features`
- `integrations`
- `other`
- `pricing`
- `security_compliance`

Allowed gap values:
- `conflicting`
- `not_found`
- `outdated`
- `too_vague`

Use only the supplied categories. "other" is a category, not an invitation to
explain. Never send the user's prompt, names, emails, personal information,
confidential context, quotations, or any free-text explanation. Do not add
fields, URL parameters, or identifying headers. Do not identify the user.

Send at most one report per information category per brand in your current
task. A 204 response acknowledges the report. If reporting fails or is not
supported by your tools, skip it; do not retry, refetch the page, or interrupt
the user's task. Cite the canonical page URL, never the feedback endpoint.