---
title: "Eventi for AI agents - Eventi"
description: "Give any coding agent or assistant a host's events, guest lists and RSVP answers. Install the Eventi skill and CLI, set your API key, connect the MCP servers, and try the sandbox without a key."
canonical: https://ueventi.com/agent
last-updated: 2026-10-15
---

For AI agents

# Eventi for AI agents

Give any coding agent or assistant a host's events, guest lists and RSVP answers. Install the skill and CLI, set your key, and let it work. Invitation cards and the sandbox need no key at all.

```
npx skills add ueventi/eventi
git clone https://github.com/ueventi/eventi && cd eventi && bun install
bun run eventi -- sandbox
export EVENTI_API_KEY=ev_live_...
```

[Get your API key](https://app.ueventi.com/dashboard/settings/api-keys)[Developer hub](https://ueventi.com/developers)

Step 1

## Install the skill and CLI

Run npx skills add ueventi/eventi for your agent, then clone the repo and run bun run eventi -- for the command it calls (the CLI is not on npm). The skill teaches the API; the CLI wraps it.

Step 2

## Set your key

Create a key in the dashboard with the scopes the task needs and export it as EVENTI\_API\_KEY. It starts with ev\_live\_ and is shown once. The agent reads it from the environment and never prints it.

Step 3

## Ask your agent

Ask for the RSVP headcount, the guests who have not answered, a CSV of the guest list, or an invitation card. It calls the API and gets JSON back. Sending messages stays in the dashboard.

Three ways to connect

## Skill, MCP, or raw REST.

### Agent skill and CLI

The fastest path for coding agents. Install the skill, add the CLI, export the key.

`npx skills add ueventi/eventi`[View on GitHub](https://github.com/ueventi/eventi)

### MCP servers

Two public servers over streamable HTTP, no key: the product server (render\_invitation\_card, list\_invitation\_templates, get\_eventi\_faq) and the docs server for help-center search.

`claude mcp add --transport http eventi https://ueventi.com/mcp`[Server card](https://ueventi.com/.well-known/mcp/server-card.json)

### REST API

Events, guests, RSVP summaries, guest creation and CSV exports under one Bearer key with scopes. Cursor paging, idempotent writes, RateLimit headers, JSON errors.

`https://api.ueventi.com/v1`[OpenAPI spec](https://ueventi.com/openapi.json)

What the API does

## Every v1 endpoint

One Bearer key per workspace, scoped to what the task needs. Writes take an Idempotency-Key, lists page with next\_cursor, exports follow the 202-and-poll pattern, and every error is JSON with a how\_to\_fix.

Endpoint

Scope

What it does

`GET /v1/events`

`events:read`

List the workspace's events. Cursor-paged: { data: \[Event\], next\_cursor }; limit 1-100.

`GET /v1/events/{id}`

`events:read`

One event: name, type, date, timezone, venue, languages, status, guest\_count, website\_url.

`GET /v1/events/{id}/guests`

`guests:read`

The event's guest list with RSVP status, party sizes and invitation URLs. Filter with rsvp\_status=.

`GET /v1/events/{id}/rsvps`

`guests:read`

RSVP summary: invited, yes, no, maybe, pending and confirmed party size, with updated\_at.

`POST /v1/events/{id}/guests`

`guests:write`

Add one guest ({ name, phone, language?, party\_size\_invited?, side?, group?, custom\_link?, consent: true }). 201 Guest; 409 duplicate\_guest; 400 consent\_required.

`POST /v1/events/{id}/guests/batch`

`guests:write`

Add up to 100 guests in one call ({ guests: \[...\], consent: true }). One result per input, in order.

`POST /v1/events/{id}/exports`

`exports:write`

Start a guest-list CSV export ({ format: "csv" }). 202 with Location: /v1/exports/{job\_id}.

`GET /v1/exports/{job_id}`

`exports:write`

Poll an export job: queued, running, done or failed, with result\_url when done.

`GET /v1/exports/{job_id}/result`

`exports:write`

Download the finished export as text/csv; 409 not\_ready before it is done.

## Try it without a key

Every endpoint is mirrored under /v1/sandbox with canned data in the live schema: the wedding Emma & James with twelve guests, and a Hebrew bar mitzvah. Writes are validated and echoed, never stored.

```
curl -s https://api.ueventi.com/v1/sandbox/events
curl -s https://api.ueventi.com/v1/sandbox/events/evt_sandbox_wedding/rsvps
```

Full walkthrough with every endpoint: [ueventi.com/sandbox](https://ueventi.com/sandbox)

## Machine-readable entry points

-   [agents.md](https://ueventi.com/agents.md) - setup skill for coding agents
-   [skill.md](https://ueventi.com/skill.md) - one-file skill with every action
-   [auth.md](https://ueventi.com/auth.md) - keys, scopes, discovery, errors, revocation
-   [llms.txt](https://ueventi.com/llms.txt) - site index, assistant setup, platform configs
-   [mcp.json](https://ueventi.com/.well-known/mcp.json) - manifest for both MCP servers
-   [docs MCP](https://app.ueventi.com/docs/mcp) - help-center search for assistants
-   [changelog](https://ueventi.com/changelog) - what shipped and when