Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the QuizAPI, 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%2Fquizapi.io%2Fquizapi" | 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%2Fquizapi.io%2Fquizapi" | 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 QuizAPI API.
Get API metadata
List quizzes
Access QuizAPI crm resources via REST API
Patterns agents use QuizAPI API for, with concrete tasks.
★ CRM Operations
Use the QuizAPI to perform crm operations programmatically. The API provides 3 endpoints covering core functionality including get API metadata, list quizzes, get questions.
Call GET /api/v1/metadata to get API metadata
GET STARTED
Automated Discovery Management
Automate discovery operations by combining multiple QuizAPI endpoints. Agents can list quizzes and then get questions in a single workflow.
Call GET /api/v1/quizzes to list quizzes, then verify the result
AI Agent Integration via Jentic
AI agents discover and call QuizAPI endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle bearer tokens manually.
Search Jentic for 'get API metadata', load the operation schema, and execute with Jentic-managed credentials
3 endpoints — access thousands of quiz questions across programming, science, and more.
METHOD
PATH
DESCRIPTION
/api/v1/metadata
Get API metadata
/api/v1/quizzes
List quizzes
/api/v1/questions
Get questions
/api/v1/metadata
Get API metadata
/api/v1/quizzes
List quizzes
/api/v1/questions
Get questions
What agents get from Jentic-routed access to this vendor.
Setup
Wiring QuizAPI by hand means learning its bearer auth, targeting the quizapi.io host, and handling paging and retries across its quiz and question reads yourself. Through Jentic you install once, import QuizAPI from the API Directory, store the token once, and your agent calls it.
Permission scoping
QuizAPI exposes read operations whose filters travel in the request parameters, so limit the agent to the operations it needs, such as listing questions or reading metadata. You choose which operations are allowed, so the agent reaches only the reads you list.
Credential isolation
Your QuizAPI token 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 'fetch quiz questions by category' or 'list available quizzes', and Jentic returns the matching QuizAPI operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Alternatives and complements available in the Jentic catalogue.
Specific to using QuizAPI API through Jentic.
What authentication does the QuizAPI use?
The QuizAPI uses a Bearer token in the Authorization header. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.
Can I get API metadata with the QuizAPI?
Yes. Use the GET /api/v1/metadata endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the QuizAPI?
Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.
How do I get API metadata through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'get API metadata'. Jentic returns the matching QuizAPI operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the QuizAPI have?
The QuizAPI exposes 3 endpoints covering discovery, quizzes, questions operations.
Can I limit what my agent is allowed to do with the QuizAPI?
Yes. Because you run Jentic One yourself, you decide which QuizAPI operations your agent may call and which credentials it may use. QuizAPI only exposes read operations, so you can allow just the calls you need, such as listing quizzes or fetching questions, while withholding metadata reads or any endpoint you do not want touched. Your own rules gate access, so the agent reaches only the reads you have explicitly permitted.
For Agents
Programmatically get API metadata, list quizzes. Covers 3 operations with bearer authentication.
Use for: I need to API metadata, I want to quizzes, Search for questions, I want to integrate QuizAPI into my workflow
Not supported: Does not handle payments, communications, or developer tools - use for crm only.
Access thousands of quiz questions across programming, science, and more. Browse by category, difficulty, and tags. Supports AI-powered question generation, embeddable widgets, leaderboards, and analytics. The API exposes 3 endpoints secured with bearer authentication.
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>