canonical: https://jentic.com/apis/citoapi.com/citoapi # Citoapi Cito UFC API 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. ## For AI 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. ## Scope Does not cover other combat sports, place bets, or settle wagers. Use for reading UFC fighter, event, bout, ranking, odds, and live data only. ## Capabilities - 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 ## Use cases ### 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. Example prompt: 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. Example prompt: 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. Example prompt: Search Jentic for 'ufc fighter statistics', load the operation schema, and read the fighter with Jentic-injected credentials ## Key endpoints | 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 | ## Key resources - **Fighters** — List fighters and read a fighter's profile, career statistics, and fight history - **Events** — List events and read an event's fight card and odds, including upcoming and recent events - **Bouts** — List bouts and read per-fighter totals, round-by-round statistics, and odds - **Rankings and Live** — Read divisional ranking boards and follow live fight-night state ## AI readiness 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. - **Score:** 61 / 100 - **Maturity:** AI-Aware - **Dimensions:** - Foundational Compliance: 77 / 100 - Developer Experience & Jentic Compatibility: 62 / 100 - AI-Readiness & Agent Experience: 45 / 100 - Agent Usability: 94 / 100 - Security: 50 / 100 - AI Discoverability: 70 / 100 - **View full report:** https://jentic.com/apis/citoapi.com/citoapi/scorecard - **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/ - **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview ### Score it yourself Every API in the directory is allowlisted, so you can re-score it with no key required. - **Score your own API:** https://jentic.com/scorecard.md - **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md ```sh npx @jentic/api-scorecard-cli score ``` ## Why Jentic - **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 handling:** 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. - **Discovery method:** 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. ## Related APIs - **API-Sports** — Multi-sport data across many leagues, versus Cito's UFC-only fighter and bout depth. - **The Odds API** — Broad betting odds across sports and bookmakers to pair with Cito's UFC data. - **SportsData.io** — Commercial sports stats and fantasy data, versus Cito's self-serve UFC statistics. ## FAQ ### 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.