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

# Aituringco AITradeMoonAPI

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

## For AI agents

Programmatically endpoint that returns a json web token. this is necesary to use the other endpoi, endpoint that receive postimagesimple64requestobject . Covers 4 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 AITradeMoonAPI into automated workflows
- Query and filter AITradeMoonAPI records by parameters
- Monitor AITradeMoonAPI operational status and events

## Use cases

### Developer Tools Operations

Use the AITradeMoonAPI to perform developer tools operations programmatically. The API provides 4 endpoints covering core functionality including endpoint that returns a json web token. this is necesary to use the other endpoi, endpoint that receive postimagesimple64requestobject , endpoint that returns a list of objects of type phototaskresponse. there are two.

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 AITradeMoonAPI endpoints. Agents can endpoint that receive postimagesimple64requestobject  and then endpoint that returns a list of objects of type phototaskresponse. there are two in a single workflow.

Example prompt: Call POST `/image/post/base64` to endpoint that receive postimagesimple64requestobject , then verify the result

### AI Agent Integration via Jentic

AI agents discover and call AITradeMoonAPI 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 | `/image/post/base64` | Endpoint that receive PostImageSimple64RequestObject |
| POST | `/search/by_task/photo_task/` | Endpoint that returns a list of objects of type PhotoTaskResponse. There are two |
| POST | `/image/results/global` | Endpoint that query results of image recognition |

## Key resources

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

## Why Jentic

- **Setup:** Wiring AITradeMoonAPI by hand means obtaining its JSON web token yourself, then posting base64 images, searching by photo task, and reading global results against the hosted host. Through Jentic you install once, import AITradeMoonAPI from the API Directory, store the credential once, and your agent calls it.
- **Permission scoping:** AITradeMoonAPI 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 reading global image results. You choose the operations it may call, so obtain_token is not included unless you add it.
- **Credential handling:** Your AITradeMoonAPI 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 'post a base64 image' or 'get global image results', and Jentic returns the matching AITradeMoonAPI 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 AITradeMoonAPI use?

The AITradeMoonAPI 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 AITradeMoonAPI?

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 AITradeMoonAPI?

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 AITradeMoonAPI operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the AITradeMoonAPI have?

The AITradeMoonAPI exposes 4 endpoints covering authentication, developers operations.

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

Yes. Because you run Jentic One yourself, your own rules decide which AITradeMoonAPI operations and credentials the agent can use. You can allow just the calls it needs, such as posting a base64 image, searching by photo task, or reading global image recognition results, and leave out the rest. Since these operations carry their target in the request body rather than the URL path, obtain_token is not available to the agent unless you explicitly add it.