For Agents
Programmatically start a payout session, confirm a session. Covers 4 operations with apiKey authentication.
Use for: I need to start a payout session, I want to confirm a session, Search for cancel a session, Find all capture session funds
Not supported: Does not handle communications, crm, or developer tools - use for payments only.
Smart Glocal API enables payout operations to various countries and currencies. Supports bank account payouts with session-based transaction management. The API exposes 4 endpoints secured with apiKey authentication.
Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Smart Glocal Payouts 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%2Fsmart-glocal.com%2Fsmart-glocal" | 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%2Fsmart-glocal.com%2Fsmart-glocal" | 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 Smart Glocal Payouts API.
Start a payout session
Confirm a session
Cancel a session
Capture session funds
Monitor Smart Glocal Payouts API operational status and events
Patterns agents use Smart Glocal Payouts API for, with concrete tasks.
★ Payments Operations
Use the Smart Glocal Payouts API to perform payments operations programmatically. The API provides 4 endpoints covering core functionality including start a payout session, confirm a session, cancel a session.
Call POST /session/start/payout to start a payout session
Automated Payouts Management
Automate payouts operations by combining multiple Smart Glocal Payouts API endpoints. Agents can confirm a session and then cancel a session in a single workflow.
Call POST /session/confirm to confirm a session, then verify the result
AI Agent Integration via Jentic
AI agents discover and call Smart Glocal Payouts 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 apiKey tokens manually.
Search Jentic for 'start a payout session', load the operation schema, and execute with Jentic-managed credentials
4 endpoints — smart glocal api enables payout operations to various countries and currencies.
METHOD
PATH
DESCRIPTION
/session/start/payout
Start a payout session
/session/confirm
Confirm a session
/session/cancel
Cancel a session
/session/capture
Capture session funds
/session/start/payout
Start a payout session
/session/confirm
Confirm a session
/session/cancel
Cancel a session
/session/capture
Capture session funds
What agents get from Jentic-routed access to this vendor.
Setup
Wiring Smart Glocal by hand means sending its X-PARTNER-PROJECT key and X-PARTNER-SIGN signature headers on every call and managing retries yourself. Through Jentic you install once, import the Smart Glocal Payouts API from the API Directory, store the key once, and your agent calls it.
Permission scoping
Smart Glocal carries the payout target in the request body rather than the URL path, so scope the agent to the operations it needs, such as starting a payout session and confirming it. You choose which operations are allowed, so cancel and capture are not included unless you add them.
Credential isolation
Your Smart Glocal 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 'start a payout session' or 'confirm a payout', and Jentic returns the matching Smart Glocal 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 Smart Glocal Payouts API through Jentic.
What authentication does the Smart Glocal Payouts API use?
The Smart Glocal Payouts API uses an API key passed in the `X-PARTNER-PROJECT` 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 start a payout session with the Smart Glocal Payouts API?
Yes. Use the POST /session/start/payout endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the Smart Glocal Payouts 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 start a payout session through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'start a payout session'. Jentic returns the matching Smart Glocal Payouts API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the Smart Glocal Payouts API have?
The Smart Glocal Payouts API exposes 4 endpoints covering payouts, sessions operations.
GET STARTED