Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the wealthAPI, 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%2Fwealthapi.eu%2Fwealthapi-eu" | shStep 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%2Fwealthapi.eu%2Fwealthapi-eu" | 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 wealthAPI API.
Login and obtain auth token
Refresh auth token
List bank accounts
Get account by ID
Delete an account
Patterns agents use wealthAPI API for, with concrete tasks.
GET STARTED
★ Payments Operations
Use the wealthAPI to perform payments operations programmatically. The API provides 11 endpoints covering core functionality including login and obtain auth token, refresh auth token, list bank accounts.
Call POST /login to login and obtain auth token
Automated Authentication Management
Automate authentication operations by combining multiple wealthAPI endpoints. Agents can refresh auth token and then list bank accounts in a single workflow.
Call POST /refreshToken to refresh auth token, then verify the result
AI Agent Integration via Jentic
AI agents discover and call wealthAPI 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, bearer tokens manually.
Search Jentic for 'login and obtain auth token', load the operation schema, and execute with Jentic-managed credentials
11 endpoints — the wealthapi api is a restful interface for accessing the wealthapi system programmatically.
METHOD
PATH
DESCRIPTION
/login
Login and obtain auth token
/refreshToken
Refresh auth token
/accounts
List bank accounts
/accounts/{id}
Get account by ID
/accounts/{id}
Delete an account
/transactions
List transactions
/funds
List funds
/users
Create a new user
/login
Login and obtain auth token
/refreshToken
Refresh auth token
/accounts
List bank accounts
/accounts/{id}
Get account by ID
/accounts/{id}
Delete an account
/transactions
List transactions
/funds
List funds
/users
Create a new user
What agents get from Jentic-routed access to this vendor.
Setup
Wiring wealthAPI by hand means learning its bearer token alongside the mandator client id and secret headers, pointing at the sandbox host, and handling responses yourself. Through Jentic you install once, import wealthAPI from the API Directory, store those credentials once, and your agent calls it.
Permission scoping
wealthAPI puts the account id in the URL path (/accounts/{id}), so a rule can pin your agent to one account and nothing else. You choose the operations it may call, so destructive ones like deleting an account are not included unless you add them.
Credential isolation
Your wealthAPI token and mandator client credentials are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'list accounts' or 'get transactions', and Jentic returns the matching wealthAPI operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Alternatives and complements available in the Jentic catalogue.
Stripe
Alternative payments API
Choose Stripe when you need a different approach to payments operations
Specific to using wealthAPI API through Jentic.
What authentication does the wealthAPI use?
The wealthAPI uses apiKey, bearer authentication. 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 login and obtain auth token with the wealthAPI?
Yes. Use the POST /login endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the wealthAPI?
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 login and obtain auth token through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'login and obtain auth token'. Jentic returns the matching wealthAPI operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the wealthAPI have?
The wealthAPI exposes 11 endpoints covering authentication, accounts, transactions operations.
Can I limit what my agent is allowed to do with the wealthAPI?
Yes. Because you run Jentic One yourself, your own rules decide which wealthAPI operations and credentials the agent may use, so you can grant read calls like GET /accounts and GET /transactions while withholding destructive ones such as DELETE /accounts/{id} unless you explicitly add them. Since wealthAPI puts the account id in the URL path (/accounts/{id}), a rule can pin the agent to a single account and block every other one. The stored token and mandator client credentials are injected only when an allowed operation runs, so the agent can never reach an endpoint you have not approved.
For Agents
Programmatically login and obtain auth token, refresh auth token. Covers 11 operations with apiKey, bearer authentication.
Use for: I need to login and obtain auth token, I want to refresh auth token, Search for bank accounts, Find all account by id
Not supported: Does not handle communications, crm, or developer tools - use for payments only.
The wealthAPI API is a RESTful interface for accessing the wealthAPI system programmatically. It provides endpoints for account, investment and transaction management and analytics (PURE core API) as well as access to brokerage connections (brokerage API). The API uses JWT bearer token authentication and supports mandator-based multi-tenancy. The API exposes 11 endpoints secured with apiKey, bearer authentication.
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.
Base layer of spec validity and structural soundness.
Aggregated quality score from linter diagnostics, weighted by severity.
Percentage of `$ref` references that resolve successfully.
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
Structural correctness score based on schema issues using logarithmic dampening.
Clarity, completeness, and ingestion readiness for developers and tooling.
How richly the API is illustrated with examples.
Percentage of examples that conform to their schemas.
Percentage of operations with complete response definitions (success, client error, server error).
Health of API ingestion, bundling, and resolution within Jentic pipelines.
Semantic breadth, depth, and agent comprehension for AI systems.
Coverage of descriptions across API elements.
Coverage of RFC 9457 Problem Details for error responses.
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
Coverage of summaries across operations/tags/info.
Functional utility, complexity comfort, and AI orchestration readiness.
Agent comfort level based on API operational and structural complexity.
Trust, risk posture, and security compliance.
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
Findability, semantic richness, and reasoning readiness.
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>