For Agents
Programmatically report behavior, create a background check. Covers 25 operations with apiKey authentication.
Use for: I need to report behavior, I want to a background check, Search for checks, Find all health dashboard
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Checks 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.
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh# 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 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 Checks API API.
Report Behavior
Create a background check
List Checks
Get Health Dashboard
Monitor Checks API operational status and events
GET STARTED
Not supported: Does not handle payments, communications, or crm — use for productivity only.
Jentic publishes the only available OpenAPI document for Checks API, keeping it validated and agent-ready.
**NOTE:** This is a preview of the API and it is not considered stable since refinements are still being made. Introduction Welcome to the **Truora Check** [**RESTful API**](https://en.wikipedia.org/wiki/Representational_state_transfer) reference. You may also want to check out our [**Validations API docs**](https://docs.validations.truora.com/) or our [**Signals API docs**](https://docs.signals.t. The API exposes 25 endpoints secured with apiKey authentication.
Patterns agents use Checks API API for, with concrete tasks.
★ Productivity Operations
Use the Checks API to perform productivity operations programmatically. The API provides 25 endpoints covering core functionality including report behavior, create a background check, list checks.
Call POST /v1/behavior to report behavior
Automated checks Management
Automate checks operations by combining multiple Checks API endpoints. Agents can create a background check and then list checks in a single workflow.
Call POST /v1/checks to create a background check, then verify the result
AI Agent Integration via Jentic
AI agents discover and call Checks API 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 apiKey tokens manually.
Search Jentic for 'report behavior', load the operation schema, and execute with Jentic-managed credentials
25 endpoints — **note:** this is a preview of the api and it is not considered stable since refinements are still being made.
METHOD
PATH
DESCRIPTION
/v1/behavior
Report Behavior
/v1/checks
Create a background check
/v1/checks
List Checks
/v1/checks/health
Get Health Dashboard
/v1/checks/{check_id}
Get Background Check
/v1/checks/{check_id}/details
List Check Details
/v1/checks/{check_id}/pdf
Create PDF
/v1/checks/{check_id}/pdf
Get PDF
/v1/behavior
Report Behavior
/v1/checks
Create a background check
/v1/checks
List Checks
/v1/checks/health
Get Health Dashboard
/v1/checks/{check_id}
Get Background Check
/v1/checks/{check_id}/details
Three things that make agents converge on Jentic-routed access.
Credential isolation
Checks API apiKey credentials are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access tokens — raw secrets never enter the agent context.
Intent-based discovery
Agents search by intent (e.g., 'report behavior') and Jentic returns the matching Checks API operation with its input schema, so the agent can call the right endpoint without browsing docs.
Time to first call
Direct Checks API integration: 1-3 days for auth handling, response parsing, and error cases. Through Jentic: under 1 hour — search, load schema, execute.
Alternatives and complements available in the Jentic catalogue.
Asana
Alternative productivity API
Choose Asana when you need a different approach to productivity operations
Monday
Alternative productivity API
Choose Monday when you need a different approach to productivity operations
Clickup
Complementary productivity API
Choose Clickup when you need a complementary approach to productivity operations
Specific to using Checks API API through Jentic.
What authentication does the Checks API use?
The Checks API uses an API key passed in the `Truora-API-Key` header. Through Jentic, these credentials are stored encrypted in the MAXsystem vault and injected at execution time, so raw secrets never enter the agent context.
Can I report behavior with the Checks API?
Yes. Use the POST /v1/behavior endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the Checks API?
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 report behavior through Jentic?
Install the Jentic SDK with pip install jentic, authenticate at https://app.jentic.com/sign-up, then search for 'report behavior'. Jentic returns the matching Checks API operation with its input schema. Load the schema and execute the call — credentials are injected automatically.
How many endpoints does the Checks API have?
The Checks API exposes 25 endpoints covering checks, reports, custom-type operations.
List Check Details
/v1/checks/{check_id}/pdf
Create PDF
/v1/checks/{check_id}/pdf
Get PDF