canonical: https://jentic.com/apis/inquizitv.com/inquizit

# Inquizitv Inquizit API

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.

## For AI agents

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

## Scope

Does not handle quiz creation, response capture, or scoring - use for Google-backed Inquizit sign-in only.

## Capabilities

- 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
- Bootstrap an authenticated Inquizit client without managing a separate password store
- Surface authentication failures distinctly from invalid Google tokens for client error handling

## Use cases

### 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.

Example prompt: 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.

Example prompt: 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.

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

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/api/user/authenticate` | Authenticate an Inquizit user with a Google ID token |

## Key resources

- **Authentication** — Single endpoint that exchanges a Google ID token for an Inquizit user session.

## Why Jentic

- **Setup:** Wiring Inquizit sign-in by hand means obtaining a Google ID token and posting it to the single authenticate endpoint on its App Engine host yourself. Through Jentic you install once, import the Inquizit API from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** The Inquizit API exposes a single sign-in operation that takes the Google ID token in the request body, so limit the agent to that one authenticate operation. You choose which operations are allowed, and no other endpoints exist to add here.
- **Credential handling:** Your Google ID token for Inquizit 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 'sign a user in to Inquizit', and Jentic returns the Inquizit authenticate operation with its input schema so the agent calls the right endpoint without browsing the docs site.

## Related APIs

- **ClassMarker API** — ClassMarker exposes a full quiz-and-assessment API rather than just an authentication endpoint.
- **Typeform API** — Typeform offers conversational quizzes and scored forms with a complete REST API.
- **SurveyMonkey API** — SurveyMonkey adds survey distribution and response analytics next to quiz authentication.

## FAQ

### 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 with Jentic One, the self-hosted execution layer.

### 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 your encrypted Jentic One instance 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.

### Can I limit what my agent is allowed to do with the Inquizit API?

Yes. Because Jentic One is self-hosted, you run your own instance and your own rules decide which operations and credentials the agent may use. The Inquizit API exposes only a single sign-in operation, POST `/api/user/authenticate`, which exchanges a Google ID token for an Inquizit session, so you can restrict the agent to just that one authenticate operation. Your Google ID token is held in your instance and injected only at execution time, so the agent can trigger the sign-in call without ever seeing the raw credential.