Install Jentic One Beta

Connect the Questmate API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Questmate 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://jentic.com/install.sh?src=apis&api=%2Fapis%2Fquestmate.com%2Fquestmate" | sh

Step 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%2Fquestmate.com%2Fquestmate" | 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 Questmate API.

Create a Quest from an existing template with a name, due date, and run schedule

Assign a Quest to users and list the assignments open for a person

Start a Quest run, update its item instances, and submit it for review

Add reviewers to a Quest and record reviews on submitted Quest instances

Export a Quest's runs as CSV or a single run as PDF for a date range

GET STARTED

Start building with Questmate API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Questmate API for, with concrete tasks.

★ Agent-run checklist dispatch through Jentic

An AI agent handling operations requests can create and dispatch Questmate checklists on demand. Through Jentic the agent searches for 'start a checklist run', receives the matching Questmate operation with its input schema, and calls POST /quests/{questIdOrFormPrototypeId}/start with the bearer token injected at execution time. The agent then reads the run back to confirm it started, without the developer wiring Questmate auth by hand.

Start a run of an existing Quest with POST /quests/{questIdOrFormPrototypeId}/start, then fetch the resulting run with GET /questInstances/{questInstanceId} to confirm its status

Assigning recurring inspections

Facilities and field teams use Questmate Quests as repeatable inspection checklists. A Quest is created from a template with POST /quests, which requires a templateId and accepts a dueAt, a runSchedule, and a runScheduleTimezone. Assignments are added per Quest with userIds, so each inspector sees the checklist in their assignment list and the Quest's scheduled starts can be listed or removed later.

Create a Quest from templateId 'tmpl_123' with a weekly runSchedule in the Europe/Dublin runScheduleTimezone, then assign it to two userIds with POST /quests/{id}/assignments

Review and sign-off of submitted work

Compliance processes often need a second person to approve a completed checklist. Questmate lets a Quest carry reviewers, added with POST /quests/{id}/reviewers, and a reviewer records a decision on a submitted run with POST /questInstances/{questInstanceId}/reviews. Runs are submitted with POST /questInstances/{id}/submit, so the full submit-and-review loop is available over the API.

Submit a completed Quest instance with POST /questInstances/{id}/submit, then add a review on it with POST /questInstances/{questInstanceId}/reviews

Exporting audit records

Auditors usually want completed checklists as files rather than live records. Questmate exports a Quest's runs as CSV through GET /quests/{questId}/runs/export, filtered by startDate, endDate, and archived, and as a multi-page PDF through the matching /pdf route. A single run exports as PDF through GET /questInstances/{questInstanceId}/export/pdf with a pageSize option.

Export all runs of a Quest between 2026-10-01 and 2026-10-31 as CSV with GET /quests/{questId}/runs/export using startDate and endDate

Key Endpoints

74 endpoints — the questmate api runs checklist and form workflows called quests, built from reusable templates and assigned to people in a workspace.

METHOD

PATH

DESCRIPTION

POST

/quests

Create a Quest from a template

POST

/quests/{questIdOrFormPrototypeId}/start

Start a Quest run

GET

/quests/{questId}/runs

List runs of a Quest

POST

/quests/{id}/assignments

Assign a Quest to users

POST

/questInstances/{id}/submit

Submit a Quest instance

GET

/quests/{questId}/runs/export

Export Quest runs as CSV

POST

/webhooks

Create a webhook

GET

/assignments

List assignments

POST

/quests

Create a Quest from a template

POST

/quests/{questIdOrFormPrototypeId}/start

Start a Quest run

GET

/quests/{questId}/runs

List runs of a Quest

POST

/quests/{id}/assignments

Assign a Quest to users

POST

/questInstances/{id}/submit

Submit a Quest instance

GET

/quests/{questId}/runs/export

Export Quest runs as CSV

POST

/webhooks

Create a webhook

GET

/assignments

List assignments

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring Questmate by hand means obtaining a JWT bearer token, attaching it to the authenticated calls, and tracking which routes such as /login and the /library endpoints are open. Through Jentic you install once, import Questmate from the API Directory, store the token once, and your agent calls it.

Permission scoping

Questmate puts the Quest id in the URL path (/quests/{questId}/runs, /quests/{id}/assignments), so a rule can pin your agent to one Quest and the operations you pick. You choose the operations it may call, so destructive ones like webhook deletion or POST /users/me/deletion are not included unless you add them.

Credential isolation

Your Questmate bearer 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 'start a checklist run' or 'export quest runs as csv', and Jentic returns the matching Questmate operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Questmate API through Jentic.

What authentication does the Questmate API use?

Per its OpenAPI spec, the Questmate API authenticates with an HTTP bearer token in JWT format, sent in the Authorization header. Most operations expect the token, while a few are declared open, including GET /health, POST /login, GET /publicQuests/{publicId}, GET /quests/{id}, and the /library template and script routes. Through Jentic the token is stored by your own instance and attached at call time, so it never enters the agent's context.

Can I export completed Questmate runs with the API?

Yes. GET /quests/{questId}/runs/export returns a Quest's runs as CSV and accepts startDate, endDate, archived, and limit query parameters, while GET /quests/{questId}/runs/export/pdf returns one PDF page per run. A single run exports with GET /questInstances/{questInstanceId}/export/pdf.

What are the rate limits for the Questmate API?

The OpenAPI spec does not specify rate limits. Check the Questmate documentation at https://www.questmate.com for current limits before scheduling bulk exports.

Is there a Questmate MCP server?

You don't need an MCP server to give your agent Questmate. Jentic connects it directly from the API Directory: import it, store your bearer token once, and your agent calls the Quest operations it needs, discovered on demand rather than loaded into its context up front.

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

Yes. For example, write a rule that allows only GET /quests/{questId}/runs and the run export operations under one Quest id, so the agent can read and export that Quest's results and cannot start runs, change assignments, or delete webhooks. Every call it makes is logged.

How do I start a Questmate checklist run through Jentic?

Search Jentic for 'start a checklist run', load the POST /quests/{questIdOrFormPrototypeId}/start operation, and execute it with the Quest id. The agent can then read the run with GET /questInstances/{questInstanceId}. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Questmate API

AI ReadinessFoundational (D)44/100

See full scorecard

Official vendor OpenAPI document · agent-readyProductivityTask Managementbearer74 EndpointsREST

For Agents

Start Questmate checklist and form Quests from templates, assign them to people, track and submit runs, and export completed runs as CSV or PDF.

Use for: Start a new run of our weekly safety inspection Quest, List all open assignments for my account, Export last month's Quest runs as a CSV file, I need to assign an onboarding checklist to a new team member

Not supported: Does not handle project timelines, time tracking, or payroll. Use for running, assigning, reviewing, and exporting Questmate checklist and form Quests only.

The Questmate API runs checklist and form workflows called Quests, built from reusable templates and assigned to people in a workspace. It starts Quest runs, tracks each run's item instances and submissions, schedules recurring starts, and adds reviewers who sign off on submitted work. Completed runs export as CSV or PDF, and webhooks notify an external endpoint when a chosen event type occurs.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: C-Signals: 4

93%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: B-Signals: 4

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

49%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: FSignals: 4

21%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

56%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

90%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: A-Signals: 1

75%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: C-Signals: 1

51%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Questmate API to your agent

Capabilities

Start building with Questmate API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Questmate API

Jentic AI Readiness Score

Questmate API

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness