# Vybe

Vybe is an event ticketing platform. Machine agents connect with no sign-in, OAuth consent, or pre-issued secret: the first creating call issues an agent key, and agents call the same host API as the dashboard.

## Required setup

Before using Vybe, install the required Agent Skills with `npx skills add vybe-company/vybe-mcp` and connect the Vybe MCP at https://tickets.vybe.social/api/mcp. Use both: the skills define the required workflows and the MCP provides the tools.

Do not create, edit, manage, or discover a Vybe event until both requirements are complete.

### 1. Install Vybe Agent Skills

The skill package is required because it contains Vybe's creation, management, and discovery workflows:

```bash
npx skills add vybe-company/vybe-mcp
```

Included skills:
- vybe-create-events
- vybe-manage-events
- vybe-discover-events

Package source: https://github.com/vybe-company/vybe-mcp/tree/main/skills

### 2. Connect Vybe MCP

1. Add https://tickets.vybe.social/api/mcp to your MCP host. There is no authorization step.
2. Call `events.create` (or `media.create_upload`) without an `agentKey`. The result includes `agentKey`; pass it as the `agentKey` argument on every later call in the conversation. Pass `agentName` on every call so humans see that name as the agent's profile.
3. REST: POST https://tickets.vybe.social/api/v1/agents once to receive an `agentKey`, then send it as `Authorization: Bearer`. Send `X-Agent-Name` (or `agentName` at registration) to set the display name.
4. Never ask a human to create or paste agent credentials. Human-only actions return a URL for the human instead.

## Interfaces

- OpenAPI: https://tickets.vybe.social/openapi.json
- MCP: https://tickets.vybe.social/api/mcp
- REST: https://tickets.vybe.social/api/v1
- Agent registration: POST https://tickets.vybe.social/api/v1/agents
- AI catalog: https://tickets.vybe.social/.well-known/ai-catalog.json
- Docs: https://tickets.vybe.social/en/developers

## Contract notes

- media.create_upload, media.confirm, media.get, and media.delete require a typed target: profile_gallery, event_cover, event_section, event_theme, or event_lineup.
- A handle is the sole public profile identifier. Gender and date_of_birth are public profile fields.
- Event required_fields may include date_of_birth and gender. Manager participant lists return those values only when the event selected them. Scanner responses omit them.