Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Sonar Trading, 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%2Fsonar.trading%2Fsonar-trading" | 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%2Fsonar.trading%2Fsonar-trading" | 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 Sonar Trading API.
Convert a currency amount to multiple other currencies
Return a list of all currencies of countries, available via service
Integrate Sonar Trading into automated workflows
Query and filter Sonar Trading records by parameters
Monitor Sonar Trading operational status and events
GET STARTED
Patterns agents use Sonar Trading API for, with concrete tasks.
★ Identity and Authentication Operations
Use the Sonar Trading to perform identity auth operations programmatically. The API provides 4 endpoints covering core functionality including convert a currency amount to multiple other currencies, return a list of all currencies of countries, available via service, return a list of all digital currencies, available via service.
Call GET /convert to convert a currency amount to multiple other currencies
Automated Currencies Management
Automate currencies operations by combining multiple Sonar Trading endpoints. Agents can return a list of all currencies of countries, available via service and then return a list of all digital currencies, available via service in a single workflow.
Call GET /country/currencies to return a list of all currencies of countries, available via service, then verify the result
AI Agent Integration via Jentic
AI agents discover and call Sonar Trading 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.
Search Jentic for 'convert a currency amount to multiple other currencies', load the operation schema, and execute with Jentic-managed credentials
4 endpoints — currency authority: exchange rate of 1453 country currencies and crypto currencies.
METHOD
PATH
DESCRIPTION
/convert
Convert a currency amount to multiple other currencies
/country/currencies
Return a list of all currencies of countries, available via service
/digital/currencies
Return a list of all digital currencies, available via service
/history
Return a historic rate for a currencies
/convert
Convert a currency amount to multiple other currencies
/country/currencies
Return a list of all currencies of countries, available via service
/digital/currencies
Return a list of all digital currencies, available via service
/history
Return a historic rate for a currencies
What agents get from Jentic-routed access to this vendor.
Setup
Wiring Sonar Trading by hand means pointing at the sonar.trading/api/v1 host and handling paging and retries on its currency conversion and history calls yourself, even though the endpoints take no credential. Through Jentic you install once, import Sonar Trading from the API Directory, and your agent calls it.
Permission scoping
Sonar Trading is read-only over query parameters rather than resource ids in the URL path, so scope the agent to the operations it needs, such as converting a currency amount or listing supported currencies. You choose which operations are in the allowed set, so anything you do not add stays out of reach.
Credential isolation
Sonar Trading needs no credential, so there is nothing to store; if the vendor later adds one, your own Jentic One instance would hold it encrypted and inject it at execution time. Nothing about the call enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'convert a currency amount to multiple currencies' or 'get historical rates', and Jentic returns the matching Sonar Trading 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.
Specific to using Sonar Trading API through Jentic.
What authentication does the Sonar Trading use?
The Sonar Trading 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 convert a currency amount to multiple other currencies with the Sonar Trading?
Yes. Use the GET /convert endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the Sonar Trading?
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 convert a currency amount to multiple other currencies through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'convert a currency amount to multiple other currencies'. Jentic returns the matching Sonar Trading operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the Sonar Trading have?
The Sonar Trading exposes 4 endpoints covering currencies operations.
Can I limit what my agent is allowed to do with the Sonar Trading API?
Yes. Jentic One is self-hosted by you, so your own rules decide which Sonar Trading operations and credentials the agent may use. Because the API is read-only over query parameters, you can add just the calls the agent needs, such as GET /convert for currency conversion or GET /country/currencies and GET /digital/currencies for listing supported currencies, while leaving GET /history out of the allowed set. Any operation you do not add stays out of the agent's reach.
Know of an official OpenAPI document? Contribute it →
For Agents
Programmatically convert a currency amount to multiple other currencies, return a list of all currencies of countries, available via service. Covers 4 operations.
Use for: I need to convert a currency amount to multiple other currencies, I want to return a list of all currencies of countries, available via service, Search for return a list of all digital currencies, available via service, Find all return a historic rate for a currencies
Not supported: Does not handle payments, communications, or crm - use for identity and authentication only.
Currency Authority: Exchange Rate of 1453 country currencies and crypto currencies. The API exposes 4 endpoints.
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
Base layer of spec validity and structural soundness.
Aggregated quality score from linter diagnostics, weighted by severity.
Percentage of `$ref` references that resolve successfully.
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
Structural correctness score based on schema issues using logarithmic dampening.
Clarity, completeness, and ingestion readiness for developers and tooling.
How richly the API is illustrated with examples.
Percentage of examples that conform to their schemas.
Percentage of operations with complete response definitions (success, client error, server error).
Health of API ingestion, bundling, and resolution within Jentic pipelines.
Semantic breadth, depth, and agent comprehension for AI systems.
Coverage of descriptions across API elements.
Coverage of RFC 9457 Problem Details for error responses.
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
Coverage of summaries across operations/tags/info.
Functional utility, complexity comfort, and AI orchestration readiness.
Agent comfort level based on API operational and structural complexity.
Trust, risk posture, and security compliance.
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
Findability, semantic richness, and reasoning readiness.
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>