Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the TruthScan AI Text Detection 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%2Ftruthscan.com%2Ftruthscan" | 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%2Ftruthscan.com%2Ftruthscan" | 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 TruthScan AI Text Detection API.
Submit text for AI detection
Query detection result status
Check user credits
Query and filter TruthScan AI Text Detection API records by parameters
Monitor TruthScan AI Text Detection API operational status and events
GET STARTED
Patterns agents use TruthScan AI Text Detection API for, with concrete tasks.
★ CRM Operations
Use the TruthScan AI Text Detection API to perform crm operations programmatically. The API provides 3 endpoints covering core functionality including submit text for ai detection, query detection result status, check user credits.
Call POST /detect to submit text for ai detection
Automated AI Detector Management
Automate ai detector operations by combining multiple TruthScan AI Text Detection API endpoints. Agents can query detection result status and then check user credits in a single workflow.
Call POST /query to query detection result status, then verify the result
AI Agent Integration via Jentic
AI agents discover and call TruthScan AI Text Detection 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 'submit text for ai detection', load the operation schema, and execute with Jentic-managed credentials
3 endpoints — truthscan ai text detection api for detecting ai-generated text.
METHOD
PATH
DESCRIPTION
/detect
Submit text for AI detection
/query
Query detection result status
/check-user-credits
Check user credits
/detect
Submit text for AI detection
/query
Query detection result status
/check-user-credits
Check user credits
What agents get from Jentic-routed access to this vendor.
Setup
Wiring TruthScan AI Text Detection API by hand means setting its apikey header, pointing at its detect-text host, and handling errors and retries yourself. Through Jentic you install once, import TruthScan AI Text Detection API from the API Directory, store the API key once, and your agent calls it.
Permission scoping
TruthScan AI Text Detection API takes its input in the request body at flat paths like /detect and /query, so scoping is operations-only: you limit the agent to the operations it needs, such as detecting text or checking remaining credits, and leave out anything else. Every operation the agent can run is one you put in that allowed set.
Credential isolation
Your TruthScan AI Text Detection API key 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 'detect AI-generated text' or 'check remaining credits', and Jentic returns the matching TruthScan AI Text Detection API 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 TruthScan AI Text Detection API through Jentic.
What authentication does the TruthScan AI Text Detection API use?
The TruthScan AI Text Detection API uses an API key passed in the `apikey` 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 submit text for ai detection with the TruthScan AI Text Detection API?
Yes. Use the POST /detect endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the TruthScan AI Text Detection 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 submit text for ai detection through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'submit text for ai detection'. Jentic returns the matching TruthScan AI Text Detection API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the TruthScan AI Text Detection API have?
The TruthScan AI Text Detection API exposes 3 endpoints covering ai detector, account operations.
Can I limit what my agent is allowed to do with the TruthScan AI Text Detection API?
Yes. Because you run Jentic One yourself, your own rules decide which TruthScan operations and credentials the agent may use, and scoping here is operations-only. You add just the endpoints the agent needs to its allowed set, such as POST /detect to submit text for AI detection, POST /query to check detection result status, or GET /check-user-credits to read remaining credits, and leave every other operation out. The agent can call only what you put in that allowed set, and your stored API key is injected at execution time rather than exposed to the agent.
For Agents
Programmatically submit text for ai detection, query detection result status. Covers 3 operations with apiKey authentication.
Use for: I need to submit text for ai detection, I want to query detection result status, Search for check user credits, List all records from TruthScan AI Text Detection API
Not supported: Does not handle payments, communications, or developer tools - use for crm only.
TruthScan AI text detection API for detecting AI-generated text. Supports batch analysis and sentence-level detection via WebSocket. The API exposes 3 endpoints secured with apiKey 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>