canonical: https://jentic.com/apis/mario-kart-tour-api.herokuapp.com/mario-kart-tour # Mario Kart Tour API The Mario Kart Tour API serves reference data for the Mario Kart Tour game: the drivers, karts, gliders, and courses that appear in it. A root endpoint describes the service, list endpoints return each collection, and a by-id endpoint returns a single driver, kart, glider, or course. Responses are read-only game data, so the API is a lookup source rather than a way to change anything in the game. ## For AI agents Look up Mario Kart Tour reference data: list drivers, karts, gliders, and courses, or fetch a single one by its id. ## Scope Serves read-only reference data for Mario Kart Tour only. Does not track player accounts, matches, or scores, and cannot change anything in the game. ## Capabilities - Read the root endpoint that describes the service and its collections - List every driver in Mario Kart Tour - Fetch a single driver by its id - List karts and gliders, or fetch one by its id - List every course in the game - Fetch a single course by its id ## Use cases ### Agent Game Data Lookup A chatbot answering Mario Kart Tour questions can pull the canonical list of drivers or courses on demand rather than relying on stale memorized data. The agent calls the relevant list endpoint, reads back the collection, and answers with current names and attributes, so a question like 'which drivers are in the game' is grounded in the live reference data. Example prompt: List the drivers and return their names and attributes for a user's question ### Companion App Content A companion app or agent building a stat page can assemble driver, kart, glider, and course details in one pass. It lists each collection, then fetches individual records by id for the ones a user selects, so the app shows accurate per-item detail without maintaining its own copy of the game data. Example prompt: List karts and gliders, then fetch the selected items by id to show their details ### Course Reference Bot A bot that quizzes players or plans tournaments can look up the full course list and pull one course at a time. It lists courses, then fetches a chosen course by its id, so the bot works from the authoritative course set rather than a hand-maintained list. Example prompt: List courses and fetch a chosen course by id to show its details ## Key endpoints | Method | Path | Description | | --- | --- | --- | | GET | `/api/drivers` | List all drivers | | GET | `/api/drivers/{driverId}` | Get a driver by id | | GET | `/api/karts` | List all karts | | GET | `/api/gliders` | List all gliders | | GET | `/api/courses` | List all courses | | GET | `/api/courses/{courseId}` | Get a course by id | ## Key resources - **Drivers** — The list of drivers and a by-id endpoint for a single driver - **Karts** — The list of karts and a by-id endpoint for a single kart - **Gliders** — The list of gliders and a by-id endpoint for a single glider - **Courses** — The list of courses and a by-id endpoint for a single course ## Why Jentic - **Setup:** Wiring the Mario Kart Tour API by hand still means mapping its nine endpoints and handling the by-id versus list response shapes. Through Jentic you install once, import it from the API Directory, and your agent calls the drivers, karts, gliders, and courses operations. - **Permission scoping:** The API's operations are read-only lookups per item type, so a rule can allow only the collections your agent needs, such as drivers and courses, and leave the others out of scope. You decide which operations are in scope, and every call is logged. - **Credential handling:** The Mario Kart Tour API needs no key or token, so there is nothing to hold. Your agent's calls still route through your own Jentic One instance, which logs each request even though no secret is involved. - **Discovery method:** Agents search Jentic by intent such as 'list Mario Kart Tour courses' or 'get a driver by id', and Jentic returns the matching operation with its response schema so the agent calls the right endpoint without reading the reference docs. ## Related APIs - **RAWG** — Video game database with details, screenshots, and ratings across platforms. - **IGDB** — Internet Game Database with metadata on games, companies, and genres. - **PUBG** — Match, player, and telemetry data for the PUBG game. ## FAQ ### What authentication does the Mario Kart Tour API use? The Mario Kart Tour API needs no authentication: its OpenAPI spec defines no security schemes, so the read-only game data endpoints are open. Through Jentic the calls still route through your own self-hosted instance, where each request is logged even though no key is involved. ### Can I list drivers and fetch one by its id with the Mario Kart Tour API? Yes. Call the drivers list endpoint to get every driver, then call the by-id endpoint with a driver id to get a single record. The same list-then-fetch pattern works for karts, gliders, and courses. ### What are the rate limits for the Mario Kart Tour API? The OpenAPI spec for the Mario Kart Tour API does not define rate limits. Because the service is a community-hosted app, keep request volume modest and cache results where you can. ### Is there a Mario Kart Tour API MCP server? You don't need an MCP server to give your agent the Mario Kart Tour API. Jentic connects it directly from the API Directory: import it and your agent calls the drivers, karts, gliders, and courses operations without another server's tool definitions loaded into its context. ### Can I limit which Mario Kart Tour operations my agent can call? Yes. Even though the endpoints are open, a rule can allow only the operations you want, such as listing drivers and courses, and leave the rest out of scope. You decide which operations are in scope, and every call the agent makes is logged. ### How do I list Mario Kart Tour drivers through Jentic? Search Jentic with an intent like 'list Mario Kart Tour drivers', and it returns the drivers list operation with its response schema so the agent calls it and reads back the collection. To run it on your own infrastructure, install Jentic One from its GitHub repo.