Install Jentic One Beta

Connect the Amana API to your agent

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

Authenticate a user through password, social login, or social signup

Step a user through KYC onboarding forms by country and entity

Read a connected DriveWealth brokerage account, statements, and violations

Set a price alert for a symbol and adjust or clear it later

Retrieve trending symbols and current market sentiment

GET STARTED

Start building with Amana API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Amana API for, with concrete tasks.

★ Agent-driven trading onboarding

An AI agent connected through Jentic guides a new user through signup and verification: it authenticates the account, advances the KYC forms for the user's country, and checks onboarding status until the brokerage account is ready. Because the agent discovers operations by intent, a conversational onboarding flow can complete the DriveWealth-backed signup without a developer wiring each KYC step.

Authenticate a user, submit the next KYC onboarding step for their country, and poll the KYC status until it reports ready

Price alert management

Users can have an agent watch the market for them by setting and maintaining price alerts. The agent creates an alert for a symbol, adjusts the threshold as conditions change, and clears alerts that are no longer needed. This turns manual alert upkeep into something the agent handles on request against the user's own account.

Create a price alert for a symbol at a target price, then update that alert to a new threshold

Market context lookups

The API supplies the market context an assistant needs to answer a user: trending symbols, market sentiment, and the events relevant to that user. An agent can pull this read-only data to brief the user before they act, grounding its answer in Amana's live market signals rather than stale information.

Retrieve the current trending symbols and market sentiment and summarize them for the user

Key Endpoints

109 endpoints — the amana api powers onboarding and account access for a retail trading platform backed by drivewealth brokerage accounts.

METHOD

PATH

DESCRIPTION

POST

/auth/login

Authenticate a user

GET

/trending

Get trending symbols

GET

/alerts/

List the user's price alerts

POST

/alerts/

Create a price alert

GET

/asset-info/market-sentiment

Get market sentiment data

GET

/drivewealth/dw/account

Read DriveWealth account data

GET

/kyc/status

Get the user's KYC status

POST

/auth/login

Authenticate a user

GET

/trending

Get trending symbols

GET

/alerts/

List the user's price alerts

POST

/alerts/

Create a price alert

GET

/asset-info/market-sentiment

Get market sentiment data

GET

/drivewealth/dw/account

Read DriveWealth account data

GET

/kyc/status

Get the user's KYC status

Why Jentic?

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

Setup

Wiring the Amana API by hand means handling its bearer-token login, threading the token through KYC and account calls, and tracking onboarding state yourself. Through Jentic you install once, import the API from the Directory, store the token once, and your agent calls it.

Permission scoping

Amana carries its request targets in the body rather than the URL path, so rules bound which operations your agent may call: you can allow market-data reads and alert operations while leaving KYC and account changes out unless you add them. You choose the operations it may use.

Credential isolation

The user's bearer token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'set a price alert' or 'get market sentiment', and Jentic returns the matching Amana operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Amana API through Jentic.

What authentication does the Amana API use?

The Amana API authenticates with a bearer token sent in the Authorization header, as declared in its OpenAPI spec, and issues that token through its login and social login flows. Through Jentic the token is stored once by your own self-hosted instance and injected at call time, so it never appears in the agent's prompt or logs.

Can I manage price alerts with the Amana API?

Yes. You can create a price alert for a symbol, update its threshold, and delete it when it is no longer needed. The alerts belong to the authenticated user, so the agent operates on that user's own watchlist.

Is there an Amana API MCP server?

You do not need an MCP server to give your agent the Amana API. Jentic connects it directly from the API Directory: import the API, store your bearer token once, and your agent calls onboarding, alerts, and market operations on demand without loading another server's tool definitions into its context.

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

Yes. Write a rule that allows only the market-data reads and alert operations, so the agent can brief the user and manage alerts but cannot touch KYC or account changes you did not approve, and every call it makes is logged for review. Amana carries its targets in the request body, so rules bound which operations the agent may call.

What are the rate limits for the Amana API?

The OpenAPI spec does not specify rate limits for the Amana API. Check the vendor documentation for current limits before polling market data or alerts frequently.

How do I onboard a trading user with the Amana API through Jentic?

Search Jentic for an intent such as 'submit a KYC onboarding step', and it returns the matching operation with its input schema so your agent advances onboarding with the right fields. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Amana Dev Amana API

AI ReadinessNon-Ready (F)38/100

See full scorecard

Community OpenAPI document · agent-readyFinanceBankingbearer109 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Onboard and authenticate trading users, run KYC steps, read DriveWealth brokerage account data and statements, set price alerts, and pull trending symbols and market sentiment.

Use for: I need to authenticate a user with their email and password, Set a price alert for a stock symbol, Get the trending symbols right now, Retrieve the KYC status for a user's onboarding

Not supported: Does not handle tax filing, accounting, or card payment processing. Use for trading-platform onboarding, KYC, account data, alerts, and market context only.

The Amana API powers onboarding and account access for a retail trading platform backed by DriveWealth brokerage accounts. It authenticates users through password and social login, steps them through KYC onboarding by country, and reads their brokerage account data, statements, and violations. For market context it serves trending symbols, market sentiment, and user-relevant events, and it lets a user set and manage price alerts.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: D+Signals: 4

71%

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

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.

49%

Response Coverage

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

100%

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

17%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

40%

OperationId Quality

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

17%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: ASignals: 1

82%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: A-Signals: 1

75%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: FSignals: 1

34%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Amana API to your agent

Capabilities

Start building with Amana API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Amana Dev Amana API

Jentic AI Readiness Score

Amana 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