Install Jentic One Beta

Connect the WealthOS API to your agent

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

Wealth Manager Greeting for BE

Create Investor

Get All Investors

Update Investor

Monitor WealthOS API operational status and events

Use Cases

GET STARTED

Start building with WealthOS API

Explore with Jentic One

View OpenAPI Document

Automated Investors Management

Automate investors operations by combining multiple WealthOS API endpoints. Agents can create investor and then get all investors in a single workflow.

Call POST /tenant/investors/v1 to create investor, then verify the result

AI Agent Integration via Jentic

AI agents discover and call WealthOS 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 apiKey tokens manually.

Search Jentic for 'wealth manager greeting for be', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

79 endpoints — welcome to wealthos.

METHOD

PATH

DESCRIPTION

GET

/tenant/test/hello-world-be

Wealth Manager Greeting for BE

POST

/tenant/investors/v1

Create Investor

GET

/tenant/investors/v1

Get All Investors

GET

/tenant/investors/v1/{investor_id}

Get Investor

PATCH

/tenant/investors/v1/{investor_id}

Update Investor

GET

/tenant/financial-products/v1

Get All Financial Products

GET

/tenant/payments/v1/{transaction_id}

Get Payment by Transaction Id

POST

/tenant/pots/v1

Create new pots

GET

/tenant/test/hello-world-be

Wealth Manager Greeting for BE

POST

/tenant/investors/v1

Create Investor

GET

/tenant/investors/v1

Get All Investors

GET

/tenant/investors/v1/{investor_id}

Get Investor

PATCH

/tenant/investors/v1/{investor_id}

Update Investor

GET

/tenant/financial-products/v1

Get All Financial Products

GET

/tenant/payments/v1/{transaction_id}

Get Payment by Transaction Id

POST

/tenant/pots/v1

Create new pots

Why Jentic?

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

Setup

Wiring the WealthOS API by hand means learning its public key and secret key headers, resolving your tenant host, and handling responses yourself. Through Jentic you install once, import the WealthOS API from the API Directory, store those keys once, and your agent calls it.

Permission scoping

WealthOS puts the record id in the URL path (/tenant/investors/v1/{investor_id}, /tenant/payments/v1/{transaction_id}), so a rule can pin your agent to one investor or transaction and nothing else. You choose the operations it may call, so writes like creating an investor or a pot are not included unless you add them.

Credential isolation

Your WealthOS public and secret keys 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 'get an investor' or 'look up a payment', and Jentic returns the matching WealthOS operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using WealthOS API through Jentic.

What authentication does the WealthOS API use?

The WealthOS API uses an API key passed 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 wealth manager greeting for be with the WealthOS API?

Yes. Use the GET /tenant/test/hello-world-be endpoint. The API returns structured JSON responses that agents can parse and act on directly.

What are the rate limits for the WealthOS 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 wealth manager greeting for be through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'wealth manager greeting for be'. Jentic returns the matching WealthOS API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

How many endpoints does the WealthOS API have?

The WealthOS API exposes 79 endpoints covering investors, pots, holdings and transactions, recurring contributions operations.

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

Yes. Because you run Jentic One yourself, your own rules decide which WealthOS operations and credentials the agent may use. WealthOS puts the record id in the URL path, such as /tenant/investors/v1/{investor_id} and /tenant/payments/v1/{transaction_id}, so a rule can pin the agent to a single investor or transaction and nothing else. You choose the operations it can call, so write actions like creating an investor or a pot stay out of reach unless you explicitly grant them.

WealthOS API

AI ReadinessFoundational (C-)50/100

See full scorecard

Official vendor OpenAPI document · agent-readyDeveloper ToolsSource ControlapiKey79 EndpointsREST

For Agents

Programmatically wealth manager greeting for be, create investor. Covers 79 operations with apiKey authentication.

Use for: I need to wealth manager greeting for be, I want to investor, Search for all investors, Find all investor

Not supported: Does not handle payments, communications, or crm - use for developer tools only.

Welcome to WealthOS. Here you will find the comprehensive set of information you need to rapidly build rich digital wealth management features. Getting Started Before you start developing your features using the WealthOS API, please make sure that the following steps are complete: * Set-up your own environment unique to your organisation using the link we have provided * Follow the step-by-step [g. The API exposes 79 endpoints secured with apiKey authentication.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: D+Signals: 4

91%

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).

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

33%

Example Density

How richly the API is illustrated with examples.

98%

Example Validity

Percentage of examples that conform to their schemas.

75%

Response Coverage

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

87%

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

62%

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.

62%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: ASignals: 1

89%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: FSignals: 1

38%

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

Capabilities

Use Cases

Start building with WealthOS API

Key Endpoints

Why Jentic?

Related APIs

FAQs

WealthOS API

Jentic AI Readiness Score

WealthOS 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