Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Peatio User API v2, 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://jentic.com/install.sh?src=apis&api=%2Fapis%2Fswaggerhub.favor-ex%2Fpeatio-user-api-v2" | shStep 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fswaggerhub.favor-ex%2Fpeatio-user-api-v2" | sh
jentic register # connects your agent to your Jentic One instanceJentic 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.
What an agent can do with Peatio User API v2 API.
getPublicAnnouncement
getPublicTradingRules
getPublicTradingFees
getPublicHealthReady
getPublicHealthAlive
GET STARTED
getPublicVersion
getPublicTimestamp
Patterns agents use Peatio User API v2 API for, with concrete tasks.
★ 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.
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.
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.
Search Jentic for 'getpublicannouncement', load the operation schema, and execute with Jentic-managed credentials
75 endpoints — api for peatio application.
METHOD
PATH
DESCRIPTION
/public/announcement
getPublicAnnouncement
/public/trading_rules
getPublicTradingRules
/public/trading_fees
getPublicTradingFees
/public/health/ready
getPublicHealthReady
/public/health/alive
getPublicHealthAlive
/public/version
getPublicVersion
/public/timestamp
getPublicTimestamp
/public/member-levels
getPublicMemberLevels
/public/announcement
getPublicAnnouncement
/public/trading_rules
getPublicTradingRules
/public/trading_fees
getPublicTradingFees
/public/health/ready
getPublicHealthReady
/public/health/alive
getPublicHealthAlive
/public/version
getPublicVersion
/public/timestamp
getPublicTimestamp
/public/member-levels
getPublicMemberLevels
What agents get from Jentic-routed access to this vendor.
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 isolation
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.
Intent-based discovery
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.
Alternatives and complements available in the Jentic catalogue.
Github
Alternative developer tools API
Choose Github when you need a different approach to developer tools operations
Specific to using Peatio User API v2 API through Jentic.
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.
Know of an official OpenAPI document? Contribute it →
For Agents
Programmatically getpublicannouncement, getpublictradingrules. Covers 75 operations with apiKey authentication.
Use for: I need to getpublicannouncement, I want to getpublictradingrules, Search for getpublictradingfees, Find all getpublichealthready
Not supported: Does not handle payments, communications, or crm - use for developer tools only.
API for Peatio application. The API exposes 75 endpoints secured with apiKey authentication.