canonical: https://jentic.com/apis/swaggerhub.aituringco/aitradeapi

# Aituringco AITradeAPI

AITuring API for web services usage. The API exposes 6 endpoints.

## For AI agents

Programmatically endpoint that returns a json web token. this is necesary to use the other endpoi, endpoint that returns a json web token, you can refresh an old one. this is nece. Covers 6 operations.

## Scope

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

## Capabilities

- Endpoint that returns a JSON web token. This is necesary to use the other endpoi
- Manage developer tools data programmatically
- Integrate AITradeAPI into automated workflows
- Query and filter AITradeAPI records by parameters
- Monitor AITradeAPI operational status and events

## Use cases

### Developer Tools Operations

Use the AITradeAPI to perform developer tools operations programmatically. The API provides 6 endpoints covering core functionality including endpoint that returns a json web token. this is necesary to use the other endpoi, endpoint that returns a json web token, you can refresh an old one. this is nece, endpoint that create place task within a time range.

Example prompt: Call POST /obtain_token/ to endpoint that returns a json web token. this is necesary to use the other endpoi

### Automated Authentication Management

Automate authentication operations by combining multiple AITradeAPI endpoints. Agents can endpoint that returns a json web token, you can refresh an old one. this is nece and then endpoint that create place task within a time range in a single workflow.

Example prompt: Call POST /refresh_token/ to endpoint that returns a json web token, you can refresh an old one. this is nece, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call AITradeAPI 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 none tokens manually.

Example prompt: Search Jentic for 'endpoint that returns a json web token. this is necesary to use the other endpoi', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/obtain_token/` | Endpoint that returns a JSON web token. This is necesary to use the other endpoi |
| POST | `/refresh_token/` | Endpoint that returns a JSON web token, you can refresh an old one. This is nece |
| POST | `/create/place_task/` | Endpoint that create Place Task within a time range |
| POST | `/image/upload_base64` | Endpoint for receiving images |
| POST | `/api_post_image_client` | Endpoint that receive PostImageRequestObject |
| POST | `/search/by_task/photo_task/` | Endpoint that returns a list of objects of type PhotoTaskResponse. There are two |

## Key resources

- **Authentication** — Secured Admin-only calls
- **Developers** — Operations available to regular developers

## Why Jentic

- **Setup:** Wiring AITradeAPI by hand means obtaining and refreshing its JSON web token yourself, then creating place tasks, uploading base64 images, and searching by photo task against the hosted host. Through Jentic you install once, import AITradeAPI from the API Directory, store the credential once, and your agent calls it.
- **Permission scoping:** AITradeAPI carries its target in the request body rather than the URL path, so limit the agent to the operations it needs, such as searching by photo task or uploading a base64 image. You choose the operations it may call, so create place task is not included unless you add it.
- **Credential handling:** Your AITradeAPI credential 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 'upload a base64 image' or 'search by photo task', and Jentic returns the matching AITradeAPI operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Github** — Alternative developer tools API
- **Gitlab** — Alternative developer tools API

## FAQ

### What authentication does the AITradeAPI use?

The AITradeAPI uses no authentication. 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 endpoint that returns a json web token. this is necesary to use the other endpoi with the AITradeAPI?

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

### What are the rate limits for the AITradeAPI?

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 endpoint that returns a json web token. this is necesary to use the other endpoi through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'endpoint that returns a json web token. this is necesary to use the other endpoi'. Jentic returns the matching AITradeAPI operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the AITradeAPI have?

The AITradeAPI exposes 6 endpoints covering authentication, developers operations.

### Can I limit what my agent is allowed to do with the AITradeAPI?

Yes. Because you self-host Jentic One, your own rules decide which AITradeAPI operations and credentials the agent may use. AITradeAPI carries its target in the request body rather than the URL path, so you can allow only the operations the agent needs, such as uploading a base64 image or searching by photo task, while withholding others like obtaining a token or creating a place task. Operations you do not grant, such as creating a place task, stay out of reach unless you explicitly add them.