Product

How Jentic Works

From API assessment to production deployment in four simple steps.

Product Overview

PLATFORM

Jentic OneSelf-hosted, open-source control plane between your agents and any APIAPI DirectoryBrowse 10,000+ APIs ready for AI agent integrationAPI ScorecardAssess your APIs for AI-readiness with automated scoringAgentic SandboxSafely simulate AI agents with your production APIsJenticSign in to the Jentic web app

CAPABILITIES

IntegrationConnect AI agents to your existing systemsWorkflowsDiscover and capture successful agent workflowsGovernanceDefine, observe, and enforce AI policies

TOOLS

Arazzo UIVisualize Arazzo workflows as interactive documentationArazzo EditorBuild and edit multi-step API workflows visually
Pricing
Developers

GET STARTED

DocumentationGuides and API referenceQuickstartGet up and running in minutes

COMMUNITY

GitHubOpen source projects and examples
Resources
BlogLatest articles and insightsPress & MediaBrand assets and press contactOpen StandardsBuilt on open specs. Never locked in.NewsletterAPIs, AI agents, mixed with architecture and strategy.
Company
About UsOur mission and teamCareersJoin our teamContactGet in touch
Install Jentic OneBook a Demo
How Jentic WorksJentic OneAPI DirectoryAPI ScorecardAgentic SandboxJenticIntegrationWorkflowsGovernanceArazzo UIArazzo Editor
Pricing
DocumentationQuickstartGitHub
BlogPress & MediaOpen StandardsNewsletter
About UsCareersContact
Request a demoInstall Jentic One
Jentic
For Enterprises
  • Product Overview
  • Agentic Sandbox
  • Book a Demo
For Developers
  • Jentic One
  • Documentation
  • GitHub
Company
  • About Jentic
  • Careers
  • Contact Us
ISO/IEC 27001:2022 certification badge issued by Prescient Security

Information Security Management System

Certified to ISO/IEC 27001:2022 by Prescient Security

Terms & Conditions•Privacy Policy•
© 2026 Jentic. All rights reserved.
APIs / Payments / Public API
Public API logo

Sandbox Echelonpay Public API

★ Only Publicly Available OpenAPI DocumentPaymentsPayment Processingbearer16 EndpointsREST

For Agents

Programmatically available payment options., available payment options.. Covers 16 operations with bearer authentication.

Use for: I need to available payment options., I want to available payment options., Search for payment., Find all incoming payment detail.

Not supported: Does not handle communications, crm, or developer tools — use for payments only.

Echelon solutions simplify your payment process, and offer a wide range of features & services to help your business run smoothly. With our cutting edge technology, global coverage, our alternative solutions - we will connect your business with over 1 billion consumers across Asia. Echelon offers you an All-In-One API integration, giving your clients access to their preferred local payment method . The API exposes 16 endpoints secured with bearer authentication.

Jentic One on GithubView OpenAPI Document

Install Jentic One Beta

Connect the Public API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Public 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.

1

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
2

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic 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.

Capabilities

What an agent can do with Public API.

Available payment options.

Create payment.

Incoming payment detail.

Outgoing payment detail.

Set external reference for the payment.

Use Cases

Patterns agents use Public API for, with concrete tasks.

★ Payments Operations

Use the Public API to perform payments operations programmatically. The API provides 16 endpoints covering core functionality including available payment options., available payment options., create payment..

Call POST /payins/!availablePaymentOptions to available payment options.

Automated Payments Management

Automate payments operations by combining multiple Public API endpoints. Agents can available payment options. and then create payment. in a single workflow.

Call POST /payouts/!availablePaymentOptions to available payment options., then verify the result

AI Agent Integration via Jentic

AI agents discover and call Public 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 bearer tokens manually.

Search Jentic for 'available payment options.', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

16 endpoints — echelon solutions simplify your payment process, and offer a wide range of features & services to help your business run smoothly.

METHOD

PATH

DESCRIPTION

POST

/payins/!availablePaymentOptions

Available payment options.

POST

/payouts/!availablePaymentOptions

Available payment options.

POST

/payins/{idPayin}

Create payment.

GET

/payins/{idPayin}

Incoming payment detail.

POST

/payouts/{idPayout}

Create outgoing payment.

GET

/payouts/{idPayout}

Outgoing payment detail.

POST

/payins/{idPayin}/!setExternalReference

Set external reference for the payment.

GET

/balances

Account balance.

POST

/payins/!availablePaymentOptions

Available payment options.

POST

/payouts/!availablePaymentOptions

Available payment options.

POST

/payins/{idPayin}

Create payment.

GET

/payins/{idPayin}

Incoming payment detail.

POST

/payouts/{idPayout}

Create outgoing payment.

GET

/payouts/{idPayout}

Outgoing payment detail.

POST

/payins/{idPayin}/!setExternalReference

Set external reference for the payment.

GET

/balances

Account balance.

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential management

Credential isolation

Public API bearer credentials are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access tokens — raw secrets never enter the agent context.

Intent-based discovery

Intent-based discovery

Agents search by intent (e.g., 'available payment options.') and Jentic returns the matching Public API operation with its input schema, so the agent can call the right endpoint without browsing docs.

Time to first call

Time to first call

Direct Public API integration: 1-3 days for auth handling, response parsing, and error cases. Through Jentic: under 1 hour — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Stripe

Alternative payments API

Choose Stripe when you need a different approach to payments operations

Alternative

Adyen

→

Alternative payments API

Choose Adyen when you need a different approach to payments operations

Complementary

Square

→

Complementary payments API

Choose Square when you need a complementary approach to payments operations

Complementary

Paypal

→

Complementary payments API

Choose Paypal when you need a complementary approach to payments operations

FAQs

Specific to using Public API through Jentic.

What authentication does the Public API use?

The Public API uses a Bearer token in the Authorization header. Through Jentic, these credentials are stored encrypted in the MAXsystem vault and injected at execution time, so raw secrets never enter the agent context.

Can I available payment options. with the Public API?

Yes. Use the POST /payins/!availablePaymentOptions endpoint. The API returns structured JSON responses that agents can parse and act on directly.

What are the rate limits for the Public 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 available payment options. through Jentic?

Install the Jentic SDK with pip install jentic, authenticate at https://app.jentic.com/sign-up, then search for 'available payment options.'. Jentic returns the matching Public API operation with its input schema. Load the schema and execute the call — credentials are injected automatically.

How many endpoints does the Public API have?

The Public API exposes 16 endpoints covering payments, incoming payments, outgoing payments operations.

GET STARTED

Start building with Public API

Explore with Jentic
View OpenAPI Document