VenuNite Events

날짜, 위치, 거리, 비용, 카테고리, 장소 분위기별로 소스 연동된 미국 이벤트 목록을 무료 원격 MCP 서버를 통해 검색하세요.

venunite.com에서 보기이 MCP 사용해 보기스폰서

문서

VenuNite may earn a commission from ticket purchases made through links on this site.

Share your feedback →

Things to Do Cities Artists Explore Free MCP Events API

About Privacy Terms

Discover the best live events across the United States.

VenuNite may earn a commission from ticket purchases made through links on this site.

VENUNITE

Explore

Developers

🌙

Free remote MCP connector

Local events, linked back to the source.

Loading current catalog coverage…

Loading…

Home Explore Saved

Search events, venues, artists

All States

Discover

For Fans

Company

For Venues

For Developers

Free remote MCP connector

Local events, linked back to the source.

Give an assistant access to upcoming events at venues across all 50 states—including library programs, farmers markets, brewery gigs, civic events, and community nights.

Connect free Create a free Builder key

https://mcp.venunite.com/v1/mcp/ · one discovery-only tool: search_events

Connect in minutes

Paste one URL. Ask about tonight.

No key is required for an instant trial under shared fair-use limits. The connector is hosted over Streamable HTTP, cannot modify events or calendars, and returns the original event source when one is available. Calls log request and search details plus quota and operational telemetry as described in the privacy policy.

Choose “Use a Builder key” for client-specific authenticated setup. ChatGPT web and Claude's custom-connector dialogs use the no-key trial; the key examples are for Codex, Cursor, and VS Code.

There is a second endpoint for ChatGPT: https://mcp.venunite.com/v1/chatgpt/mcp/ serves the same tool under the same allowances, but its 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.

Connection or quota trouble?

No-key trialUse a Builder key

ChatGPTClaudeCodexCursorVS Code

On ChatGPT web, enable Developer mode in Settings → Security and login. Open Plugins, use the + button to create a developer-mode app, paste this URL, and choose No Authentication. Select the app from Developer mode in the conversation's + menu. Availability depends on your plan and workspace permissions.

https://mcp.venunite.com/v1/mcp/

Copy

Official ChatGPT setup documentation · Checked September 2, 2026

Free enough to build something real.

Instant trial

$0 · no signup

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. Up to 10 events per search, 30 days ahead

Free Builder

$0 · free account

5/minute and 100 tool calls/day per account. Up to 20 events per search, 30 days ahead

Production Data API

$29.99/month

60 requests/minute, REST and MCP, self-serve cancellation

Only actual tools/call event searches 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. 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 and an otherwise empty instead—except a past the plan horizon, which deliberately returns so you can see what to narrow to—and the row budget is reported only when it runs out.

Try these prompts

Useful on the first call.

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

Coverage proof, without hand-waving

Long-tail provenance is measurable. Competitor absence is a separate test.

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.

—

serving rows sourced outside those prefixes

—

distinct ingestion sources

—

serving rows created, 7-day mean

—

venues with 1–2 upcoming events

The provenance snapshot uses upcoming rows in TrustedEventServingView (every metric is computed under WHERE "startDate" > now()), is recomputed and cached daily, and counts rows created during the previous seven days rather than net additions after removals.

Public benchmark methodology

Sample 20 US metros across “tonight” and “this weekend.”

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), the trial cannot be metered (401), or I still get the trial 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.

Let your assistant find the neighborhood-sized stuff.

Connect without a key now, or create a free key when you need a durable allowance.

Connect free Create a free key

Privacy · Terms · Service readiness · hello@venunite.com

validation_errors

applied_filters

date_start

horizon_end

Events per search

10 on the no-key trial, 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 on the trial, 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 on the trial, 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 trial 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. The Data API charges the same ledger, so if an account ever holds both a paid Data API plan and a row budget the two draw down together; today a free Builder key is not provisioned for the REST Data API (/v1/events resolves with allowFree: false and 403s a free plan), so its rows are spent on MCP alone.

✓

Price and age metadata when captured; missing values remain unknown

✓The original event source when available; this is a discovery surface, so the separate ticket-purchase link is not returned—the source URL may still be a ticketing page
✓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.

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.

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.

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 comparison Eventbrite comparison Meetup comparison Hyperlocal coverage

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.

The trial 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.

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 9 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.

Give an assistant access to 411,000+ upcoming events at 38,000+ venues

71%

serving rows sourced outside those prefixes

7,091

distinct ingestion sources

7,629/day

serving rows created, 7-day mean

61%

venues with 1–2 upcoming events

Browse Live Events by State

Alabama Alaska Arizona Arkansas California Colorado Connecticut Delaware District of Columbia Florida Georgia Hawaii Idaho Illinois Indiana Iowa Kansas Kentucky Louisiana Maine Maryland Massachusetts Michigan Minnesota Mississippi Missouri Montana Nebraska Nevada New Hampshire New Jersey New Mexico New York North Carolina North Dakota Ohio Oklahoma Oregon Pennsylvania Rhode Island South Carolina South Dakota Tennessee Texas Utah Vermont Virginia Washington West Virginia Wisconsin Wyoming