canonical: https://jentic.com/apis/smart-glocal.com/smart-glocal # Smart Glocal Payouts API 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. ## For AI agents Programmatically start a payout session, confirm a session. Covers 4 operations with apiKey authentication. ## Scope Does not handle communications, crm, or developer tools - use for payments only. ## Capabilities - Start a payout session - Confirm a session - Cancel a session - Capture session funds - Monitor Smart Glocal Payouts API operational status and events ## Use cases ### 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. Example prompt: 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. Example prompt: 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. Example prompt: Search Jentic for 'start a payout session', load the operation schema, and execute with Jentic-managed credentials ## Key endpoints | Method | Path | Description | | --- | --- | --- | | POST | `/session/start/payout` | Start a payout session | | POST | `/session/confirm` | Confirm a session | | POST | `/session/cancel` | Cancel a session | | POST | `/session/capture` | Capture session funds | ## Key resources - **Payouts** — Operations related to Payouts - **Sessions** — Operations related to Sessions ## AI readiness 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. - **Score:** 65 / 100 - **Maturity:** AI-Aware - **Dimensions:** - Foundational Compliance: 93 / 100 - Developer Experience & Jentic Compatibility: 63 / 100 - AI-Readiness & Agent Experience: 45 / 100 - Agent Usability: 94 / 100 - Security: 50 / 100 - AI Discoverability: 100 / 100 - **View full report:** https://jentic.com/apis/smart-glocal.com/smart-glocal/scorecard - **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/ - **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview ### Score it yourself Every API in the directory is allowlisted, so you can re-score it with no key required. - **Score your own API:** https://jentic.com/scorecard.md - **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md ```sh npx @jentic/api-scorecard-cli score ``` ## Why Jentic - **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 handling:** 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. - **Discovery method:** 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. ## Related APIs - **Stripe** — Alternative payments API - **Adyen** — Alternative payments API - **Square** — Complementary payments API - **Paypal** — Complementary payments API ## FAQ ### 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. ### Can I limit what my agent is allowed to do with the Smart Glocal Payouts API? Yes. Because you run Jentic One yourself, you decide which of the Smart Glocal Payouts operations your agent may call, so you can allow it to start a payout session and confirm it while excluding cancel and capture. The payout target travels in the request body rather than the URL, so scoping is set by the operations you enable rather than by path patterns. Your Smart Glocal key is stored encrypted by your own instance and injected only when an allowed operation runs, so it never enters the agent's prompt or logs.