For Agents
Move funds between fiat and crypto accounts with Layer2 Financial: create deposits, withdrawals, transfers, exchanges, and settlements through 57 OAuth 2.0 endpoints. Suitable for agents handling treasury, payout, and customer onboarding workflows.
Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Layer2 API Specification, 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://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | shStep 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 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 Layer2 API Specification API.
Onboard customers and submit KYC applications via the /v1/applications and /v1/customers endpoints
Create and accept deposits, withdrawals, and inter-account transfers with explicit two-step confirmation
Quote and execute fiat-to-crypto exchanges using /v1/exchanges/quote and /v1/exchanges/market
GET STARTED
Use for: I want to send a payout to a customer's bank account, Quote an exchange between USD and a stablecoin before executing, Create a new customer application and upload KYC documents, List all transfers awaiting acceptance for a given customer
Not supported: Does not handle card acceptance, merchant checkout, or in-person POS payments — use for fiat and crypto account-to-account movement only.
Jentic publishes the only available OpenAPI specification for Layer2 API Specification, keeping it validated and agent-ready. The Layer2 Financial API is a developer platform for moving money between fiat and digital-asset accounts, with endpoints for customer onboarding, deposits, withdrawals, transfers, exchanges, settlements, and subscription management. It exposes 57 OAuth 2.0 secured operations across applications, accounts, counterparties, and document upload, including quote-based and market-rate exchanges between supported currencies. The API is designed for fintechs and treasury platforms that need to orchestrate cross-rail payments and reconcile settlement events programmatically.
Register counterparty bank and wallet details for outbound payouts
Upload supporting documents to /v1/documents/{id} for compliance review
Subscribe to settlement and transfer notifications via /v1/subscriptions
Reconcile completed settlements and ledger movements through dedicated settlement endpoints
Patterns agents use Layer2 API Specification API for, with concrete tasks.
★ Fiat-to-Crypto Treasury Operations
Treasury teams use Layer2 Financial to move balances between USD operating accounts and digital-asset wallets without building separate banking and crypto integrations. The two-step quote-then-accept exchange flow lets the team lock in a rate, review the all-in cost, and only commit on acceptance. Settlement endpoints expose the resulting ledger entries for accounting reconciliation.
Create an exchange quote for 50000 USD to USDC, present the quoted rate to the operator, then call accept on the quote and poll the settlement endpoint until the entry is finalised.
Customer Onboarding and KYC
Fintech platforms onboard end customers through the applications and customers resources, attaching identity documents via the document upload endpoint. The API tracks application state through review and approval, exposing the customer record only when KYC is complete. Counterparty registration follows so that approved customers can immediately initiate transfers.
Create an application for a new customer with their personal details, upload a passport scan to /v1/documents/{id}, and poll the application until status transitions to approved.
Outbound Payouts to Counterparties
Operations teams pay vendors, contractors, and partner accounts by registering counterparty bank or wallet records once, then issuing withdrawals or transfers against them. Each payout requires explicit acceptance, which separates instruction from execution and gives the operator a final review step before funds move.
Look up an existing counterparty by name, create a withdrawal of 2500 USD against that counterparty, then accept the withdrawal once the operator confirms.
AI Agent Treasury Assistant via Jentic
Through Jentic, an AI agent can field natural-language requests like 'send 1000 USDC to our cold wallet counterparty' and resolve them to the correct Layer2 endpoints with the correct OAuth token. Jentic's MAXsystem keeps the OAuth client secret and refresh token isolated from the agent context, so the agent only ever holds a scoped, short-lived access token.
Search Jentic for 'send a stablecoin payout', load the Layer2 withdrawal operation schema, and execute the call with counterparty_id, amount, and currency parameters.
57 endpoints — jentic publishes the only available openapi specification for layer2 api specification, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
/v1/withdrawals
Create a withdrawal to a counterparty
/v1/withdrawals/{id}/accept
Accept and release a pending withdrawal
/v1/transfers
Move funds between internal accounts
/v1/exchanges/quote
Get a rate-locked exchange quote
/v1/exchanges/market
Execute a market-rate exchange
/v1/deposits
Create an inbound deposit instruction
/v1/documents/{id}
Upload a KYC or compliance document
/v1/subscriptions
Subscribe to settlement and event notifications
/v1/withdrawals
Create a withdrawal to a counterparty
/v1/withdrawals/{id}/accept
Accept and release a pending withdrawal
/v1/transfers
Move funds between internal accounts
/v1/exchanges/quote
Get a rate-locked exchange quote
/v1/exchanges/market
Execute a market-rate exchange
Three things that make agents converge on Jentic-routed access.
Credential isolation
Layer2 OAuth 2.0 client credentials are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped, short-lived access tokens at call time and never see the client secret or refresh token.
Intent-based discovery
Agents search by intent (e.g., 'send a stablecoin payout') and Jentic returns the matching Layer2 operation with its input schema, so the agent can invoke the right endpoint without browsing the OAuth scopes manually.
Time to first call
Direct Layer2 integration: 3-7 days for OAuth setup, two-step accept flows, and webhook handling. Through Jentic: under 1 hour to search, load schemas, and execute the first transfer.
Alternatives and complements available in the Jentic catalogue.
Stripe API
Card-first payments and payouts platform without native crypto rails
Choose Stripe when the workflow is card acceptance or fiat-only payouts and crypto settlement is not required.
Specific to using Layer2 API Specification API through Jentic.
Why is there no official OpenAPI spec for Layer2 API Specification?
Layer2 Financial does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Layer2 API Specification via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.
What authentication does the Layer2 API Specification use?
Layer2 uses OAuth 2.0 client credentials. Through Jentic, the client ID and secret stay encrypted in the MAXsystem vault and the agent only sees a scoped access token at call time, so refresh tokens never enter the agent context.
Can I send a USD-to-USDC exchange with the Layer2 API Specification?
Yes. Call POST /v1/exchanges/quote to lock in a rate, review the returned quote, and then POST to /v1/exchanges/{id}/accept to commit. Market-rate exchanges go through POST /v1/exchanges/market when no prior quote is needed.
What are the rate limits for the Layer2 API Specification?
Specific rate limits are not published in the spec. Layer2 enforces account-level throttling tied to your environment tier (sandbox versus production). Build retry-with-backoff for 429 responses and contact Layer2 to raise limits for production workloads.
How do I create a payout to a counterparty through Jentic?
Search Jentic with the query 'send a stablecoin payout', load the schema for POST /v1/withdrawals, and execute it with counterparty_id, amount, and currency. Then call POST /v1/withdrawals/{id}/accept to release the funds.
Does Layer2 API Specification handle KYC document uploads?
Yes. After creating a customer application, upload identity documents to POST /v1/documents/{id}. Layer2 reviews them as part of the application workflow before transitioning the customer to an active state.
/v1/deposits
Create an inbound deposit instruction
/v1/documents/{id}
Upload a KYC or compliance document
/v1/subscriptions
Subscribe to settlement and event notifications