Install Jentic One Beta

Connect the Lemonway API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Lemonway 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%2Flemonway.com%2Flemonway" | 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%2Flemonway.com%2Flemonway" | 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 Lemonway API.

Open and manage per-user Lemonway accounts including blocking and unblocking flows

Accept money-in via web card payment, PayPal, SEPA direct debit, or virtual IBAN bank transfer

Send money-out via SEPA transfer to a registered IBAN for marketplace seller payouts

Run P2P transfers between two Lemonway accounts for marketplace settlement

Issue refunds against a money-in transaction and confirm the new transaction state

GET STARTED

Start building with Lemonway API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Lemonway API for, with concrete tasks.

★ Marketplace Seller Onboarding and Payouts

Onboard a marketplace seller and pay them out at the end of the cycle. The agent calls POST /v2/accounts to open the seller account, registers the IBAN via POST /v2/moneyouts/iban, and at payout time calls POST /v2/moneyouts/transfer to send the SEPA transfer. Replaces the manual onboarding ticket queue and lets payouts run on schedule.

POST /v2/accounts for the seller, POST /v2/moneyouts/iban with their IBAN, then POST /v2/moneyouts/transfer at payout time.

Web Card Checkout for a Marketplace Buyer

Take a card payment from a buyer and credit the platform's holding account. The agent calls POST /v2/moneyins/cards/web/init with the amount and return URL, redirects the buyer to the hosted card page, and then verifies the resulting state via GET /v2/moneyins/{id}. The funds are then available for split or P2P transfer to the seller.

POST /v2/moneyins/cards/web/init with the order amount, redirect the buyer to the hosted page, and confirm the result with GET /v2/moneyins/{id}.

Refund and Dispute Reconciliation

Run finance reconciliation across refunds and disputes. The agent issues refunds via PUT /v2/refunds/{id} where required, lists open disputes through GET /v2/disputes, and joins the data to internal order records. Removes the manual export-and-pivot workflow that finance teams typically run on a Lemonway dashboard.

PUT /v2/refunds/{id} for the queued refunds and GET /v2/disputes to pull open disputes, joining both to the internal order ledger.

P2P Transfer Between Buyer and Seller Accounts

Move funds from a buyer's holding account to the seller's account inside Lemonway after the order ships. The agent calls POST /v2/p2p with both accountIds and the amount, then confirms the new balances via GET /v2/accounts/{accountid}/balances. Avoids re-running card capture and keeps the marketplace ledger consistent.

POST /v2/p2p with the buyer and seller accountIds and the order amount, then GET /v2/accounts/{accountid}/balances on both to confirm.

AI Agent Marketplace Operator via Jentic

An AI agent built on Jentic acts as a junior payments operator: it opens accounts on demand, runs payouts, and resolves refund tickets without the operator touching the API directly. Jentic isolates the OAuth client credentials so the agent never holds the raw bearer token between calls.

Through Jentic, search 'open lemonway account', execute POST /v2/accounts for the new seller, then chain to POST /v2/moneyouts/iban and POST /v2/moneyouts/transfer when the payout is due.

Key Endpoints

17 endpoints — jentic publishes the only available openapi specification for lemonway api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/v2/accounts

Create an account

GET

/v2/accounts/{accountid}/balances

Get account balances

POST

/v2/moneyins/cards/web/init

Initiate a hosted web card payment

POST

/v2/moneyins/bankwire/iban/create

Create a virtual IBAN for incoming wires

POST

/v2/moneyouts/iban

POST

/v2/moneyouts/transfer

Send a SEPA payout

POST

/v2/p2p

Run a P2P transfer between two accounts

PUT

/v2/refunds/{id}

Issue a refund against a money-in transaction

POST

/v2/accounts

Create an account

GET

/v2/accounts/{accountid}/balances

Get account balances

POST

/v2/moneyins/cards/web/init

Initiate a hosted web card payment

POST

/v2/moneyins/bankwire/iban/create

Create a virtual IBAN for incoming wires

POST

/v2/moneyouts/iban

POST

/v2/moneyouts/transfer

Send a SEPA payout

POST

/v2/p2p

Run a P2P transfer between two accounts

PUT

/v2/refunds/{id}

Issue a refund against a money-in transaction

Why Jentic?

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

Setup

