canonical: https://jentic.com/apis/swaggerhub.favor-ex/peatio-user-api-v2

# Favor Ex Peatio User API v2

API for Peatio application. The API exposes 75 endpoints secured with apiKey authentication.

## For AI agents

Programmatically getpublicannouncement, getpublictradingrules. Covers 75 operations with apiKey authentication.

## Scope

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

## Capabilities

- getPublicAnnouncement
- getPublicTradingRules
- getPublicTradingFees
- getPublicHealthReady
- getPublicHealthAlive
- getPublicVersion
- getPublicTimestamp

## Use cases

### Developer Tools Operations

Use the Peatio User API v2 to perform developer tools operations programmatically. The API provides 75 endpoints covering core functionality including getpublicannouncement, getpublictradingrules, getpublictradingfees.

Example prompt: Call GET `/public/announcement` to getpublicannouncement

### Automated public Management

Automate public operations by combining multiple Peatio User API v2 endpoints. Agents can getpublictradingrules and then getpublictradingfees in a single workflow.

Example prompt: Call GET `/public/trading_rules` to getpublictradingrules, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Peatio User API v2 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 'getpublicannouncement', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/public/announcement` | getPublicAnnouncement |
| GET | `/public/trading_rules` | getPublicTradingRules |
| GET | `/public/trading_fees` | getPublicTradingFees |
| GET | `/public/health/ready` | getPublicHealthReady |
| GET | `/public/health/alive` | getPublicHealthAlive |
| GET | `/public/version` | getPublicVersion |
| GET | `/public/timestamp` | getPublicTimestamp |
| GET | `/public/member-levels` | getPublicMemberLevels |

## Key resources

- **public** — Operations about publics
- **account** — Operations about accounts
- **rewards** — Operations about rewards
- **market** — Operations about markets
- **coingecko** — Operations about coingeckos

## Why Jentic

- **Setup:** Wiring the Peatio User API by hand means passing its JWT API key in the header on every call and coding the public market and account operations against a local host yourself. Through Jentic you install once, import Peatio User API v2 from the API Directory, store the key once, and your agent calls it.
- **Permission scoping:** Peatio public routes take their parameters in the query or body rather than a resource id in the path, so scope the agent to the operations it needs, such as reading announcements or trading rules. You choose the operations it may call, so anything beyond those read operations is not included unless you add it.
- **Credential handling:** Your Peatio 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 'get current trading fees' or 'check the exchange health', and Jentic returns the matching Peatio User API v2 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 Peatio User API v2 use?

The Peatio User API v2 uses an API key passed in the `JWT` 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 getpublicannouncement with the Peatio User API v2?

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

### What are the rate limits for the Peatio User API v2?

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 getpublicannouncement through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'getpublicannouncement'. Jentic returns the matching Peatio User API v2 operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Peatio User API v2 have?

The Peatio User API v2 exposes 75 endpoints covering public, account, rewards operations.

### Can I limit what my agent is allowed to do with the Peatio User API v2?

Yes. Jentic One is self-hosted by you, so your own rules decide which Peatio operations and credentials the agent may use. Because Peatio's public routes take their parameters in the query or body rather than a resource id in the path, you scope the agent to just the operations it needs, such as reading announcements, trading rules, or trading fees. Anything beyond the read operations you approve is not available to the agent unless you add it.