canonical: https://jentic.com/apis/amana-dev.com/amana-dev # Amana Dev Amana API 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. ## For AI 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. ## Scope Does not handle tax filing, accounting, or card payment processing. Use for trading-platform onboarding, KYC, account data, alerts, and market context only. ## Capabilities - 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 - List events relevant to the authenticated user ## Use cases ### 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. Example prompt: 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. Example prompt: 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. Example prompt: Retrieve the current trending symbols and market sentiment and summarize them for the user ## Key endpoints | 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 | ## Key resources - **Auth** — Authenticate users through password, social login, and signup, and manage sessions - **Onboarding & KYC** — Step users through country-specific KYC onboarding and read status - **DriveWealth** — Read a connected brokerage account, statements, and violations - **Alerts** — Set, update, and clear price alerts for symbols - **Market data** — Retrieve trending symbols, market sentiment, and user events ## AI readiness 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. - **Score:** 38 / 100 - **Maturity:** Non-Ready - **Dimensions:** - Foundational Compliance: 49 / 100 - Developer Experience & Jentic Compatibility: 62 / 100 - AI-Readiness & Agent Experience: 19 / 100 - Agent Usability: 82 / 100 - Security: 75 / 100 - AI Discoverability: 34 / 100 - **View full report:** https://jentic.com/apis/amana-dev.com/amana-dev/scorecard - **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/ - **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview ### Score it yourself Every API in the directory is allowlisted, so you can re-score it with no key required. - **Score your own API:** https://jentic.com/scorecard.md - **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md ```sh npx @jentic/api-scorecard-cli score ``` ## Why Jentic - **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 handling:** 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. - **Discovery method:** 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. ## Related APIs - **Alpaca Trading** — Alpaca offers brokerage account and trading APIs as an alternative platform for retail investing - **Plaid** — Plaid links bank accounts and verifies identity data that can feed a KYC onboarding flow - **Finnhub** — Finnhub provides broad market data and fundamentals beyond Amana's trending and sentiment signals ## FAQ ### 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.