Wiring the Lemonway API by hand means running the OAuth client-credentials flow, refreshing the resulting bearer token, and targeting the api.lemonway.com host across the money-in and money-out endpoints yourself. Through Jentic you install once, import the Lemonway API from the API Directory, store the OAuth client credentials once, and your agent calls it.

Permission scoping

You choose which Lemonway operations the agent may call, so you can limit it to the ones it needs, such as opening accounts and reading balances. Because payouts and transfers move money, you can leave the money-out and refund operations out of the allowed set and grant only account and balance access.

Credential isolation

Your Lemonway OAuth client credentials are stored once, encrypted, by your own Jentic One instance and the resulting bearer token is injected at execution time. The secrets never enter the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'open a Lemonway account' or 'send a SEPA payout', and Jentic returns the matching Lemonway operation with its input schema so the agent calls the right endpoint without parsing the payment docs by hand.

FAQs

Specific to using Lemonway API through Jentic.

Why is there no official OpenAPI spec for Lemonway API?

Lemonway does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Lemonway API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

What authentication does the Lemonway API use?

The Lemonway API uses OAuth 2.0 client credentials at `https://api.lemonway.com/oauth/token` to issue a bearer token, which is then sent in the `Authorization: Bearer <token>` header on subsequent calls. Through Jentic, both the client credentials and the token sit encrypted in the credential vault.

Can I issue a refund against a money-in transaction?

Yes. PUT /v2/refunds/{id} issues the refund where `{id}` is the original money-in transaction. The response includes the refund state, and you can confirm the impact on balances with GET /v2/accounts/{accountid}/balances.

What are the rate limits for the Lemonway API?

Rate limits are not declared in the OpenAPI spec. Lemonway is a regulated payments service, so design integrations to handle 4xx and 5xx responses gracefully and prefer webhook-driven flows over tight polling on /v2/moneyins/{id}.

How do I open a Lemonway account through Jentic?

Run `pip install jentic`, search 'open lemonway account', and execute POST /v2/accounts with the user details. Jentic resolves the right operation, applies the OAuth-issued bearer token, and returns the new accountId.

Which money-in methods does the Lemonway API support?

POST /v2/moneyins/cards/web/init for hosted web card, /v2/moneyins/paypal/init for PayPal, /v2/moneyins/sdd/init for SEPA direct debit, and /v2/moneyins/bankwire/iban/create for a virtual IBAN that buyers can wire to.

Can I limit what my agent is allowed to do with the Lemonway API?

Yes. Because Jentic One is self-hosted, your own rules decide which Lemonway operations the agent may call, so you can allow only what a task needs, such as opening accounts with POST /v2/accounts and reading balances with GET /v2/accounts/{accountid}/balances. Since payouts and transfers move money, you can leave the money-out and refund operations like POST /v2/moneyouts/transfer and PUT /v2/refunds/{id} out of the allowed set. Your OAuth client credentials stay encrypted in your own instance and the bearer token is injected only for the operations you permit.

Lemonway API

AI ReadinessAI-Aware (B+)70/100

See full scorecard

Agent-ready OpenAPI document · curated by JenticPaymentsPayment Processingoauth2, bearer17 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Open Lemonway accounts, accept card and SEPA payments, run P2P transfers and payouts, refund transactions, and reconcile balances and disputes for marketplace and fintech apps.

Use for: Open a new Lemonway account for a marketplace seller, Initiate a card payment for a buyer, Send a SEPA payout to a seller's IBAN, Refund a specific money-in transaction

Not supported: Does not handle KYC document verification, accounting, or tax filing - use for account, money-in, money-out, P2P, refunds, and disputes only.

Jentic publishes the only available OpenAPI specification for Lemonway API, keeping it validated and agent-ready. The Lemonway API is a European payments and e-money platform built around per-user accounts: agents can open accounts, block or unblock them, list balances and transactions, take money in via card, PayPal, SEPA direct debit, or virtual IBAN bank transfer, send payouts via SEPA transfer, run peer-to-peer transfers between accounts, issue refunds, and list disputes. OAuth client-credentials issues a bearer token that is sent on subsequent calls.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: ASignals: 4

98%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

100%

Specification Validity

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

25%

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: B-Signals: 4

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

50%

Response Coverage

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

93%

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: C-Signals: 4

58%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

100%

OperationId Quality

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

52%

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: A-Signals: 1

72%

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 Lemonway API to your agent

Capabilities

Start building with Lemonway API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Lemonway API

Jentic AI Readiness Score

Lemonway 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