Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Wealth Reader 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%2Fwealthreader.com%2Fwealthreader" | 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%2Fwealthreader.com%2Fwealthreader" | 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 Wealth Reader API.
Obtiene los activos financieros y el detalle de su composición
Listado de códigos de error
Integrate Wealth Reader API into automated workflows
Query and filter Wealth Reader API records by parameters
Monitor Wealth Reader API operational status and events
GET STARTED
Patterns agents use Wealth Reader API for, with concrete tasks.
★ Finance and Accounting Operations
Use the Wealth Reader API to perform finance operations programmatically. The API provides 3 endpoints covering core functionality including obtiene los activos financieros y el detalle de su composición, obtiene el listado de entidades soportadas, listado de códigos de error.
Call POST /entities to obtiene los activos financieros y el detalle de su composición
Automated entity-data Management
Automate entity-data operations by combining multiple Wealth Reader API endpoints. Agents can obtiene el listado de entidades soportadas and then listado de códigos de error in a single workflow.
Call GET /entities to obtiene el listado de entidades soportadas, then verify the result
AI Agent Integration via Jentic
AI agents discover and call Wealth Reader 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 none tokens manually.
Search Jentic for 'obtiene los activos financieros y el detalle de su composición', load the operation schema, and execute with Jentic-managed credentials
3 endpoints — las apis regulatorias basadas en psd2 proporcionan acceso a cierta información financiera como saldos de cuentas bancarias y transacciones.
METHOD
PATH
DESCRIPTION
/entities
Obtiene los activos financieros y el detalle de su composición
/entities
Obtiene el listado de entidades soportadas
/error-codes
Listado de códigos de error
/entities
Obtiene los activos financieros y el detalle de su composición
/entities
Obtiene el listado de entidades soportadas
/error-codes
Listado de códigos de error
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Wealth Reader API by hand means pointing at its host, shaping the entities request, and handling responses yourself. Through Jentic you install once, import the Wealth Reader API from the API Directory, configure it once, and your agent calls it.
Permission scoping
This API carries its target in the request body rather than in the URL path, so limit the agent to the operations it needs, such as creating or listing entities. You choose the operations it may call, so anything beyond what you enable is not available.
Credential isolation
Any account values this API needs 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 'retrieve financial assets' or 'list entities', and Jentic returns the matching Wealth Reader 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.
Specific to using Wealth Reader API through Jentic.
What authentication does the Wealth Reader API use?
The Wealth Reader API uses no 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 obtiene los activos financieros y el detalle de su composición with the Wealth Reader API?
Yes. Use the POST /entities endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the Wealth Reader 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 obtiene los activos financieros y el detalle de su composición through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'obtiene los activos financieros y el detalle de su composición'. Jentic returns the matching Wealth Reader API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the Wealth Reader API have?
The Wealth Reader API exposes 3 endpoints covering entity-data, usage-data operations.
Can I limit what my agent is allowed to do with the Wealth Reader API?
Yes. Because you run Jentic One yourself, your own rules decide which Wealth Reader operations the agent can call, so you can enable just the ones it needs, such as GET /entities to list supported entities while withholding POST /entities that retrieves financial assets. Since this API carries its target in the request body rather than the URL path, scoping is done at the operation level: any endpoint you do not enable, including GET /error-codes, stays unavailable to the agent. The account values the API requires are held encrypted by your instance and injected only at execution time, so the agent never sees the raw credentials.
For Agents
Programmatically obtiene los activos financieros y el detalle de su composición, obtiene el listado de entidades soportadas. Covers 3 operations.
Use for: I need to obtiene los activos financieros y el detalle de su composición, I want to obtiene el listado de entidades soportadas, Search for listado de códigos de error, List all records from Wealth Reader API
Not supported: Does not handle payments, communications, or crm - use for finance and accounting only.
Las APIs regulatorias basadas en PSD2 proporcionan acceso a cierta información financiera como saldos de cuentas bancarias y transacciones. Sin embargo, hay otras fuentes de información patrimonial que no son accesibles por estas APIs. La API de Wealth Reader amplía la información ofrecida por las APIs regulatorias proporcionando acceso en tiempo real a las fuentes patrimoniales adicionales en cua. The API exposes 3 endpoints.
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>