Tolq Translation API

Name: Tolq Translation API
Brand: Tolq Translation API
Availability: InStock

✓ Official Vendor SpecStorageObject Storagebasic9 EndpointsREST

For Agents

Programmatically create translation request, list all translation requests. Covers 9 operations with basic authentication.

Install Jentic One Beta

Connect the Tolq Translation API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Tolq Translation 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://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# 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 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 Tolq Translation API.

Create Translation Request

List All Translation Requests

Get Translation Request

Order Quoted Request

GET STARTED

Start building with Tolq Translation API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Tolq Translation API for, with concrete tasks.

★ Storage and Databases Operations

Use the Tolq Translation API to perform storage operations programmatically. The API provides 9 endpoints covering core functionality including create translation request, list all translation requests, get translation request.

Call POST /translations/requests to create translation request

Automated File Uploads Management

Automate file uploads operations by combining multiple Tolq Translation API endpoints. Agents can list all translation requests and then get translation request in a single workflow.

Call GET /translations/requests to list all translation requests, then verify the result

AI Agent Integration via Jentic

AI agents discover and call Tolq Translation 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 basic tokens manually.

Search Jentic for 'create translation request', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

9 endpoints — tolq translation api for submitting translation requests, getting quotes, managing file uploads, and retrieving completed translations.

METHOD

PATH

DESCRIPTION

POST

/translations/requests

Create Translation Request

GET

/translations/requests

List All Translation Requests

GET

/translations/requests/{id}

Get Translation Request

POST

/translations/requests/quote

Create Quote Request

POST

/translations/requests/{id}/order

Order Quoted Request

POST

/translations/requests/upload

Initiate File Upload

POST

/translations/requests/files/{uid}

Order Uploaded File Translation

GET

/translations/requests/files/{uid}

Get Uploaded File Info

POST

/translations/requests

Create Translation Request

GET

/translations/requests

List All Translation Requests

GET

/translations/requests/{id}

Get Translation Request

POST

/translations/requests/quote

Create Quote Request

POST

/translations/requests/{id}/order

Order Quoted Request

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Tolq Translation API basic 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., 'create translation request') and Jentic returns the matching Tolq Translation API operation with its input schema, so the agent can call the right endpoint without browsing docs.

Time to first call

Direct Tolq Translation API integration: 1-3 days for auth handling, response parsing, and error cases. Through Jentic: under 1 hour — search, load schema, execute.

FAQs

Specific to using Tolq Translation API through Jentic.

What authentication does the Tolq Translation API use?

The Tolq Translation API uses HTTP Basic authentication with username and password. 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 create translation request with the Tolq Translation API?

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

What are the rate limits for the Tolq Translation 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 create translation request through Jentic?

Install the Jentic SDK with pip install jentic, authenticate at https://app.jentic.com/sign-up, then search for 'create translation request'. Jentic returns the matching Tolq Translation API operation with its input schema. Load the schema and execute the call — credentials are injected automatically.

How many endpoints does the Tolq Translation API have?

The Tolq Translation API exposes 9 endpoints covering file uploads, translations operations.

Tolq Translation API

Connect the Tolq Translation API to your agent

Capabilities

Start building with Tolq Translation API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs