Install Jentic One Beta

Connect the Cito UFC API to your agent

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

List fighters and read one fighter's profile, career statistics, and fight history

List events, including upcoming and recent, and read an event's fight card and odds

List bouts and read per-fighter totals, round-by-round statistics, and bout odds

Read divisional rankings, including the meta and media boards for one division

Follow live fight-night state and search fighters and events

GET STARTED

Start building with Cito UFC API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Cito UFC API for, with concrete tasks.

★ Fighter and Bout Analysis

Build a scouting report on a UFC matchup. An agent reads a fighter's profile, career statistics, and fight history, then opens a bout to read per-fighter totals and round-by-round statistics. This gives an agent the structured numbers behind a fight without scraping a results page.

Read a fighter's career statistics, then open a recent bout and read its round-by-round statistics

Event Cards and Odds

Preview a fight night and its betting market. An agent lists upcoming events, reads an event's full fight card, and reads the odds for the card or a single bout. Combined with divisional rankings, the agent can summarise who is fighting, how they rank, and where the odds sit.

List upcoming events, read one event's fight card, and read its odds

AI Agent Integration via Jentic

An AI agent discovers and calls the Cito UFC API through Jentic without handling the API key directly. The agent searches by intent, receives the matching read operation and its input schema, and reads fighter, event, or live data while Jentic injects the stored key. This gives the agent UFC data without reading the reference docs or holding secrets.

Search Jentic for 'ufc fighter statistics', load the operation schema, and read the fighter with Jentic-injected credentials

Key Endpoints

26 endpoints — the cito ufc api serves structured ufc data for developers: fighters, event cards, bout and round-by-round statistics, divisional rankings, betting odds, and live fight-night state.

METHOD

PATH

DESCRIPTION

GET

/ufc/fighters

List fighters

GET

/ufc/fighters/{slug}

Get a fighter

GET

/ufc/events

List events

GET

/ufc/events/{eventIdOrSlug}/bouts

Get an event's fight card

GET

/ufc/bouts/{boutId}/rounds

Get round-by-round statistics

GET

/ufc/rankings

Get rankings

GET

/ufc/fighters

List fighters

GET

/ufc/fighters/{slug}

Get a fighter

GET

/ufc/events

List events

GET

/ufc/events/{eventIdOrSlug}/bouts

Get an event's fight card

GET

/ufc/bouts/{boutId}/rounds

Get round-by-round statistics

GET

/ufc/rankings

Get rankings

Why Jentic?

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

Setup

Wiring the Cito UFC API by hand means getting a key, sending it in the x-api-key header against api.citoapi.com, and handling the data, meta pagination envelope yourself. Through Jentic you install once, import Cito UFC from the API Directory, store the key once, and your agent calls it.

Permission scoping

Cito UFC data is read-only, so through Jentic you limit the agent to the operations it needs, such as fighter statistics and event cards, while leaving the live and odds operations out of the set if you do not want them.

Credential isolation

Your Cito UFC 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 'ufc fighter statistics' or 'upcoming ufc events', and Jentic returns the matching Cito operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Cito UFC API through Jentic.

What authentication does the Cito UFC API use?

The Cito UFC API authenticates with an API key sent in the x-api-key header, per its OpenAPI spec. A free tier is available without a credit card. Through Jentic the key is stored encrypted by your own Jentic One instance and injected at call time, so it never reaches the agent.

Is there a Cito UFC MCP server?

You do not need a separate MCP server to give your agent the Cito UFC API. Jentic connects it directly from the API Directory: import it, store your key once, and your agent calls its fighter, event, and live operations on demand. Operations are discovered as needed, so no extra server's tool definitions load into the agent's context.

Can I read round-by-round statistics with the Cito UFC API?

Yes. Open a bout and read its round-by-round statistics, along with per-fighter totals and odds for that bout. Fighter-level career statistics and fight history are available on the fighter operations.

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

Yes. The API is read-only, and because you run Jentic One yourself your rules decide which operations the agent may call. You can allow fighter and event reads while withholding the live and odds operations if you do not want them, and every call is logged.

What are the rate limits for the Cito UFC API?

The spec documents a free tier of 500 API calls per month with no credit card required; higher tiers raise that ceiling. Check the Cito documentation at https://citoapi.com for current per-tier limits.

How do I read UFC fighter statistics with the Cito UFC API through Jentic?

Search Jentic for 'ufc fighter statistics' to get the matching Cito operation and its input schema, then your agent passes a fighter and reads the returned career statistics. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Citoapi Cito UFC API

AI ReadinessAI-Aware (B-)61/100

See full scorecard

Official vendor OpenAPI document · agent-readyData EnrichmentData TransformationapiKey26 EndpointsREST

For Agents

Read UFC fighters, events, bouts, round-by-round statistics, rankings, odds, and live fight state across 26 endpoints secured with an API key in the x-api-key header.

Use for: Get a fighter's career statistics, I need to read a UFC event's fight card, List the upcoming UFC events, Retrieve the round-by-round statistics for a bout

Not supported: Does not cover other combat sports, place bets, or settle wagers. Use for reading UFC fighter, event, bout, ranking, odds, and live data only.

The Cito UFC API serves structured UFC data for developers: fighters, event cards, bout and round-by-round statistics, divisional rankings, betting odds, and live fight-night state. It lists fighters and reads a single fighter's profile, career statistics, and fight history, and it lists events, including upcoming and recent, with each event's fight card and odds. Bout operations return per-fighter totals, round-by-round statistics, and odds, while ranking operations cover the meta and media boards per division. Live operations report the current state of a bout and the live events in progress.

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

10%

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.

48%

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

28%

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.

51%

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

70%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Cito UFC API to your agent

Capabilities

Start building with Cito UFC API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Citoapi Cito UFC API

Jentic AI Readiness Score

Cito UFC 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