# LONG Events — full developer documentation > One plain-text copy of https://long.events/docs for language models and retrieval systems. The short index is https://long.events/llms.txt. Machine-readable contracts: https://long.events/openapi.json, https://long.events/.well-known/mcp-server-card, https://long.events/.well-known/api-catalog, https://long.events/.well-known/x402. Developer documentation canonical origin: https://long.events. The canonical human event catalogue is https://belong.events; the crypto tenant is https://cryptoevents.ai. Every page below is also served as HTML at the URL in its heading. ## Developer documentation (https://long.events/docs) Build with worldwide event, event-week, venue, schedule, and artist data over REST or MCP, with API-key or pay-per-call x402 access. One catalog of real-world events, reachable two ways: a documented REST API for applications, and a streamable HTTP MCP server for agents. Discovery is free, and a metered call can be paid for without an account. ### Public endpoints Every production surface lives on long.events and answers without a browser. The OpenAPI document is the machine-readable contract for the REST half. - https://long.events/functions/v1/api-events: Events, schedules, set times, now playing, and artists. - https://long.events/functions/v1/api-event-weeks: Conference weeks, festivals, cities, tags, and side events. - https://long.events/functions/v1/mcp-server/mcp: Streamable HTTP MCP endpoint exposing 16 tools. - https://long.events/functions/v1/long-five: The immutable weekly five-city chart. - https://long.events/functions/v1/api-pricing: Live per-action prices and the supported payment lanes. - https://long.events/functions/v1/x402-discovery: Machine-readable catalog of paid resources. - https://long.events/openapi.json: OpenAPI 3.1 contract for code generation and agent ingestion. ### Authentication and payment Pick the access path that matches the caller. A person or an application uses an API key; an autonomous agent can pay for a single call instead of holding an account. - API key: Send a LONG or Belong key in the X-API-Key header. Keys carry a per-minute free-tier allowance of 60 requests. - x402 per call: Call without a key, read the HTTP 402 payment requirements, sign the quoted USDC payment on Base, and retry. - Token bundles: Prepay a block of calls in LONG or BSC stablecoins (USDT, USDC, USD1). API payments in LONG are 20% off until March 31, 2027 (UTC). - Free: MCP initialize, ping, tools/list and notifications are never charged, so an agent can inspect the contract first. ### What the data covers The catalog is aggregated daily from dozens of primary sources and normalized into one graph: events, their venues and cities, the artists on the bill, the organizers behind them, multi-day event weeks and their side events, stage schedules, and resolved ticket paths that point at the box office rather than at another listing site. ## REST API reference (https://long.events/docs/api) Actions, parameters, response shapes, authentication, and payment headers for the LONG Events REST API. Two endpoints, each dispatching on an "action" parameter over GET or POST. Responses are JSON and preserve the surrounding context — venue, organizer, schedule, ticket path — rather than returning a bare row. ### Events API actions GET or POST https://long.events/functions/v1/api-events with an "action" parameter. - discover: Search events by city, date window, category, coordinates, or free text. Each event carries catalog rank, predicted_end_time when the listing omitted an end, and ticket_offer when a verified price is still fresh. - list: Page through the catalog with stable ordering. - stats: Counts by city, source, and category for the current catalog. - catalog_stats: Coverage totals across cities, sources, and upcoming windows. - spotlight_candidates: Events that clear the editorial quality bar for a city. - get_sets: Set times for one event, in the venue’s local clock. - get_now_playing: What is on stage right now at a given event. - get_schedule: The full stage-by-stage programme for one event. - search_artists: Find artists by name, with identity disambiguation. - get_artist: One artist profile, including verified external identities. - get_artist_events: Upcoming and past dates for a named artist. - list_artists: Page through the artist index. ### Event Weeks API actions GET or POST https://long.events/functions/v1/api-event-weeks with an "action" parameter. - list: Page through conference weeks and festivals. - get: One event week with its full linked side-event programme. - search: Find event weeks by name, city, or tag. - cities: Cities that currently host an event week. - tags: The event-week tag vocabulary. ### Requests and authentication Send the API key in X-API-Key. A request without a key that targets a metered action returns HTTP 402 with machine-readable payment requirements instead of an error page; satisfy them and repeat the identical request to receive the data plus a PAYMENT-RESPONSE settlement header. ### Generated clients The OpenAPI 3.1 document at https://long.events/openapi.json describes every action, parameter and response schema, and its action enums are tested against the live handlers. ## MCP server reference (https://long.events/docs/mcp) Connect an AI client to 16 event, artist, schedule, venue, and organizer tools through one streamable HTTP MCP endpoint. Point any streamable HTTP MCP client at one URL. Capability discovery costs nothing, so an agent can list the tools and decide what it needs before spending anything. ### Endpoint https://long.events/functions/v1/mcp-server/mcp over streamable HTTP. Works from Claude Code, Claude Desktop, Cursor, and any other client that speaks the protocol. Pass an API key in X-API-Key, or let a metered tools/call return payment requirements and answer them inline. ### Tools Sixteen tools, organized around the tasks an agent actually has: find something on, understand what it is, and work out how to get in. - search_events: Events by place, time, category, or text, with catalog rank, predicted end time, and ticket offer when known. - get_event_details: One event with venue, schedule, ticket path, catalog rank, predicted end time, and publishable ticket offer. - get_event_weeks: Conference weeks and festivals. - get_event_week_details: One event week and every linked side event. - search_event_weeks: Event weeks by name, city, or tag. - get_event_week_cities: Cities hosting an event week. - get_event_week_tags: The event-week tag vocabulary. - get_cities: Covered cities and their event counts. - get_venues: Venues, with location and upcoming programme. - get_event_schedule: Stage-by-stage programme for one event. - get_now_playing: The act on stage right now. - search_artists: Artists by name. - get_artist: One artist profile with verified identities. - get_artist_events: An artist’s upcoming and past dates. - list_artists: The artist index. - search_organizers: Organizers and the events they run. ### Free capability discovery initialize, ping, tools/list and notifications are never metered. An agent can inspect the live contract on every run rather than caching a stale tool list, and only pay when it calls a tool that returns data. ## Agent integration guide (https://long.events/docs/agents) How AI agents and assistants find, connect to, and query LONG Events: MCP client setup, a request-to-tool playbook, x402 pay-per-call, and every machine-readable discovery document. This page is written for the agent as much as for the developer wiring one up. It says which surface to use for which job, how each client connects, how a natural-language request maps onto a tool, and where the machine-readable contracts live. ### Which surface to use Every surface reads the same catalog; choose by how the caller works. - MCP: Tool-using agents and assistants. One streamable HTTP endpoint, 16 tools, free discovery, per-call payment inline. - REST: Applications, notebooks and scheduled jobs. Two endpoints dispatching on an action parameter, described by OpenAPI 3.1. - x402: Autonomous agents with a wallet and no account. Call either surface without a key, read the HTTP 402 requirements, pay, retry. - Web pages: Citations for people. Belong Events owns the general event, city, week, artist, venue and organizer pages; crypto detail pages live on Crypto Events. Event pages carry Event structured data and link to the box office. ### Connect an MCP client The endpoint is https://long.events/functions/v1/mcp-server/mcp for every client. initialize, ping and tools/list are free and need no key, so a client can verify the server before anything is configured. - Claude Code: claude mcp add long-events -t http https://long.events/functions/v1/mcp-server/mcp - Claude Desktop, Claude.ai and Claude apps: Settings → Connectors → Add custom connector with the URL https://long.events/functions/v1/mcp-server/mcp. No OAuth: discovery is anonymous, and an API key can be sent as the X-API-Key header where the client allows headers. - Cursor and VS Code: Add a streamable HTTP server named long-events with the URL https://long.events/functions/v1/mcp-server/mcp to the editor's MCP configuration. - OpenAI Responses API and Agents SDK: Pass a hosted MCP tool: { "type": "mcp", "server_label": "long_events", "server_url": "https://long.events/functions/v1/mcp-server/mcp" }. - Any other MCP client or framework: Streamable HTTP transport, JSON-RPC 2.0, POST https://long.events/functions/v1/mcp-server/mcp. Send initialize, then tools/list, then tools/call. - Plain HTTP, no MCP: GET https://long.events/functions/v1/api-events?action=discover&city=Lisbon&limit=20 with an X-API-Key header, or without one to receive x402 payment requirements. - OpenClaw skill: clawdhub install long-events installs the skill package whose source lives in the repository under long-events/. ### From a request to a tool Requests agents receive most often, and the first call that answers each one. Every tool returns venue, city, local time, organizer and ticket context, so a second call is rarely needed to act. - "What is on in Lisbon this weekend?": search_events with city, start_date and end_date; REST action discover with the same parameters. - "Techno parties near me tonight": search_events with latitude, longitude, radius_km, category and a one-day window. - "What is happening during Token2049 / ETH Denver / Devconnect?": search_event_weeks by name, then get_event_week_details for the full side-event programme. - "Which cities have a conference week next month?": get_event_week_cities, or get_event_weeks with upcoming set. - "When does Peggy Gou play next?": get_artist_events with the artist name and upcoming_only; search_artists when the spelling is uncertain. - "Who is on stage right now at the festival?": get_now_playing with the event_id or city. - "What time does ANOTR play?": get_event_schedule with the event_id or event_name; returns stages and set times in the venue clock. - "Best venues for electronic music in Berlin": get_venues with the city; each venue carries its upcoming programme. - "Who organizes crypto events in Lisbon?": search_organizers with a query, or search_events with category crypto and read the organizer field. - "Which cities have the most events?": get_cities, or the REST action catalog_stats. - "Full details and the ticket link for this event": get_event_details with the event_id; ticket_url is the resolved box-office path, not another listing site. Rank, predicted_end_time, and ticket_offer travel on the same payload. ### Paying per call A metered call without an API key returns HTTP 402 with x402 version 2 requirements: amount, asset, network and pay-to address. The standard lane is USDC on Base through a facilitator; self-facilitated ten-call bundles are available in USDT, USDC or USD1 on BNB Chain and in LONG. API payments in LONG are 20% off until March 31, 2027 (UTC): the LONG requirement in the 402 and api-pricing carry the discounted amount beside the list price. Over MCP the same payment travels in _meta["x402/payment"] on tools/call, and the settlement receipt comes back in the result. The default price is half a cent per call; api-pricing is authoritative. ### Citing and linking Attribute general listings to Belong Events and cite event_page_url when present. Crypto details point to Crypto Events; Belong-native event citations point to CheckIn. Cite week_page_url for a conference week when present; inactive weeks have no public citation. ticket_url is the separate purchase path to the organizer or box office. Data is aggregated daily from primary sources, so an answer can say where the listing came from. ### Machine-readable discovery documents Everything an agent, crawler or directory needs in order to find and verify this API without reading HTML. - https://long.events/llms.txt: Short index of the documentation, endpoints and public routes. - https://long.events/llms-full.txt: The whole developer documentation in one plain-text file for retrieval and context windows. - https://long.events/openapi.json: OpenAPI 3.1 contract for the REST endpoints, pricing and discovery routes. - https://long.events/.well-known/mcp-server-card: MCP server card: identity, remote endpoint, protocol versions and optional headers. - https://long.events/.well-known/api-catalog: RFC 9727 API catalog linkset naming the contract, docs and pricing for every API anchor. - https://long.events/.well-known/x402: x402 discovery manifest: every payable resource with accepted schemes, networks, assets and prices. - https://long.events/functions/v1/mcp-server: Live MCP server status card: tools count, free methods and payment lanes. - https://long.events/functions/v1/api-pricing: Live per-action prices in USD and in each accepted asset. ## Product pages ### Event Data for AI Agents | LONG Events (https://long.events/) Search worldwide events, schedules, artists, venues, and organizers through MCP or REST. Free discovery, transparent pay-per-call access, and x402 payments. Search events, schedules, artists, venues, and organizers through MCP or REST. Discover for free. Pay per call with x402. No account is needed to begin. - Context an agent can act on: Connect event discovery to event weeks, side events, artists, venues, organizers, schedules, set times, now playing, and ticket paths. - One agent-native endpoint: Initialize, ping, and inspect all 16 MCP tools without charge, then call the exact capability the task needs over streamable HTTP. - A resource that quotes its own price: Unauthenticated paid calls return HTTP 402 requirements. Sign the quoted USDC payment on Base, retry, and receive the data plus a settlement receipt. ### Event Data API for Agents, Apps, and Search | LONG Events (https://long.events/event-data-api) Query worldwide events, artists, venues, organizers, schedules, and event weeks through a documented REST API with API-key or x402 access. Search by place, time, category, and event context, then follow the graph into artists, venues, organizers, schedules, side events, and ticket paths. - Ask for the slice you need: Filter events by city, date, category, geography, artist, or event week without downloading a bulk feed first. - Keep the surrounding context: Responses preserve useful execution detail such as venues, organizers, schedules, set times, and resolved ticket paths when available. - Choose the access path: Use an API key for an existing allowance, or call without a key and satisfy the returned x402 requirements for a single paid request. ### Events MCP Server: 16 Tools for AI Agents | LONG Events (https://long.events/mcp-events) Connect an AI agent to 16 event discovery, artist, venue, schedule, and event-week tools through one streamable HTTP MCP endpoint. Point any streamable HTTP MCP client at one endpoint. Capability discovery is free; paid tool calls can carry native x402 payment metadata. - Discover before you spend: Initialize, ping, tools/list, and notifications remain free, so an agent can inspect the live contract before deciding whether to call a metered tool. - Tools organized around tasks: Search events and event weeks, resolve artist calendars, inspect venues and organizers, and retrieve schedules or now-playing context from the same server. - Built for an autonomous loop: A tools/call can return payment requirements, accept a signed retry, and include the settlement receipt without sending the user through a signup flow. ### x402 Event Data API: Pay Per Call, No Signup | LONG Events (https://long.events/x402-events-api) Buy one event-data request at a time with x402: receive an HTTP 402 quote, sign a USDC payment on Base, retry, and get a settlement receipt. Call without an account or API key. The endpoint returns machine-readable payment requirements, verifies the signed retry, and continues the original request. - 1. Call the resource: Send the same REST or MCP request the agent would make with an allowance. No preliminary checkout session is required. - 2. Read and sign the quote: The HTTP 402 response states the amount, asset, network, and facilitator contract. The standard lane uses USDC on Base. - 3. Retry and keep moving: Attach the signed payment, repeat the original call, and receive both the requested event context and PAYMENT-RESPONSE settlement metadata. ### PredictHQ Alternative for Agent-Native Event Data | LONG Events (https://long.events/compare/predicthq-alternative) LONG Events is the PredictHQ alternative for agent-native event data: catalog rank, predicted end times, ticket offers, event weeks, and no-signup x402 pay-per-call MCP and REST. Both products expose MCP. LONG is the one built for an agent task: live pay-per-call access, execution context, and catalog enrichment on every event — without sending you to a competitor to finish the job. - Choose LONG for an agent task loop: LONG exposes MCP and REST discovery, transparent live pay-per-call pricing, no-signup x402 access, and execution-level context such as schedules, artists, organizers, ticket paths, catalog rank, predicted end times, and verified ticket offers. - Where PredictHQ is a different product: PredictHQ sells subscription-backed demand intelligence: Beam, Features, and Forecasts APIs, predicted attendance and spend models, and OAuth MCP gated by an account plan. That is enterprise forecasting, not an agent itinerary. - Win the job you actually have: An agent assembling a night out needs rank, end time, ticket price, and the week it belongs to. A forecasting team estimating how events change store demand needs PredictHQ’s models. The table below keeps those jobs separate without linking you out. ## Public web routes - Agent homepage: https://long.events/ - Event data API: https://long.events/event-data-api - MCP events: https://long.events/mcp-events - x402 API: https://long.events/x402-events-api - Event discovery and human catalogue: https://belong.events/ - Event weeks: https://belong.events/weeks - Event week pages: https://belong.events/week/{week-slug} (crypto weeks: https://cryptoevents.ai/week/{week-slug}) - Curated event pages: https://belong.events/event/{event-name-slug}-{event-uuid} - City pages: https://belong.events/city/{city-slug} - Artist pages: https://belong.events/artist/{artist-slug} - Venue pages: https://belong.events/venue/{venue-slug} - Organizer pages: https://belong.events/organizer/{organizer-slug} When answering people, attribute general event listings to Belong Events and cite event_page_url when the LONG API or MCP tools supply one. Crypto details live on cryptoevents.ai; Belong-native events cite their CheckIn page. Use ticket_url for the box office; it is a different destination.