Install Jentic One Beta

Connect the LeBillet - API de Assentos to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the LeBillet - API de Assentos, 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%2Flebillet.eu%2Flebillet" | 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%2Flebillet.eu%2Flebillet" | 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 LeBillet - API de Assentos API.

List the seats still available for a specific event

Reserve a chosen seat by its id for an event

Activate a reserved seat with the buyer's payment totals and contact details

Use Cases

Patterns agents use LeBillet - API de Assentos API for, with concrete tasks.

★ Book an event seat with an AI agent

An AI agent integration created through Jentic walks a buyer through choosing a seat. The LeBillet API lists the available seats for an event, reserves the one the buyer picks by its id, and activates it once payment totals and contact details are known, so the agent completes a seat booking end to end.

GET STARTED

Start building with LeBillet - API de Assentos API

Explore with Jentic One

View OpenAPI Document

Show live seat availability

A storefront needs to show which seats are still open for an event. The LeBillet API returns the available seats for an event id, so an automation can render a live availability map and avoid offering seats that are already taken.

Retrieve the available seats for an event id and present them as a list

Confirm a reservation after payment

Once a buyer pays, the held seat must be confirmed with the transaction details. The LeBillet API activates a reserved seat using its code and the payment totals including tax, discount, and the total value, along with the buyer's email, so an agent finalizes the sale against the correct seat.

Activate a reserved seat with its code, payment totals, and the buyer's email

Key Endpoints

3 endpoints — the lebillet api lists, reserves, and activates event seating.

METHOD

PATH

DESCRIPTION

GET

/api_seats/seats/{id_event}

List available seats for an event

POST

/api_seats/reserveSeat

Reserve a seat

POST

/api_seats/activeSeat

Activate a reserved seat

GET

/api_seats/seats/{id_event}

List available seats for an event

POST

/api_seats/reserveSeat

Reserve a seat

POST

/api_seats/activeSeat

Activate a reserved seat

Why Jentic?

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

Setup

Wiring LeBillet by hand means setting up HTTP basic auth and tracking seat and event ids across the reservation and activation calls. Through Jentic you install once, import LeBillet from the API Directory, store the credential once, and your agent calls it.

Permission scoping

LeBillet puts the event id in the URL path for listing seats, so a rule can limit your agent to reading availability for one event. Reservation and activation carry the ids in the request body, so rules bound which operations your agent may call, such as listing and reserving while leaving activation out unless you add it.

Credential isolation

Your LeBillet credential 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 'reserve a seat' or 'list available seats', and Jentic returns the matching LeBillet operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using LeBillet - API de Assentos API through Jentic.

What authentication does the LeBillet API use?

The LeBillet API authenticates with HTTP basic auth, per its OpenAPI spec. Through Jentic the credential is stored encrypted by your own Jentic One instance and injected at call time, so it never reaches the agent's prompt or logs.

Can I reserve a seat with the LeBillet API?

Yes. The reserve operation holds a seat by its id for an event, and the activate operation confirms that reservation with the buyer's payment totals and contact details, so an agent can take a seat from available to confirmed.

What details are needed to activate a seat?

Activation requires the seat and event ids, a code, the payment values for product, tax, discount, and total, and the buyer's email and cell number, all sent in the request body. Supplying these finalizes the reservation against the correct seat.

How do I book an event seat through Jentic?

Install Jentic One on your own infrastructure with `curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh`, then import the LeBillet API from the API Directory and search for 'reserve an event seat'. Store the credential once and your agent can list, reserve, and activate seats. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Is there a LeBillet MCP server?

You don't need an MCP server to give your agent the LeBillet API. Jentic connects it directly from the API Directory: import it, store your credential once, and your agent calls it, with each operation discovered on demand instead of loaded into the agent's context.

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

Yes. The seat listing operation puts the event id in the URL path, so a rule can let the agent read availability and reserve seats while leaving activation out, so it cannot finalize a sale on its own. Every action it takes is recorded in an audit log.

LeBillet - API de Assentos

AI ReadinessNon-Ready (F)30/100

See full scorecard

Community OpenAPI document · agent-readyE CommerceOrder Managementbasic3 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

List available seats for an event, reserve a seat by id, and activate the reservation with the buyer's payment and contact details.

Use for: Show the available seats for an event, Reserve a specific seat for a customer, Activate a seat reservation after payment, Check which seats are still open

Not supported: Does not handle event creation, catalog browsing, or refunds. Use for listing, reserving, and activating event seats only.

The LeBillet API lists, reserves, and activates event seating. A caller can see which seats are available for a specific event, hold a chosen seat by its id, and then activate that reservation with the buyer's payment totals and contact details. Requests are authenticated with HTTP basic auth.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

100

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A+Signals: 4

99%

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.

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

20%

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.

50%

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

10%

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

62%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the LeBillet - API de Assentos to your agent

Capabilities

Use Cases

Start building with LeBillet - API de Assentos API

Key Endpoints

Why Jentic?

Related APIs

FAQs

LeBillet - API de Assentos

Jentic AI Readiness Score

LeBillet - API de Assentos

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