For AI agents
AI assistants are welcome here. Three doors, depending on whether you are acting for someone with a BandMate account.
Start with /llms.txt (summary) or /llms-full.txt (everything). These pages have a Markdown twin: add .md to the path, or send Accept: text/markdown to the HTML URL.
Public, no account, JSON enveloped as { "data": ..., "meta": ... }.
POST https://bandmateai.com/api/v1/public/bands/{slug}/booking-inquiry with a JSON body. No account needed. Required: name, email, venue_or_event_name, details (10–5000 characters). Optional: proposed_date (YYYY-MM-DD), budget_range, is_booker. Say which agent is submitting in details. The band reads it in their inbox and replies to the email given.
{
"name": "Jordan Lee",
"email": "jordan@example.com",
"venue_or_event_name": "Riverside Summer Series",
"proposed_date": "2027-06-19",
"details": "Outdoor stage, 7–9pm, PA provided. Submitted by an AI assistant on behalf of Jordan Lee.",
"budget_range": "$600–800",
"is_booker": true
}201 on success. 403 if the band has inquiries turned off. 429 after three inquiries a day from one email.
BandMate is an MCP server. A Band or Band Pro member connects you from their side: they add the URL below in their client and approve it once on bandmateai.com. You then act as them, see only their bands, and do what their role allows: gigs, pay, venues, expenses, mileage.
https://bandmateai.com/api/v1/mcp
OAuth 2.1 with PKCE and dynamic client registration. An unauthenticated request returns 401 with a WWW-Authenticate challenge naming the resource metadata; follow it. Discovery: /.well-known/oauth-protected-resource/api/v1/mcp.
list_bands — bands, your role, plan, booking contact and whether the connector is enabledlist_gigs — upcoming or past gigs with your pay and miles; owners and managers see the band totalget_gig — one gig in full, including tech notescheck_availability — what you already have on a date or range, across every bandcreate_gig — add a gig to a band you own or manage; a city/state-only address gives an estimated distanceupdate_gig — edit a gig: date, times, venue, pay, status, notes; only the fields passed changecancel_gig — cancel a gig and keep it in historydelete_gig — delete a gig permanently; owner only, and only after you confirmlist_members — a band's members with role, position and how each is paidinvite_member — invite someone by email with a role, position and pay type; they get a join linkresend_invite — send a pending invite again and extend it a weekcancel_invite — revoke a pending inviteset_member_pay — set one member's pay on a gig, apart from the band totalset_member_rate — put a member (sound engineer, sub) on a flat fee with a dated rate schedulemark_paid — record a payment: amount, date, method (cash, Venmo, Zelle, check)log_mileage — log your own round-trip miles for a gigcreate_expense — log an expense with category, vendor, receipt note and giglist_venues — a band's venues, with ids for create_gigcreate_venue — add a venue with address, load-in notes and contact; reuses an existing matchupdate_venue — edit a venue's details or your band's notes and contact for itmerge_venues — merge a duplicate venue into the one to keep, moving its gigs; after you confirmset_band_contact — store the band's leader or booker name, email and phonecalendar_feed — your personal ICS calendar URL plus per-band feeds, with subscribe stepsmileage_summary — a year of deductible miles, effective rate and each triptax_summary — income marked paid, expenses by category, the mileage deductionlist_expenses — your logged expenseslist_equipment — your gear with purchase details and rig noteslist_setlists — a band's setlistsget_setlist — every song on a setlist with key, BPM and duration