Inquizitv Inquizit API

Name: Inquizit API
Brand: Inquizit API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentIdentity AuthAuthenticationnone1 EndpointsREST

For Agents

Authenticate a user into Inquizit by exchanging a verified Google identity token for an Inquizit session.

Install Jentic One Beta

Connect the Inquizit API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Inquizit 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://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | 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 Inquizit API.

Exchange a Google ID token for an Inquizit user session via /api/user/authenticate

Federate sign-in for video quiz creators using their existing Google accounts

Verify that a Google-authenticated user has an active Inquizit account

GET STARTED

Start building with Inquizit API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI specification for Inquizit API, keeping it validated and agent-ready. The Inquizit API is a single-endpoint authentication service that lets the Inquizit video quiz and assessment platform sign users in using Google credentials. It accepts a Google ID token and exchanges it for an Inquizit session, providing a thin federated login layer for quiz creators and respondents. The surface area is intentionally narrow and is intended to be embedded into Inquizit clients rather than to expose quiz content directly.

Use Cases

Patterns agents use Inquizit API for, with concrete tasks.

★ Google Federated Login for Inquizit

Embed Inquizit into a learning portal or quiz hosting site by accepting Google sign-in and exchanging the resulting Google ID token for an Inquizit session through /api/user/authenticate. The endpoint validates the token server-side so the client never handles raw Inquizit credentials, and the integration takes only a few hours once a Google OAuth client is configured.

POST a verified Google ID token to /api/user/authenticate and return the Inquizit session response to the calling client.

Single Sign-On for Quiz Authors

Let teachers and trainers reach the Inquizit authoring tools without a separate password by accepting their school or workplace Google identity and routing the verified token through the Inquizit authenticate endpoint. This avoids a parallel credential database while still tying every quiz to a real Inquizit user record.

Accept a Google sign-in callback, forward the ID token to /api/user/authenticate, and store the returned session for subsequent authoring requests.

AI Agent Sign-In Bootstrap via Jentic

An AI agent that needs to act on behalf of an Inquizit user can call the authenticate endpoint through Jentic to obtain a session, with the Google ID token retrieved from a Jentic-managed credential. Jentic isolates the token from the agent's prompt context, so the agent only sees the structured authentication response.

Through Jentic, call inquizit_authenticate_user with the stored Google ID token and return the Inquizit session identifier to the caller.

Key Endpoints

1 endpoints — jentic publishes the only available openapi specification for inquizit api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/api/user/authenticate

Authenticate an Inquizit user with a Google ID token

POST

/api/user/authenticate

Authenticate an Inquizit user with a Google ID token

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Inquizit authentication relies on a Google ID token. Through Jentic, that token is stored in the encrypted Jentic vault and injected into the request at execution time, so the agent never sees raw Google credentials.

Intent-based discovery

Agents search Jentic for an intent like 'sign a user in to Inquizit' and Jentic returns the inquizit_authenticate_user operation with its input schema, removing any need to read the Inquizit docs site.

Time to first call

Direct integration: about half a day to handle Google OAuth, token verification, and Inquizit response parsing. Through Jentic: under 30 minutes — search, load, execute.

FAQs

Specific to using Inquizit API through Jentic.

Why is there no official OpenAPI spec for Inquizit API?

Inquizit does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Inquizit API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the Inquizit API use?

The Inquizit API itself does not declare a security scheme on /api/user/authenticate; instead, the request body must contain a valid Google-issued ID token, which Inquizit verifies server-side. When called through Jentic, the Google ID token is held in the encrypted Jentic vault and never enters the agent's prompt context.

Can I create or fetch quizzes with the Inquizit API?

Not through this spec. The Inquizit API published here exposes only /api/user/authenticate. Quiz creation, response collection, and scoring are handled inside the Inquizit web product, not via this public endpoint.

What are the rate limits for the Inquizit API?

The OpenAPI specification does not document explicit rate limits for the authenticate endpoint. Treat it as an interactive sign-in operation, retry on transient 5xx errors with backoff, and avoid hammering it from background jobs since each call corresponds to a user session exchange.

How do I sign a user into Inquizit through Jentic?

Run pip install jentic, then have the agent call the search-load-execute flow with the query 'sign a user in to Inquizit with Google'. Jentic returns the inquizit_authenticate_user operation bound to POST /api/user/authenticate; the agent supplies the Google ID token reference and receives the Inquizit session response.

Is the Inquizit API free to use?

Inquizit does not publish public pricing for direct API access. The endpoint is intended for first-party Inquizit clients, so commercial use typically requires coordinating with Inquizit directly; Jentic only handles the call mechanics, not the commercial agreement.