canonical: https://jentic.com/apis/truthscan.com/truthscan

# TruthScan AI Text Detection API

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.

## For AI agents

Programmatically submit text for ai detection, query detection result status. Covers 3 operations with apiKey authentication.

## Scope

Does not handle payments, communications, or developer tools - use for crm only.

## Capabilities

- 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

## Use cases

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

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

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

Example prompt: Search Jentic for 'submit text for ai detection', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/detect` | Submit text for AI detection |
| POST | `/query` | Query detection result status |
| GET | `/check-user-credits` | Check user credits |

## Key resources

- **AI Detector** — Operations related to AI Detector
- **Account** — Operations related to Account

## AI readiness

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.

- **Score:** 68 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 100 / 100
  - Developer Experience & Jentic Compatibility: 62 / 100
  - AI-Readiness & Agent Experience: 54 / 100
  - Agent Usability: 94 / 100
  - Security: 50 / 100
  - AI Discoverability: 75 / 100
- **View full report:** https://jentic.com/apis/truthscan.com/truthscan/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **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 handling:** 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.
- **Discovery method:** 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.

## Related APIs

- **Hubspot** — Alternative crm API
- **Salesforce** — Alternative crm API
- **Pipedrive** — Complementary crm API
- **Zoho** — Complementary crm API

## FAQ

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