Install Jentic One Beta

Connect the Weezevent API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Weezevent 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%2Fweezevent.com%2Fweezevent" | 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%2Fweezevent.com%2Fweezevent" | 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 Weezevent API.

Get access token

List event participants

Create/update participants

Partial update participants

Delete participants

Use Cases

GET STARTED

Start building with Weezevent API

Explore with Jentic One

View OpenAPI Document

Automated Authentication Management

Automate authentication operations by combining multiple Weezevent API endpoints. Agents can list event participants and then get participant in a single workflow.

Call GET /evenement/{id_event}/participants to list event participants, then verify the result

AI Agent Integration via Jentic

AI agents discover and call Weezevent API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle apiKey tokens manually.

Search Jentic for 'get access token', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

18 endpoints — weezevent event management api for managing participants, checkpoints, partners, forms, widgets, promocodes, and webhooks.

METHOD

PATH

DESCRIPTION

POST

/auth/access_token

Get access token

GET

/evenement/{id_event}/participants

List event participants

GET

/evenement/{id_event}/participants/{id_participant}

Get participant

POST

/participants

Create/update participants

PATCH

/participants

Partial update participants

DELETE

/participants

Delete participants

POST

/checkpoints

Create/update checkpoints

GET

/checkpoints

List checkpoints

POST

/auth/access_token

Get access token

GET

/evenement/{id_event}/participants

List event participants

GET

/evenement/{id_event}/participants/{id_participant}

Get participant

POST

/participants

Create/update participants

PATCH

/participants

Partial update participants

DELETE

/participants

Delete participants

POST

/checkpoints

Create/update checkpoints

GET

/checkpoints

List checkpoints

Why Jentic?

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

Setup

Wiring the Weezevent API by hand means calling its /auth/access_token endpoint, then passing the api_key query parameter across the participant and checkpoint calls, and handling retries yourself. Through Jentic you install once, import Weezevent from the API Directory, store the API key once, and your agent calls it.

Permission scoping

Weezevent puts the event id in the URL path (/evenement/{id_event}/participants), so a rule can pin your agent to one event: it can read participants for that event and nothing else. You choose the operations it may call, so participant deletion or update is not included unless you add them.

Credential isolation

Your Weezevent API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'list participants for an event' or 'check in a participant', and Jentic returns the matching Weezevent operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Weezevent API through Jentic.

What authentication does the Weezevent API use?

The Weezevent API uses an API key passed in the `api_key` query. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

Can I get access token with the Weezevent API?

Yes. Use the POST /auth/access_token endpoint. The API returns structured JSON responses that agents can parse and act on directly.

What are the rate limits for the Weezevent API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

How do I get access token through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'get access token'. Jentic returns the matching Weezevent API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

How many endpoints does the Weezevent API have?

The Weezevent API exposes 18 endpoints covering authentication, checkpoints, participants operations.

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

Yes. Because you run Jentic One yourself, your own rules decide which Weezevent operations and credentials the agent may use. Since the event id sits in the URL path (/evenement/{id_event}/participants), you can pin the agent to a single event so it reads that event's participants and nothing else. You choose the operations it may call, so participant deletion or update via /participants stays off limits unless you explicitly add it.

Weezevent API

AI ReadinessFoundational (D+)49/100

See full scorecard

Official vendor OpenAPI document · agent-readyDeveloper ToolsSource ControlapiKey18 EndpointsREST

For Agents

Programmatically get access token, list event participants. Covers 18 operations with apiKey authentication.

Use for: I need to access token, I want to event participants, Search for participant, Find all create/update participants

Not supported: Does not handle payments, communications, or crm - use for developer tools only.

Weezevent event management API for managing participants, checkpoints, partners, forms, widgets, promocodes, and webhooks. The API exposes 18 endpoints secured with apiKey authentication.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A-Signals: 4

98%

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).

17%

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: B-Signals: 4

Example Density

How richly the API is illustrated with examples.

100%

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: CSignals: 4

53%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

100%

OperationId Quality

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

67%

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: FSignals: 1

15%

Authentication Strength

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

100

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: A+Signals: 1

100%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Weezevent API to your agent

Capabilities

Use Cases

Start building with Weezevent API

Key Endpoints

Why Jentic?

Related APIs

FAQs

Weezevent API

Jentic AI Readiness Score

Weezevent 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