VenuNite Events
स्रोत-लिंक्ड अमेरिकी इवेंट सूचियों को तारीख, स्थान, दूरी, लागत, श्रेणी और स्थल के माहौल के आधार पर एक मुफ्त रिमोट MCP सर्वर के माध्यम से खोजें।
दस्तावेज़
Loading...
VenuNite may earn a commission from ticket purchases made through links on this site.
Things to DoCitiesArtistsExploreFree MCP ConnectorLocal Events API
Discover
Explore EventsThings to DoBrowse ArtistsBrowse Cities
For Fans
Suggest a VenueSend FeedbackReport a Bug
Company
For Venues
For Developers
Free Events MCPEvents Data API
Discover the best live events across the United States.
VenuNite may earn a commission from ticket purchases made through links on this site.
Privacy PolicyTerms of Service
Developers
🌙
Free remote MCP connector
A free MCP connector for local events.
Loading current catalog coverage…
Loading…
Search events, venues, artists
All States
Discover
© 2026 VenuNite
Discover
For Fans
Company
For Venues
For Developers
© 2026 VenuNite
Free event search for your AI
A free MCP connector for local events.
Ask the assistant you already use what’s happening nearby: concerts, brewery gigs, markets and community events, with venue details and links to check the source.
Get a free MCP keyTry without signupTry a live search
Works with Claude, ChatGPT, Codex, Cursor and other MCP clients. No key needed to try.
Neighborhood calendars, alongside major shows.
Bring brewery nights, library programs, markets and community events into the conversation. VenuNite combines major ticketing feeds with direct venue and community calendars across the U.S.
—
sourced outside 8 named ticketing feeds
—
of venues list 1–2 upcoming events
These shares describe source provenance and venue mix. They do not measure listings exclusive to VenuNite or guarantee coverage in a particular area.
Coverage measurements and comparisons
VenuNite labels records whose ingestion source is outside eight named ticketing-aggregator prefixes. That proves source provenance; it does not, by itself, prove the event is absent from every competitor catalog. The prefixes are ticketmaster, eventbrite, axs, seatgeek, aeg, livenation, dice, ticketweb.
The provenance snapshot uses upcoming rows in TrustedEventServingView (every metric is computed under WHERE "startDate" > now()), and is recomputed daily.
How to compare coverage
- Sample 20 US metros across “tonight” and “this weekend.”
- Run the same place, time, and category queries against each published catalog.
- Normalize occurrences, deduplicate recurring series, and validate the original source URL.
- Publish unique valid-event counts, overlap, stale-link rate, query timestamp, and raw methodology—not an unsupported “most complete” claim.
Ticketmaster comparisonEventbrite comparisonMeetup comparisonHyperlocal coverage
Start free with MCP. Upgrade when you need more.
MCP is available free. Paid plans add REST access and higher MCP allowances.
MCP lets compatible AI assistants discover and call VenuNite tools. REST lets your app or backend request event and venue JSON directly. Both connect to VenuNite's event data; your plan sets the access and limits.
Try MCP
$0 · no signup
Up to 10 events per search, 30 days ahead. Shared fair-use limits apply.
Free MCP
$0 · free account
5 tool calls/minute and 100 tool calls/day per account. Up to 20 events per search, 30 days ahead.
Ongoing free access. Your Builder key works in MCP clients that support API keys.
Paid · REST + MCP
From $29.99/month
REST event search plus higher MCP allowances, using one key for your app or assistant.
Separate REST trial: eligible verified accounts can try event search for 7 days or 1,000 event rows, whichever comes first. No credit card or automatic charge.
Full usage limits and how allowances are shared
Tool calls and delivered events have separate allowances. Without a key, the delivered-event budget is shared across your network. With a key, allowances are shared across every key on your account. Free MCP and the eligible REST trial are separate.
Without a key: up to 5/minute and 10 per 24-hour transport session when the client returns VenuNite's signed session token through the Mcp-Session-Id header or cookie; shared-network fair-use ceilings otherwise.
Both search and ticket-handoff tools/call invocations count. MCP initialization, capability discovery, and tool listing do not use the allowance. The count is taken during admission, before your arguments are checked, so a call that comes back with validation_errors has still spent one—though not any rows, because a failed search settles its row reservation at zero. Anonymous handoff calls also spend a call before returning authentication_required; handoffs never consume event-row allowance. Fix one careful call rather than looping.
What a free search returns, and how far ahead
Calls are one budget; delivered events are a second one. Both free tiers are capped on both. The result cap comes back as applied_filters.limit on every search the server actually runs, and on the free tiers the horizon comes back as applied_filters.horizon_end, so a narrowed answer never has to be guessed at (a plan with no horizon simply omits that key); a call rejected before retrieval returns validation_errors and an otherwise empty applied_filters instead—except a date_start past the plan horizon, which deliberately returns horizon_end so you can see what to narrow to—and the row budget is reported only when it runs out.
Events per search
10 without a key, 20 with a free Builder key, whatever limit asks for. A limit above the plan cap but within the schema maximum of 100 is clamped, not rejected: applied_filters.limit reports the number actually used and applied_filters.requested_limit reports what you sent. Above 100 the call is rejected outright—see the bounds below. Asking for 100 without a key returns 10.
How far ahead
30 days without a key, 30 days with a free key, measured from the request clock rather than from date_start. applied_filters.horizon_end is the furthest instant the plan may search to; applied_filters.date_end is the end of the window actually searched. A window that ends past the horizon is trimmed to it; a date_start already past it returns zero events plus a validation_errors entry on date_start. A festival 45 days out is therefore invisible on the free tiers—that is the horizon, not an empty catalog.
Delivered rows per 24 hours
500 events without a key, 2,000 with a free key, over a rolling window. Exhausting it returns row_budget_exhausted with zero events while tool calls may still be available. The no-key budget is keyed to your source IP—so everyone behind one office, campus, or assistant-vendor egress address draws on the same rows—while a key's budget is per account and shared across every key on it. Paid REST and MCP use the account's shared row allowance. A free Builder MCP allowance does not include paid REST access; eligible verified accounts can separately try REST before subscribing. See the Data API plans and trial details.
See what your AI will find
Your first event search
Choose a city and date to browse real event listings. No signup, install or model API key required. Check the results, then take a working request into your own project.
Try a cityDenverAustinPortland
City and stateWhat are you looking for? (optional)
Date (optional)
City's time zoneEasternCentralMountainArizonaPacificAlaskaAleutianHawaii
Leave the date blank for the next 7 days. Searches cover a 15-mile radius and dates up to 30 days ahead.
Search events
Uses free no-key MCP access: 5 searches/minute and 10 per rolling 24 hours per session, plus shared-network limits. Get a free MCP key for more calls in a supported client. Search details are handled under our privacy policy.
Node.js exampleMCP requestJSON response
search_events
From your first search to your first integration.
Run a search to generate a working Node.js example with your exact filters. Inspect the request and the live JSON response here.
Connect in minutes
Connect the assistant you already use.
Pick your client, add VenuNite and ask for events near a city or neighborhood. Try without signup under shared fair-use limits. Get a free MCP (Builder) key when you need an account-based allowance in a compatible client.
Choose “Use a Builder key” for client-specific authenticated setup. ChatGPT web and Claude's custom-connector dialogs use no-key access; the key examples are for Codex, Cursor, and VS Code.
Advanced: ChatGPT endpoint behavior
There is a second endpoint for ChatGPT: https://mcp.venunite.com/v1/chatgpt/mcp/ serves the same tools under the same allowances, but its search schema drops the five location arguments—place_name, center_lat, center_lng, state_hint, timezone—and takes the search center from the coarse location ChatGPT sends with the request instead. Its results therefore omit applied_filters.center and round distances to a tenth of a mile, and it returns location_unavailable when the client supplies no US location. The panel below configures the general-purpose endpoint, which accepts an explicit place from any client.
What the connector can access
The hosted search cannot modify events or calendars. Calls log request and search details plus quota and operational telemetry as described in the privacy policy. Tools: search_events + authenticated create_ticket_handoff.
No-key trialUse a Builder key
ChatGPTClaudeClaude CodeGemini CLICodexCursorVS Code
Open VenuNite Events in the Claude directory, connect it, and enable it in your conversation. Then ask for events in your city. Managed workspaces may need an administrator to enable the connector.
Manual setup and workspace permissions
Individual Free, Pro, or Max: open Customize → Connectors, choose + → Add custom connector, name it VenuNite Events, and paste this URL (Free allows one custom connector). Team/Enterprise: an Owner must add it under Organization settings → Connectors; members then connect it under Customize → Connectors.
https://mcp.venunite.com/v1/mcp/
Copy
Official Claude setup documentation · Checked October 1, 2026
Try these prompts
Find a plan worth going out for.
Enable VenuNite for the conversation, then replace YYYY-MM-DD below with an upcoming date. Include the city and state so your assistant does not have to guess your location.
- “Use VenuNite’s search_events to find events starting in Denver, Colorado, on YYYY-MM-DD. Show the local start time, venue, and source link for each result. Label reservation-only listings.”
- “Find free live music in Austin, Texas, this coming weekend. Confirm that each listing is a live performance with free admission, and show the local date and source link.”
- “Find date-night events starting in Portland, Oregon, tomorrow evening with a known admission price of $100 or less per person. Exclude unknown prices, verify each price at its source, and show fees separately when available.”
A successful connection exposes search_events. A successful search returns matching listings or an empty result; zero matches does not mean the connection failed. Check the original source for schedule and ticket changes.
What agents receive
Answers you can verify.
- ✓ISO-8601 start/end timestamps, venue name, city, and state
- ✓Price and age metadata when captured; missing values remain unknown
- ✓event_id and canonical VenuNite event_url for citations and ticket handoffs; the original source url is retained when available, and ticket_url is not returned by search
- ✓ticket_link_status (available, unavailable or missing); an event with no usable link is still returned, with event_url
- ✓Distance when the venue’s location precision supports it
- ✓Filters for keyword, date range, radius, category, admission price, venue vibe, sort order, and per-venue diversity
applied_filters.center is the search center; individual venue coordinates are not returned. state_hint disambiguates a place name, rather than restricting events to one state. A radius can include neighboring states.
Search guidance for places, dates and prices
Turn a prompt into a reliable search
Resolve the place
Use place_name with a city and state, or pass both center_lat and center_lng when you have a precise location. Check the returned center and radius. If the place cannot be resolved, ask for a clearer location or coordinates.
Match the intended day
Pass date_start and date_end with explicit UTC offsets, plus the local IANA timezone (for example, America/Denver). Convert returned timestamps to that zone for display; timezone controls day grouping, not timestamp formatting. Use date_match: "starts_within" for events starting on a requested day or evening. The default date_match: "overlap" also includes events that began earlier and are still running. Label ongoing events and reservation windows so their start is not mistaken for a new show.
Make the budget explicit
For the Portland prompt, pass max_cost: 100 and include_unknown_prices: false. The default include_unknown_prices: true retains unknown prices with positive price bounds; those results do not establish a budget match. max_cost: 0 requires explicitly free admission. A listed price is not a total outing cost: check the original source for ticket tiers, fees, availability, and optional extras before calling an option affordable.
Check what the listing establishes
Music categories can include films or talks about music. Romantic and date-spot tags influence ranking without guaranteeing a match. Read the description and source before making those claims, and check whether a published time means doors, show start, or appointment availability.
Advanced search arguments and bounds
The rest of the arguments
Location, dates, and budget are covered above. These six shape the result set and are the ones most often missed.
vibe_tags — 5 of these are hard filters
A fixed 49-tag vocabulary across ambiance, social, time, age, venue type, and activity; at most 12 per call. Most tags influence ranking, but queer-friendly, family-friendly, all-ages, 18-plus, 21-plus are safety-critical HARD filters: a venue that does not carry the tag is excluded from the results entirely, never merely down-ranked. Sending family-friendly for someone who only said “something fun tonight” removes most venues and looks like an empty catalog. Send one only when the request explicitly asked for that property.
sort
date, distance, demand, or relevance. Results are grouped by calendar day in timezone; sort orders within each day. The schema publishes those four, and a value outside them is rejected by the tool's input schema before the search runs, so there is no graceful fallback for a typo. distance with no resolved center does fall back to chronological instead of failing—compare applied_filters.sort with sort_requested to see whether that happened.
limit and max_events_per_venue
limit defaults to 20 and is then clamped by the plan cap above. max_events_per_venue defaults to 1, which is what makes a “what is on this weekend” answer span many venues; raise it to 3–5 for “what is on at this one room,” up to 20.
local_only
true clamps the effective radius to a neighborhood-scale maximum for the local density—10 miles urban, 30 suburban, 50 rural—even when radius_miles is larger. Omitting radius_miles entirely gets the density-aware default instead of a guess.
min_cost
Lower bound in USD, the counterpart to max_cost. Rarely useful—set it only when free events are explicitly unwanted.
An out-of-range value rejects the whole call. Except for the plan caps above, which clamp, a bound that is exceeded is a failure rather than a correction: the call returns zero events and a validation_errors list naming each field. radius_miles 0.5–500, a date window of at most 180 days, at most 12 vibe_tags and 10 categories, and query_text up to 500 characters are checked by the search layer and behave exactly that way. limit 1–100 and max_events_per_venue 1–20 are different: they are published as minimum/maximum in the tool's input schema, so your MCP client or the transport rejects them first with an “Input validation error” message and no validation_errors list at all.
Every search needs a subject. At least one of query_text, both center_lat and center_lng, place_name, vibe_tags, or categories must be present. A date-only call—just date_start and date_end—is rejected with a _root validation error, because it would ask for the entire upcoming catalog.
From a recommendation to the ticket seller
When someone wants tickets, create a confirmation link to a supported seller using a Builder or paid key. They choose whether to continue to external checkout. This does not buy, hold or reserve tickets.
Ticket handoff setup, limits and confirmation flow
Cite the canonical event_url in each search result. When the user wants tickets, call create_ticket_handoff with only the result's event_id. A site-issued free Builder or paid vn_live_ bearer key is required. The authenticated key supplies attribution; callers cannot choose a destination or partner identity.
{"name":"create_ticket_handoff","arguments":{"event_id":654662}}
Present the returned handoff_url to the user. It expires after 15 minutes; opening or previewing it records no affiliate click. The user must choose Continue to redeem it at most once and reach the supported seller's checkout. Repeated Continue returns 409 without another seller redirect. Handoff calls use the normal MCP call allowance plus a separate limit of 10 creation requests per minute per account across REST and MCP; they consume no event-row allowance. Some events have no supported ticket link. MCP returns ticket_handoff_not_available without a fallback URL; use event_url from the preceding search result to show the event page.
This action creates a referral, not a purchase or reservation. It does not check live inventory, guarantee final prices, or report confirmed purchases. No-key browser connectors can search but receive authentication_required for handoffs. OAuth account linking is not available; use a client that forwards your bearer key. The REST handoff reference describes the same response fields and limits.
Connection and quota help
The server connects, but my assistant does not search
Enable VenuNite and its search_events tool in the current conversation. Ask explicitly to use VenuNite, with a city, state, and upcoming date. If no tool appears, verify the full https://mcp.venunite.com/v1/mcp/ URL, use Streamable HTTP, and refresh the client's tool list. Managed workspaces may require administrator approval.
Too many requests or allowance exhausted (429)
Pause automatic retries. VenuNite's 429 carries no Retry-After header, so a client that shows no countdown is behaving normally—use the windows instead. The per-minute allowance is 5 tool calls without a key and 5 with a free Builder key; a paid plan carries its own higher per-minute limit. It is counted over the last 60 seconds rather than reset on the minute, so waiting 60 seconds after the rejected call always clears the per-minute limit. Read the 429 body's title to tell which limit fired. The per-minute titles are rate_limit_exceeded with a key, anonymous_rate_limit_exceeded without one, and anonymous_ip_rate_limit_exceeded for the shared-network ceiling. The 24-hour titles are daily_quota_exceeded with a key, anonymous_daily_quota_exceeded without one, and anonymous_ip_daily_abuse_limit_exceeded for the shared network; waiting a minute does nothing for any of those three. Daily limits use a rolling 24-hour window, not a midnight reset: an individual call frees its slot roughly 24 hours after you made it. A row_budget_exhausted result is a different limit and arrives as a tool result rather than a 429; waiting a minute does not clear it. A free Builder key gives an account allowance in clients that support bearer headers. Creating more keys on the same account does not increase that allowance.
My key is rejected (401), no-key access cannot be metered (401), or I still get the no-key allowance
Check that VENUNITE_API_KEY is set in the environment of the client making the request, then restart that client. Set the variable to the full vn_live_ key without quotes, spaces, or a Bearer prefix in its value. The examples add the header prefix for you. If the key was lost or revoked, create a replacement under Developer keys. OAuth client-ID and client-secret fields do not accept VenuNite keys. A 401 anonymous_ip_unresolvable is a different failure and is not about your key: the keyless tier is metered per source address, and VenuNite could not determine one for the request. That is usually a proxy or tunnel that strips the client address; sending a key instead removes the need for it.
Searches come back asking me to verify my email
An email_verification_required result means the key is valid but the account's free allowance is not active yet. Verify the email on the account under Developer keys and retry. This one is not an HTTP status: it arrives as an ordinary 200 response whose tool result is flagged as an error, so a client that only inspects status codes will report the call as a success with no events. A paid developer plan is never gated on verification.
No-key access is unavailable on a shared network, or the session expired
Preserving the signed Mcp-Session-Id header or session cookie returned by VenuNite gives an anonymous client a session allowance; shared-network fair-use ceilings still apply. Those ceilings are 300 tool calls per minute and 10,000 per rolling 24 hours from one source address, shared by everyone behind it—an office, a campus, or an assistant vendor's egress can reach them without any one person doing so. A Builder key provides a portable account allowance in supported clients. If the server explicitly returns 404 session_terminated for an expired session, reconnect so the client can initialize a new session. Reconnecting is not a remedy for a quota limit.
The search returns no events, or a temporary service error
For a successful search with no matches, check the city, upcoming date, radius, and filters, then broaden one constraint. Read applied_filters before broadening: horizon_end shows whether the date was past the free lookahead, and a validation_errors list means the call was rejected outright rather than searched—a date-only call and a date_start past the free horizon are the two common causes. A safety vibe tag is different: the call runs, and applied_filters.strict_tags shows the tag that excluded every venue, so drop it if the user did not ask for that property. For a temporary service error, wait briefly before retrying; avoid a retry loop. If it persists, check service readiness below and email the client name, time of failure, error text, and x-request-id if available. Never include your API key.
Give your next event search a local starting point.
Get a free MCP key for ongoing access in a compatible client, or try without signup. Paid plans add REST event search and higher MCP allowances.
Get a free MCP keyTry without signup
Privacy · Terms · Service readiness · hello@venunite.com
72%
sourced outside 8 named ticketing feeds
68%
of venues list 1–2 upcoming events
Browse Live Events by State
AlabamaAlaskaArizonaArkansasCaliforniaColoradoConnecticutDelawareDistrict of ColumbiaFloridaGeorgiaHawaiiIdahoIllinoisIndianaIowaKansasKentuckyLouisianaMaineMarylandMassachusettsMichiganMinnesotaMississippiMissouriMontanaNebraskaNevadaNew HampshireNew JerseyNew MexicoNew YorkNorth CarolinaNorth DakotaOhioOklahomaOregonPennsylvaniaRhode IslandSouth CarolinaSouth DakotaTennesseeTexasUtahVermontVirginiaWashingtonWest VirginiaWisconsinWyoming