canonical: https://jentic.com/apis/straker.ai/straker

# Straker Verify API

Language project management, file processing, and quality verification API. The API exposes 16 endpoints secured with bearer authentication.

## For AI agents

Programmatically get all supported languages, download file from a project. Covers 16 operations with bearer authentication.

## Scope

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

## Capabilities

- Get all supported languages
- Download file from a project
- Create API key
- Query and filter Straker Verify API records by parameters
- Monitor Straker Verify API operational status and events

## Use cases

### Productivity Operations

Use the Straker Verify API to perform productivity operations programmatically. The API provides 16 endpoints covering core functionality including get all supported languages, download file from a project, create API key.

Example prompt: Call GET /languages to get all supported languages

### Automated API Keys Management

Automate API keys operations by combining multiple Straker Verify API endpoints. Agents can download file from a project and then create API key in a single workflow.

Example prompt: Call GET `/file/{fileId}` to download file from a project, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Straker Verify 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 bearer tokens manually.

Example prompt: Search Jentic for 'get all supported languages', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/languages` | Get all supported languages |
| GET | `/file/{fileId}` | Download file from a project |
| POST | `/key` | Create API key |
| GET | `/key` | Get API keys |
| GET | `/key/{keyId}` | Get API key |
| POST | `/project` | Create a new project |
| GET | `/project` | Get projects |
| GET | `/project/{projectId}` | Get project details |

## Key resources

- **API Keys** — Operations related to API Keys
- **Files** — Operations related to Files
- **Languages** — Operations related to Languages
- **Projects** — Operations related to Projects
- **User** — Operations related to User

## 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:** 67 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 83 / 100
  - Developer Experience & Jentic Compatibility: 63 / 100
  - AI-Readiness & Agent Experience: 47 / 100
  - Agent Usability: 94 / 100
  - Security: 60 / 100
  - AI Discoverability: 100 / 100
- **View full report:** https://jentic.com/apis/straker.ai/straker/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 the Straker Verify API by hand means handling its bearer auth against api-verify.straker.ai and coordinating the project, file, and workflow steps of each verification job yourself. Through Jentic you install once, import the Straker Verify API from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** Straker Verify puts the resource id in the URL path (`/project/{projectId}` and `/file/{fileId}`), so a rule can pin your agent to reading one project and its files. You choose the operations it may call, so creating or confirming projects and rotating API keys are not included unless you add them.
- **Credential handling:** Your Straker Verify API 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.
- **Discovery method:** Agents search Jentic by intent such as 'list supported languages' or 'get a verification project', and Jentic returns the matching Straker Verify API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Asana** — Alternative productivity API
- **Monday** — Alternative productivity API
- **Clickup** — Complementary productivity API

## FAQ

### What authentication does the Straker Verify API use?

The Straker Verify API uses a Bearer token in the Authorization 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 get all supported languages with the Straker Verify API?

Yes. Use the GET /languages endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Straker Verify 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 get all supported languages through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'get all supported languages'. Jentic returns the matching Straker Verify API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Straker Verify API have?

The Straker Verify API exposes 16 endpoints covering API keys, files, languages operations.

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

Yes. Because you run Jentic One yourself, your own rules decide which Straker Verify operations and credentials the agent may use. Straker Verify puts the resource id in the URL path, so operations like GET `/project/{projectId}` and GET `/file/{fileId}` let you pin the agent to reading a single project and its files. You choose which operations it may call, so creating projects with POST /project or rotating keys with POST /key stay off limits unless you grant them.