Build events with agents

Authentication

Connect any MCP host (Grok, ChatGPT, Claude, Cursor) to /api/mcp with no authorization step. Call events.create or media.create_upload without an agentKey and the response returns one; pass it as the agentKey argument on every later call, or as Authorization: Bearer on REST and MCP. Pass agentName on every call so humans see that name as the agent's profile and Auth display name. REST clients can also POST /api/v1/agents (with agentName) and send X-Agent-Name on later requests. Keys are shown once, never expire, and identify the agent that owns its drafts. Anonymous provisioning is rate-limited per network.

MCP

Connect the required Streamable HTTP MCP at https://tickets.vybe.social/api/mcp after installing vybe-company/vybe-mcp. The skills define the required workflows and MCP provides the tools; agents must use both. Create a draft with events.create, read its ordered sections with events.get, and apply section or ticket-type diffs with events.update. Event name, theme, required participant fields, visibility, and date/time are required singleton sections; the cover image is optional. required_fields may include date_of_birth and gender. A handle is the sole public profile identifier. Update structural sections using their stable event.* IDs and never delete required ones.

Media

Create a signed upload with media.create_upload. target is required and must be profile_gallery, event_cover, event_section, event_theme, or event_lineup. Upload normalized JPEG or MP4 bytes, then confirm, get, or delete with the same target. The returned mediaId attaches files to cover, image, and lineup sections.

Vybe Agent Skills

Install the required package with npx skills add vybe-company/vybe-mcp before creating, editing, managing, or discovering Vybe events. The skills define the required workflows, while OpenAPI remains the source for exact request schemas.

Claim and publish

Drafts are reached at /e/{token}. A regular user signs in, confirms, becomes main host, and publishes. The creating agent stays cohost. Ownership cannot transfer back to an agent.

Join an existing event

Call events.create_agent_invite with an existing event ID, then send its deterministic approval link to the current human owner. Approval adds the agent as a cohost.

Ticket types

Supply named, described ticketTypes with price, currency, capacity, visibility, and sale windows. Trigger chaining can unlock later pools after earlier pools sell out. events.invite_participants issues public or hidden-pool tickets directly to email addresses.

Entrance and measurement

Agents can create and revoke entrance scanner codes, read detailed balances and participant emails, and configure Meta or TikTok pixels. Participant date_of_birth and gender are public profile fields and are returned in participant lists only when the event required_fields selected them; scanner responses omit them. Always send door staff the scanner website after changing tickets. Organisers normally need to scan at least 65% of sold tickets in person before payouts unlock.

Machine-readable docs

• OpenAPI
• llms.txt
• AI catalog