Install Jentic One Beta

Connect the Eventee Public API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Eventee Public API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Feventee.com%2Feventee" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Feventee.com%2Feventee" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Eventee Public API.

Create halls, lectures, and breaks to lay out the event schedule

Add and update speakers for the event

Invite registrations and attendees and check attendees in

Manage tracks and labels that group sessions

Add and update event partners

GET STARTED

Start building with Eventee Public API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Eventee Public API for, with concrete tasks.

★ Agent-Driven Agenda Building

An AI agent connected through Jentic assembles a conference agenda by creating halls, adding lectures to them, and inserting breaks between sessions. Because Eventee models each schedule element as its own operation, the agent lays out a full day of programming and attaches speakers to the sessions it created.

Create a hall, add two lectures to it, and attach a speaker to each lecture

Attendee Onboarding

An events team onboards attendees by inviting registrations, inviting attendees, and checking them in on arrival. The Eventee API exposes invite and check-in operations and reads back participants, so an agent drives registration through to door check-in and reconciles who actually attended.

Invite a batch of attendees, then mark one as checked in and confirm it in the participants list

Speaker and Partner Management

A conference organiser keeps speakers, tracks, and partners current as the programme changes. The API creates and updates speakers, tracks, and partners, letting an agent add a late-addition speaker, slot their talk into a track, and register a new sponsor as a partner.

Add a new speaker, assign their session to a track, and register a new partner for the event

Key Endpoints

30 endpoints — the eventee public api builds and maintains a conference agenda and its attendees on the eventee event platform.

METHOD

PATH

DESCRIPTION

GET

/content

Get all event content

POST

/hall

Create a new hall

POST

/lecture

Create a new lecture or workshop

POST

/speaker

Create a new speaker

PUT

/attendee/invite

Invite attendees

GET

/registrations

Get all registrations

GET

/participants

Get all participants

GET

/partners

Get all partners

GET

/content

Get all event content

POST

/hall

Create a new hall

POST

/lecture

Create a new lecture or workshop

POST

/speaker

Create a new speaker

PUT

/attendee/invite

Invite attendees

GET

/registrations

Get all registrations

GET

/participants

Get all participants

GET

/partners

Get all partners

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring the Eventee Public API by hand means generating a token in the admin console and formatting the Authorization header as a bearer value on every call. Through Jentic you install once, import the API from the API Directory, store the token once, and your agent calls the agenda and attendee operations.

Permission scoping

Eventee carries the hall, lecture, and speaker ids in the URL path, so a rule can scope your agent to operations on specific sessions. You choose the operations it may call, so destructive ones like deleting a lecture or speaker are not included unless you add them.

Credential isolation

Your Eventee token is held by your own Jentic One instance, encrypted, and injected into the Authorization header at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'create a lecture' or 'invite attendees', and Jentic returns the matching Eventee operation with its input schema so the agent builds the agenda or manages attendees correctly.

FAQs

Specific to using Eventee Public API through Jentic.

What authentication does the Eventee Public API use?

The Eventee Public API authenticates with an API token sent in the Authorization header in the form `Bearer YOUR_API_KEY`, per its OpenAPI spec, and you generate the token in the Eventee admin settings. Through Jentic the token is held by your own Jentic One instance and attached at execution time, so it never appears in your agent's prompt or logs.

Can I build a conference agenda with the Eventee Public API?

Yes. The API creates halls, lectures, workshops, and breaks, adds speakers, and manages tracks that group sessions. Your agent can lay out a schedule and attach speakers to the sessions it created, then adjust the programme as it changes.

What are the rate limits for the Eventee Public API?

The OpenAPI spec does not specify rate limits. Check the Eventee documentation at https://eventee.com for the current limits before running bulk agenda or attendee operations.

Is there an Eventee MCP server?

You do not need an MCP server to give your agent the Eventee Public API. Jentic connects it directly from the API Directory: import it, store your token once, and your agent discovers the agenda and attendee operations it needs on demand without loading an extra server's tool definitions into its context.

Can I limit what my agent is allowed to do with the Eventee Public API?

Yes. Eventee carries the hall, lecture, and speaker ids in the URL path, so a rule can scope your agent to operations on specific sessions. You choose the operations it may call, so destructive ones like deleting a lecture or speaker stay out unless you add them, and every call it makes is logged.

How do I build an Eventee agenda through Jentic?

Install the Jentic One command line with `curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh`, then add the Eventee Public API from the Jentic directory and search by intent such as 'create a lecture in a hall'. Jentic returns the matching operation with its input schema so your agent builds a valid request. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Eventee Public API

AI ReadinessFoundational (C-)52/100

See full scorecard

Community OpenAPI document · agent-readyProductivityCalendar SchedulingapiKey30 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Build a conference agenda on Eventee: create halls, lectures, and breaks, manage speakers, tracks, and partners, and invite, check in, and read back attendees.

Use for: Create a new lecture in a specific hall, Add a speaker to the event agenda, Invite a list of attendees to the event, Check in an attendee at the door

Not supported: Does not sell tickets, process payments, or stream sessions. Use for managing conference agenda, speakers, and attendees only.

The Eventee Public API builds and maintains a conference agenda and its attendees on the Eventee event platform. Your agent creates halls, lectures, and breaks to lay out the schedule, adds and updates speakers and partners, and manages tracks that group sessions. It also handles the audience side, inviting registrations and attendees, checking attendees in, and reading back participants, content, and reviews for the event.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A+Signals: 4

97%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

100%

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

100%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: A-Signals: 4

67%

Example Density

How richly the API is illustrated with examples.

99%

Example Validity

Percentage of examples that conform to their schemas.

50%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: FSignals: 4

47%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

57%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: C-Signals: 1

50%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: BSignals: 1

64%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Eventee Public API to your agent

Capabilities

Start building with Eventee Public API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Eventee Public API

Jentic AI Readiness Score

Eventee Public API

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness