Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Thunes Money Transfer API, 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%2Fthunes.com%2Fthunes" | 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%2Fthunes.com%2Fthunes" | 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 Thunes Money Transfer API.
Check API status
List available services
Get payer details
Retrieve payer rates
BIC code lookup
GET STARTED
Patterns agents use Thunes Money Transfer API for, with concrete tasks.
★ Payments Operations
Use the Thunes Money Transfer API to perform payments operations programmatically. The API provides 31 endpoints covering core functionality including check API status, list available services, list payers with filtering options.
Call GET /ping to check API status
Automated Balances Management
Automate balances operations by combining multiple Thunes Money Transfer API endpoints. Agents can list available services and then list payers with filtering options in a single workflow.
Call GET /services to list available services, then verify the result
AI Agent Integration via Jentic
AI agents discover and call Thunes Money Transfer API 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 basic tokens manually.
Search Jentic for 'check API status', load the operation schema, and execute with Jentic-managed credentials
31 endpoints — thunes money transfer api v2 providing access to cross-border payment services including quotations, transactions, payer discovery, balance management, and reporting.
METHOD
PATH
DESCRIPTION
/ping
Check API status
/services
List available services
/payers
List payers with filtering options
/payers/{id}
Get payer details
/payers/{id}/rates
Retrieve payer rates
/countries
List countries
/lookups/BIC/{swiftBicCode}
BIC code lookup
/balances
Retrieve account balances
/ping
Check API status
/services
List available services
/payers
List payers with filtering options
/payers/{id}
Get payer details
/payers/{id}/rates
Retrieve payer rates
/countries
List countries
/lookups/BIC/{swiftBicCode}
BIC code lookup
/balances
Retrieve account balances
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Thunes Money Transfer API by hand means setting up its basic auth from your API key and secret, choosing between the production and pre-production hosts, and building the payer and quote calls yourself. Through Jentic you install once, import the Thunes Money Transfer API from the API Directory, store the credentials once, and your agent calls it.
Permission scoping
Thunes puts the payer id in the URL path (/payers/{id}, /payers/{id}/rates), so a rule can pin your agent to one payer: it can read that payer and its rates and nothing else. You choose the operations it may call, so it stays limited to the read lookups you grant.
Credential isolation
Your Thunes API key and secret are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'list available payers' or 'get transfer rates for a payer', and Jentic returns the matching Thunes Money Transfer API 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.
Stripe
Alternative payments API
Choose Stripe when you need a different approach to payments operations
Specific to using Thunes Money Transfer API through Jentic.
What authentication does the Thunes Money Transfer API use?
The Thunes Money Transfer API uses HTTP Basic authentication with username and password. 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 check API status with the Thunes Money Transfer API?
Yes. Use the GET /ping endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the Thunes Money Transfer API?
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 check API status through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'check API status'. Jentic returns the matching Thunes Money Transfer API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the Thunes Money Transfer API have?
The Thunes Money Transfer API exposes 31 endpoints covering balances, countries, lookups operations.
Can I limit what my agent is allowed to do with the Thunes Money Transfer API?
Yes. Jentic One is self-hosted by you, so your own rules decide which Thunes operations and credentials your agent can use. Because Thunes puts the payer id in the URL path, a rule can pin the agent to a single payer through GET /payers/{id} and GET /payers/{id}/rates and nothing else. You choose the operations it may call, so you can keep it to read-only lookups like GET /services, GET /countries, and GET /balances while blocking everything you do not grant.
For Agents
Programmatically check API status, list available services. Covers 31 operations with basic authentication.
Use for: I need to check API status, I want to available services, Search for payers with filtering options, Find all payer details
Not supported: Does not handle communications, crm, or developer tools - use for payments only.
Thunes Money Transfer API v2 providing access to cross-border payment services including quotations, transactions, payer discovery, balance management, and reporting. The API exposes 31 endpoints secured with basic authentication.