A published event.
More possibilities.

For your website: REST API

Fetch a published event by its slug. The slug is at the end of its public link /e/your-event.

GET https://echoventra.vercel.app/api/v1/public/events/{slug}

The response contains event, ticketing, sessions, speakers, revision and updatedAt. Unknown details remain null. The materials list is still empty in this API version.

const response = await fetch(
  "https://echoventra.vercel.app/api/v1/public/events/your-event-slug",
  { cache: "no-store" }
);
if (response.status === 404) {
  // Event is missing or was no longer published.
}
if (response.ok) {
  const { event, sessions, speakers } = await response.json();
}

Example for your website server. Replace your-event-slug with the actual public slug; the API accepts only lowercase letters, digits, and hyphens.

For your assistant: MCP

Add the following address as a remote MCP server with Streamable HTTP. No API key is required.

https://echoventra.vercel.app/api/mcp

All three tools expect only { "slug": "your-event" }. Any website URLs and private account identifiers are not inputs.

"Read the published program of your-event with Echoventra and show the next talks. Mark missing times."

Supports the current MCP protocol 2026-07-28 as well as older Streamable HTTP clients in stateless mode. Setup and naming depend on the assistant used.