canonical: https://jentic.com/apis/cryptocurrencyalerting.com/cryptocurrencyalerting # Cryptocurrency Alerting API The Cryptocurrency Alerting API lets developers create and manage alert conditions on cryptocurrency markets and on-chain events. Alerts cover price thresholds, percent change windows, wallet balance shifts, and Bitcoin mempool activity, and they can be delivered through email, SMS, Telegram, or webhook channels configured in the parent account. The API exposes five endpoints centred on the alert-conditions resource and authenticates with HTTP Basic credentials. ## For AI agents Create, list, update, and delete cryptocurrency price and on-chain alert conditions for an existing Cryptocurrency Alerting account. ## Scope Does not execute trades, hold custody of crypto, or run portfolio analytics - use for crypto alert condition management only. ## Capabilities - Create a price alert that fires when a cryptocurrency crosses an absolute threshold in a chosen quote currency - Create a percent-change alert that fires when an asset moves a defined percentage within a time window - Set up a wallet watch alert that fires when an address sends or receives a transaction - Configure a Bitcoin mempool alert that fires when fees or transaction backlog cross thresholds - List and inspect every active alert condition on the account, including its delivery channel - Pause, resume, or delete an alert condition without re-creating it from scratch ## Use cases ### Trader Price Alerts Power a trading dashboard that lets users define price thresholds and receive alerts on Telegram or email when the market crosses them. The API persists every alert as an alert-condition record and the parent service handles delivery, so the integrator only manages condition CRUD. Suitable for retail trading apps that do not want to build their own price monitoring infrastructure. Example prompt: Call POST /alert-conditions with type=price, asset=BTC, target=100000, and a delivery channel ID to create a one-shot price alert. ### Treasury Wallet Monitoring Watch corporate treasury wallets for unauthorised outflows. The agent registers a wallet alert on each cold-storage address and the API fires a webhook the moment any transaction touches it. This catches early signs of compromise long before exchanges credit deposits, and it works across multiple chains supported by the parent service. Example prompt: Call POST /alert-conditions with type=wallet, asset=BTC, address=, and a webhook delivery channel for the security incident response stack. ### Mempool Fee Strategy Time outbound Bitcoin transfers to avoid overpaying for confirmation. A Bitcoin mempool alert fires when the recommended fee drops below a target threshold or when the backlog clears, signalling a low-fee window. The same alert framework can also fire when fees spike so a user-facing app can warn customers before they broadcast. Example prompt: Call POST /alert-conditions with type=mempool, parameter=feeRate, threshold=20, and direction=below to alert when fees become favourable. ### AI Agent Crypto Monitoring An AI agent acting as a portfolio assistant can stand up custom alerts on demand. Through Jentic the agent searches for the right alert-conditions operation, loads its schema, and creates the alert with credentials from the vault. The user gets per-condition control without the agent ever seeing the raw Basic auth credentials. Example prompt: Search Jentic for 'create a crypto price alert', load the Cryptocurrency Alerting create operation, and execute it with the user's asset, target, and channel. ## Key endpoints | Method | Path | Description | | --- | --- | --- | | GET | `/alert-conditions` | List all alert conditions on the account | | POST | `/alert-conditions` | Create a new alert condition | | GET | `/alert-conditions/{id}` | Retrieve a single alert condition | | PATCH | `/alert-conditions/{id}` | Update or pause an alert condition | | DELETE | `/alert-conditions/{id}` | Delete an alert condition | ## Key resources - **Alert Conditions** — Create, list, retrieve, update, and delete every type of alert condition the account supports ## Why Jentic - **Setup:** Wiring the Cryptocurrency Alerting API by hand means encoding Basic auth credentials, pointing at the api.cryptocurrencyalerting.com/v1 host, and managing your own retries around alert-condition calls. Through Jentic you install once, import the Cryptocurrency Alerting API from the API Directory, store the username and password once, and your agent calls it. - **Permission scoping:** The alert condition id travels in the URL path (`/alert-conditions/{id}`), so a rule can pin your agent to one alert condition: it can read and update that condition and nothing else. You choose the operations it may call, so destructive ones like deleting an alert condition are not included unless you add them. - **Credential handling:** Your Cryptocurrency Alerting Basic auth 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. - **Discovery method:** Agents search Jentic by intent such as 'create a crypto price alert' or 'monitor a wallet address', and Jentic returns the matching alert-conditions operation with its input schema so the agent calls the right endpoint without browsing the reference docs. ## Related APIs - **CoinGecko API** — Market data feed for crypto prices and exchange rates - **CoinAPI** — Consolidated market data and historical OHLC across exchanges - **Crypto APIs Blockchain REST API** — Blockchain data API with its own confirmation callbacks ## FAQ ### What authentication does the Cryptocurrency Alerting API use? The API uses HTTP Basic authentication with credentials issued from the Cryptocurrency Alerting account dashboard. Through Jentic the credentials are stored in the vault and the agent only receives scoped access tokens. ### Can I create wallet monitoring alerts with the Cryptocurrency Alerting API? Yes. POST /alert-conditions accepts a wallet alert type with an address parameter, and the parent service watches the chain and fires the configured delivery channel when the address sends or receives funds. ### What are the rate limits for the Cryptocurrency Alerting API? The Cryptocurrency Alerting service does not publish a hard request rate limit, but condition counts are capped per plan. Inspect plan limits in the dashboard before creating a large batch of alerts programmatically. ### How do I create a price alert through Jentic? Search Jentic for 'create a crypto price alert', load the operation, and execute it against POST /alert-conditions with the asset, target, and configured delivery channel ID. Jentic supplies the Basic auth credentials from the vault. ### Is the Cryptocurrency Alerting API free? There is a free tier with a small monthly alert allowance and paid plans for higher volumes. Pricing is published at https://cryptocurrencyalerting.com/pricing. ### How do I pause an alert without deleting it? Call PATCH `/alert-conditions/{id}` (or the equivalent update path) with the disabled flag set. The condition stays on the account so it can be re-enabled later without re-entering thresholds. ### Can I limit what my agent is allowed to do with the Cryptocurrency Alerting API? Yes. Because you run Jentic One yourself, your own rules decide which alert-conditions operations and which Basic auth credentials the agent may use. Since the alert condition ID travels in the URL path (`/alert-conditions/{id}`), you can pin the agent to a single condition so it only reads and updates that one and touches nothing else. You choose the operations it may call, so a destructive path like DELETE `/alert-conditions/{id}` is excluded unless you explicitly add it.