Cryptocurrency Alerting API

Name: Cryptocurrency Alerting API API
Brand: Cryptocurrency Alerting API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentDeveloper ToolsMonitoring Observabilitybasic5 EndpointsREST

For Agents

Create, list, update, and delete cryptocurrency price and on-chain alert conditions for an existing Cryptocurrency Alerting account.

Quickstart

Get started with Cryptocurrency Alerting API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"create a crypto price alert"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Cryptocurrency Alerting API API.

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

GET STARTED

Start building with Cryptocurrency Alerting API API

Explore with Jentic

View OpenAPI Document

Use for: I need to create a price alert for when BTC crosses 100,000 USD, Set up a percent-change alert for ETH moving more than 5 percent in an hour, Monitor a specific Bitcoin address for incoming transactions, Get the details of all active alert conditions on my account

Not supported: Does not execute trades, hold custody of crypto, or run portfolio analytics — use for crypto alert condition management only.

Jentic publishes the only available OpenAPI document for Cryptocurrency Alerting API, keeping it validated and agent-ready.

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.

Use Cases

Patterns agents use Cryptocurrency Alerting API API for, with concrete tasks.

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

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.

Call POST /alert-conditions with type=wallet, asset=BTC, address=<cold-storage>, 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.

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.

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

5 endpoints — the cryptocurrency alerting api lets developers create and manage alert conditions on cryptocurrency markets and on-chain events.

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

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

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Cryptocurrency Alerting Basic auth credentials are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped tokens and never see the underlying username and password.

Intent-based discovery

Agents search by intent (for example 'create a crypto price alert' or 'monitor a wallet address') and Jentic returns the matching alert-conditions operation with its input schema.

Time to first call

Direct Cryptocurrency Alerting integration: half a day for auth setup and channel wiring. Through Jentic: under 15 minutes — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

CoinGecko API

Market data feed for crypto prices and exchange rates

Use CoinGecko alongside Cryptocurrency Alerting when the agent needs to compute or visualise the price series that an alert is based on.

Complementary

CoinAPI

Consolidated market data and historical OHLC across exchanges

Use CoinAPI when the agent needs cross-exchange data to set the alert threshold rather than just monitoring a single market.

Alternative

Crypto APIs Blockchain REST API

Blockchain data API with its own confirmation callbacks

Choose Crypto APIs when the use case is on-chain confirmation webhooks rather than market price thresholds.

FAQs

Specific to using Cryptocurrency Alerting API API through Jentic.

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.