Nritya (Dance)

Nritya (Dance) — connector documentation

• MCP endpoint: https://nritya.connectorbay.com/mcp
• REST API: POST https://nritya.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://nritya.connectorbay.com/openapi.json
• Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
• Authentication: none required. An optional Authorization: Bearer <key> raises rate limits.
• Health: https://nritya.connectorbay.com/health · Tool schemas: https://nritya.connectorbay.com/tools.json
• Publisher: Unify Dynamics LLC · connectorbay.com/nritya · agent@connectorbay.com

What Nritya (Dance) is for

The question that comes up whenever Indian classical dance enters a conversation — what state does this form come from, what's the difference between nritta and nritya, what does that hand gesture mean, what's the traditional order of a Bharatanatyam performance — answered from one hand-curated, respectful reference, rather than a scattered mix of tourism sites and forum posts.

What it does

A profile for each of the eight forms recognized by the Sangeet Natak Akademi — Bharatanatyam, Kathak, Odissi, Kuchipudi, Manipuri, Mohiniyattam, Kathakali and Sattriya — covering state of origin, style characteristics, typical costume, music-accompaniment tradition (Carnatic, Hindustani, or a distinct regional tradition), and a brief history note (dance_form_info, dance_form_search); a hasta mudra (hand-gesture) reference of 18 common gestures with their name meaning, hand formation, and typical symbolic use (mudra_info, mudra_search, random_mudra); a glossary of core terms — adavu, tala, abhinaya, tandava, lasya, gharana, navarasa, rasa, margam, and more — including a clear explanation of how nritta (pure rhythmic dance), nritya (expressive dance, this connector's own namesake) and natya (full dramatic theatre) relate to and differ from one another (dance_glossary); a detailed costume guide per form (costume_guide); the traditional general stages of learning a form, from basic steps through repertoire to a full milestone performance, along with each form's own debut-milestone name (learning_path_guide); and the typical repertoire order for a full traditional performance, such as Bharatanatyam's margam running from Alarippu through Tillana (performance_structure).

What it is not

Not a substitute for training under a qualified guru — the fine points of movement, expression, rhythm and regional or gharana style are transmitted aurally and physically across years of study, not fully captured in any short reference entry. Nritya (Dance) is deliberately conservative: where a sub-detail genuinely varies by gharana, school, or regional tradition — costume specifics, the exact naming of a training milestone, the order of items in a program — this data says so explicitly rather than presenting one version as the only one. Fully local, zero upstream calls, nothing stored.

Tools

Forms

dance_form_info — One classical dance form's state of origin, style characteristics, typical costume, music-accompaniment tradition (Carnatic, Hindustani, or a distinct regional tradition), and a brief history note. Use for "tell me about Bharatanatyam", "where does Odissi come from", "what music accompanies Kathak". Args: name.

dance_form_search — Keyword search across all eight forms' names, states of origin, style characteristics, music tradition and history notes. Use for "which dance form comes from Kerala", "which forms use Carnatic music". Args: query.

Mudras

mudra_info — One hand-gesture (hasta mudra)'s name meaning, hand formation, and typical symbolic use. Use for "what does the Pataka mudra mean", "how do you form the Anjali mudra". Args: name.

mudra_search — Keyword search across all mudras' names, meanings, hand formations and symbolic uses. Use for "which mudra represents a peacock", "find mudras used for a flower". Args: query.

random_mudra — A random hasta mudra from this dataset — good for a "mudra of the day" prompt. Use for "give me a mudra of the day", "surprise me with a mudra". Args: seed.

Per-form guides

costume_guide — A dance form's typical costume elements in detail — garment, jewelry, hair/makeup, and other notable items. Use for "what's the costume for Odissi", "what does a Kathakali performer wear". Args: dance_form.

learning_path_guide — The traditional general stages of learning a classical dance form — basic adavus/steps and posture, then item-based repertoire of increasing complexity, then a full margam or milestone performance — plus that form's own name and description for its debut milestone where one is conventionally used. Use for "how does someone learn Bharatanatyam", "what's the arangetram", "how is Kathak training structured". Args: dance_form.

performance_structure — The typical repertoire order for a full traditional performance of a classical dance form (for example Bharatanatyam's margam: Alarippu, Jatiswaram, Shabdam, Varnam, Padam, Tillana). Use for "what's the traditional order of a Bharatanatyam performance", "what happens during a Kathakali show". Args: dance_form.

Reference

dance_glossary — Definitions of core Indian classical dance terms (adavu, tala, abhinaya, nritta, nritya, natya, tandava, lasya, mudra, gharana, guru-shishya parampara, navarasa, rasa, margam) — including a clear explanation of how nritta (pure rhythm), nritya (expressive dance, this connector's namesake) and natya (full dramatic theatre) relate to and differ from one another. Use for "what's the difference between nritta and nritya", "what does tandava mean". Args: term.

Conventions

• Read-only. Every tool reads public data or computes; nothing is written anywhere and nothing about the user is stored.
• Result envelope. ok: true with data, or ok: false with a structured error (bad_input, not_found, upstream_error). degraded lists optional sources that were unreachable.
• Rate limits. Free tier 60 tool calls/minute and 300/day per user (keyed on the user identifier supplied by the host agent, else client IP); Pro keys raise this. Over-limit calls return HTTP 429 with Retry-After. initialize and tools/list are never counted.

Support

agent@connectorbay.com · connectorbay.com/nritya/support

Nritya (Dance) — Privacy Policy

Effective 24 September 2026. Unify Dynamics LLC ("we", "us"), Menlo Park, California.

What Nritya (Dance) is. Nritya (Dance) is a connector (an MCP server and REST API) that AI assistants and personal agents call on your behalf for a hand-curated Indian classical dance reference: dance form profiles, a hasta mudra guide, costume guides, learning paths, performance structures, and a glossary. You interact with your assistant; the assistant sends us only the arguments needed for that one lookup.

What we receive. The arguments of each tool call — a dance form name, a keyword, a mudra name, or a glossary term — the technical headers needed to serve the request (an IP address or a client identifier supplied by the assistant, and a Pro API key if you have one), and standard server logs.

Everything is answered from a bundled, hand-curated reference file and nothing is stored. No request is forwarded to any third party — there is no upstream call at all, live or otherwise — and no query is logged in request bodies, recorded, or used to train anything.

What we do not receive or store. We do not receive your conversation with the assistant or your name, and we do not build a profile from your queries: each request is answered independently and nothing carries over between requests. Rate-limit counters (a client identifier and timestamps) are held in memory for at most 24 hours. Hosting-provider access logs, which contain IP addresses and request paths but not request bodies, are retained for up to 30 days for security and abuse prevention.

Sub-processors. None — the entire dataset is bundled with the server and answered locally. Hosting: Vercel (United States regions).

Legal bases and your rights. Our processing is necessary to provide the service you request through your assistant. Because we store no personal data beyond short-lived logs, requests to access, correct or delete personal data are usually satisfied automatically; you can still contact agent@connectorbay.com and we will respond within 30 days. We do not sell or share personal information and do not use your data to train models.

Children. Nritya (Dance) is a general-audience service operated by the adult using the assistant.

Changes. We will post changes here with a new effective date.

Nritya (Dance) — Terms of Service

Effective 24 September 2026. These terms govern use of the Nritya (Dance) connector ("the Service") operated by Unify Dynamics LLC ("we", "us").

1. The Service. Nritya (Dance) returns a hand-curated Indian classical dance reference — form profiles (state of origin, style, costume, music tradition, history), a hasta mudra guide, costume guides, learning paths, performance structures, and a glossary — from data verified against standard, widely-published sources at build time. It is accessed through an AI assistant or directly over MCP or HTTP.
2. A reference, not a lesson. Nritya (Dance) is an independent reference tool, not affiliated with or endorsed by any gharana, institution, artist, or organization, including the Sangeet Natak Akademi. It is not a substitute for training under a qualified guru, and it deliberately notes where a detail is contested, varies by school, or is not confidently documented rather than assert something that could mislead a student or performer.
3. Facts and conventions vary. Costume specifics, training-milestone naming, and performance-order convention vary by gharana, school, and regional tradition; this Service reflects mainstream, widely- published references as of the build date stated in its own data.
4. Acceptable use. Automated use within the published rate limits is welcome.
5. Availability. The Service is provided "as is" without warranty. We may change, limit or discontinue it at any time.
6. Data. Our Privacy Policy describes what we process. In short: your query is answered from a bundled reference file, and nothing is stored.
7. Pro keys. Optional Pro API keys are issued at our discretion, are personal to the holder and may be revoked for abuse.
8. Liability. To the fullest extent permitted by law, Unify Dynamics LLC is not liable for any loss arising from use of or reliance on the Service. Our total liability is limited to US $100.
9. Governing law. California law; venue in San Mateo County, California.
10. Contact. Unify Dynamics LLC · agent@connectorbay.com · https://connectorbay.com/nritya

Nritya (Dance) support

Email agent@connectorbay.com. We answer within two business days.

• MCP endpoint: https://nritya.connectorbay.com/mcp
• REST API: https://nritya.connectorbay.com/openapi.json
• Live status: https://nritya.connectorbay.com/health

When you report a problem, include the question you asked your agent, roughly when, and which agent you used (for example Claude, ChatGPT or Gemini). Never send us passwords, account numbers or ID numbers. Nritya (Dance) never asks for them.