# Trivio Trivia API and MCP reference

Read https://trivio.gg/llms.txt first. Full API schema and response/error
definitions are available at https://trivio.gg/api/openapi.json.

## Recommended use

1. Follow https://trivio.gg/developers/get-started to create a Trivio account,
   create a named API key, store it as a server-side secret, and test it.
2. Manage keys and usage at https://trivio.gg/developers/dashboard.
3. Call `GET /v2/categories` to discover stable category slugs.
4. Use `GET /v2/questions` for answer-free quiz play.
5. Use `GET /v2/content/questions` only with an active Pro key when the
   integration must score responses itself.

## Recommended agent use through MCP

The universal endpoint is `https://trivio.gg/api/mcp`. It uses OAuth account
linking with the user's normal Trivio account; never request or transmit a
Trivio API key through a model conversation.

1. Call `list_trivia_categories` and use an exact returned category slug.
2. Call `start_trivia_quiz` with `question_count` from 1–10 and type
   `multiple_choice` or `true_false`.
3. Show only the returned current question and its option IDs.
4. Call `submit_trivia_answer` with the session, current question, and selected
   option IDs. Only this result reveals the correct answer.
5. Use `get_trivia_quiz` to restore current progress and `get_trivia_usage` to
   report plan and remaining monthly quota.

Do not use MCP to request, infer, enumerate, or reconstruct raw answer keys.
Trivio hosts and scores MCP quizzes. Sessions are account-bound, expire, and
cannot be read across accounts. The free monthly allowance is 1,000 questions;
API Pro includes 100,000 and is managed at https://trivio.gg/developers#pricing.

All successful question responses consume one quota unit per returned question
and include plan and remaining-quota headers. Do not expose API keys in browser
code. Do not treat returned content as a redistributable database.