Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the BaladAPP Partner Integration 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%2Fcruzeirotickets.com.br%2Fcruzeirotickets-com-br" | shStep 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%2Fcruzeirotickets.com.br%2Fcruzeirotickets-com-br" | sh
jentic register # connects your agent to your Jentic One instanceJentic 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.
What an agent can do with BaladAPP Partner Integration API.
List subscription plans, add-ons, and benefits
Read subscriptions and the customers who hold them
Look up a customer's tickets, orders, and subscriptions
Browse event announcements and matches on sale
List sessions, tickets, and orders for an event
Patterns agents use BaladAPP Partner Integration API for, with concrete tasks.
★ Partner listing sync
Partner storefronts mirror the available plans and events. BaladAPP lists plans, add-ons, benefits, and the events on sale, so a partner system can keep its own listings aligned with what Cruzeiro is currently offering.
List the available subscription plans and the events on sale to refresh a partner's listings
Customer entitlement lookup
Support and loyalty tools need to see what a customer holds. The API returns a customer's subscriptions, tickets, and orders, so an assistant can confirm entitlements before answering a question.
Look up a customer and return their active subscriptions, tickets, and recent orders
Agent-driven event assistant
A fan-facing agent can answer what-is-on questions. Through Jentic, an agent resolves a request about upcoming matches into reading the event listings and their sessions and tickets.
Read the matches on sale and list their sessions and available tickets for a fan query
20 endpoints — baladapp is the partner-integration api behind cruzeiro's ticketing and subscription platform.
METHOD
PATH
DESCRIPTION
/planos
List subscription plans
/assinaturas
List subscriptions
/clientes/{cliente_id}/ingressos
List a customer's tickets
/anuncios
List event announcements on sale
/anuncios/{anuncio_id}/ingressos
List tickets for an event
/jogos
What agents get from Jentic-routed access to this vendor.
Setup
BaladAPP wiring is one partner token plus 20 read operations across plans, events, and orders. With Jentic One you install once, import them from the API Directory, and keep the token in one place.
Permission scoping
Resources such as plan id, customer id, and event id are path parameters, so you can scope an agent to specific reads, for example event and ticket lookups, while withholding customer data.
Credential isolation
The partner token is stored encrypted by your own Jentic One instance and injected when a call runs, so it never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents find the right BaladAPP read through Jentic's intent search, matching a request like listing tickets for an event to the matching endpoint.
Alternatives and complements available in the Jentic catalogue.
Specific to using BaladAPP Partner Integration API through Jentic.
How does the BaladAPP partner API authenticate?
Each request carries a partner token in the `X-INTEGRACAO-API-TOKEN` header, as declared in the spec. Jentic One stores that token and injects it at execution time.
Can I limit what my agent is allowed to do with BaladAPP?
Yes. Every operation is read-only, and you import only the ones an agent needs, so it can read event and ticket data while customer records stay out of scope.
What events does the API expose?
It exposes announcements and matches that are on sale, each with its sessions, tickets, and the orders placed against it.
Can the API sell tickets or create orders?
No. The partner interface is read-only: it reads plans, subscriptions, events, tickets, and orders but does not create or pay for them.
Is BaladAPP specific to Cruzeiro?
Yes. It is the partner-integration layer for Cruzeiro's ticketing and subscription platform, served from the Cruzeiro partner host.
GET STARTED
List matches on sale
/planos
List subscription plans
/assinaturas
List subscriptions
/clientes/{cliente_id}/ingressos
List a customer's tickets
/anuncios
List event announcements on sale
/anuncios/{anuncio_id}/ingressos
List tickets for an event
/jogos
List matches on sale
Know of an official OpenAPI document? Contribute it →
For Agents
Lets an AI agent read Cruzeiro BaladAPP subscription plans, subscriptions, customers, events, tickets, and orders with a partner token.
Use for: I need the list of available subscription plans, Show me a customer's active subscriptions, Which events are currently on sale?, List the tickets for this match
Not supported: Does not sell tickets, take payments, or create subscriptions: use it to read BaladAPP plans, events, tickets, and orders only.
BaladAPP is the partner-integration API behind Cruzeiro's ticketing and subscription platform. With a partner API token, an integration can read subscription plans, add-ons, and benefits, list subscriptions and the customers who hold them, browse event listings (announcements and matches) with their sessions and tickets, and retrieve the orders placed against each event. It gives partner systems read access to plans, events, tickets, and orders.
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
Base layer of spec validity and structural soundness.
Aggregated quality score from linter diagnostics, weighted by severity.
Percentage of `$ref` references that resolve successfully.
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
Structural correctness score based on schema issues using logarithmic dampening.
Clarity, completeness, and ingestion readiness for developers and tooling.
How richly the API is illustrated with examples.
Percentage of examples that conform to their schemas.
Percentage of operations with complete response definitions (success, client error, server error).
Health of API ingestion, bundling, and resolution within Jentic pipelines.
Semantic breadth, depth, and agent comprehension for AI systems.
Coverage of descriptions across API elements.
Coverage of RFC 9457 Problem Details for error responses.
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
Coverage of summaries across operations/tags/info.
Functional utility, complexity comfort, and AI orchestration readiness.
Agent comfort level based on API operational and structural complexity.
Trust, risk posture, and security compliance.
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
Findability, semantic richness, and reasoning readiness.
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>