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.

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%2Fsandbox.echelonpay.com%2Fsandbox-echelonpay" | sh

Step 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%2Fsandbox.echelonpay.com%2Fsandbox-echelonpay" | 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

GET STARTED

Start building with Public API

Explore with Jentic One

View OpenAPI Document

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?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring the Echelon Pay Public API by hand means learning its bearer auth, choosing the sandbox or production echelonpay.com host, and handling payin and payout retries yourself. Through Jentic you install once, import the Public API from the API Directory, store the bearer token once, and your agent calls it.

Permission scoping

Echelon Pay puts the payin and payout ids in the URL path (/payins/{idPayin}, /payouts/{idPayout}), so a rule can pin your agent to specific transactions: it can read the ones you allow and nothing else. You choose the operations it may call, so writes like creating payouts are not included unless you add them.

Credential isolation

Your Echelon Pay bearer token 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 'get available payment options' or 'get a payin', and Jentic returns the matching Public API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

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 your Jentic One instance 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 through Jentic One, the self-hosted execution layer, 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.

Can I limit what my agent is allowed to do with the Echelon Pay Public API?

Yes. Jentic One runs on infrastructure you host, and your own rules decide which Echelon Pay operations and credentials the agent may use. Because Echelon Pay puts the payin and payout ids directly in the URL path (/payins/{idPayin}, /payouts/{idPayout}), you can pin the agent to specific transactions and grant read-only calls like GET /payins/{idPayin}, GET /payouts/{idPayout}, or GET /balances while excluding writes such as POST /payins/{idPayin} that create payments. Only the operations you explicitly allow are exposed to the agent.

Sandbox Echelonpay Public API

Name: Public API
Brand: Public API
Availability: InStock

AI ReadinessFoundational (C)56/100

See full scorecard

Community OpenAPI document · agent-readyPaymentsPayment Processingbearer16 EndpointsREST

Know of an official OpenAPI document? Contribute it →

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 Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: BSignals: 4

82%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

75%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: A-Signals: 4

17%

Example Density

How richly the API is illustrated with examples.

94%

Example Validity

Percentage of examples that conform to their schemas.

72%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: FSignals: 4

74%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

47%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: B-Signals: 1

60%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

100

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: A+Signals: 1

100%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Public API to your agent

Capabilities

Use Cases

Start building with Public API

Key Endpoints

Why Jentic?

Related APIs

FAQs

Sandbox Echelonpay Public API

Jentic AI Readiness Score

Public API

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness