canonical: https://jentic.com/apis/dripmetrics.ai/dripmetrics # DripMetrics API The DripMetrics API computes crypto market microstructure, risk, and on-chain metrics on demand and returns them as structured JSON. It covers microstructure signals such as VPIN, Kyle's lambda, and order-flow imbalance, risk measures such as realized volatility, drawdown, and beta, order-book analytics, BTC options greeks, and venue-specific metrics for Hyperliquid, Polymarket, Kraken xStocks, and Aerodrome. Discovery endpoints are free and paid computations are priced per call with the x402 protocol, so there are no subscriptions or long-lived API keys to manage. ## For AI agents Compute crypto market microstructure, risk, order-book, options, prediction-market, and on-chain metrics on demand, returned as structured JSON. Discovery is free and paid computations are priced per call with the x402 protocol. ## Scope Does not handle trade execution, order placement, or portfolio custody. Use for computing crypto market microstructure, risk, and on-chain metrics only. ## Capabilities - Compute market microstructure metrics such as VPIN, Kyle's lambda, and order-flow imbalance for crypto pairs - Measure risk with realized volatility, drawdown, beta, and vol-of-vol metrics - Analyze order-book state with spread, micro-price, imbalance, and depth-at-distance metrics - Score Polymarket prediction markets with flow imbalance, wallet concentration, and probability-shock metrics - Read on-chain metrics including stablecoin flow, TVL momentum, and DEX efficiency - Compute BTC options analytics such as expected move, variance risk premium, and gamma exposure - Pull Hyperliquid, Kraken xStocks, and Aerodrome venue-specific microstructure and flow metrics ## Use cases ### Agent-driven crypto risk analysis An AI agent connected through Jentic can assess the risk profile of a crypto asset without running its own quant pipeline. It computes realized volatility, drawdown, and vol-of-vol for a pair, pulls VPIN and order-flow imbalance to gauge toxicity, and returns a single structured summary, turning a research question into a set of on-demand metric calls. Example prompt: Compute realized volatility, drawdown, and VPIN for a given crypto pair over a chosen window and summarize whether the market looks stressed. ### Prediction-market signal monitoring DripMetrics exposes Polymarket-specific metrics such as flow imbalance, wallet concentration, two-sidedness, and probability shock. An agent can watch a market for a sudden probability shock or a spike in wallet concentration and flag it, giving prediction-market traders a programmatic early-warning signal rather than manual chart watching. Example prompt: Pull the probability-shock and wallet-concentration metrics for a Polymarket market and alert if either crosses a threshold. ### Execution cost estimation The order-book endpoints compute spread, micro-price, imbalance, depth-at-distance, and execution impact from live book state. An agent sizing a trade can estimate the execution impact of a given order size and read the current spread and imbalance, so it can decide whether to split an order before sending it to an execution venue. Example prompt: Read the order-book spread, imbalance, and execution impact for a target size on a market and report the estimated cost to fill. ### On-chain and options analytics DripMetrics computes on-chain metrics such as stablecoin flow, TVL momentum, protocol fee yield, and DEX efficiency, plus BTC options analytics including variance risk premium, crash premium, and gamma exposure. An agent can combine an on-chain flow reading with an options positioning signal to build a cross-market view in one pass. Example prompt: Read the on-chain stablecoin flow and the BTC options gamma exposure, then summarize the combined positioning signal. ## Key endpoints | Method | Path | Description | | --- | --- | --- | | GET | `/catalog` | List available metrics, exchanges, windows, and pricing | | GET | `/metrics/vpin` | Compute VPIN for a crypto pair | | GET | `/metrics/realized-vol` | Compute realized volatility | | GET | `/metrics/vwap` | Compute VWAP | | GET | `/orderbook/imbalance` | Compute order-book imbalance | | GET | `/polymarket/probability-shock` | Compute Polymarket probability shock | | GET | `/options/expected-move` | Compute BTC options expected move | | GET | `/metrics/onchain/stablecoin-flow` | Compute on-chain stablecoin flow | ## Key resources - **Microstructure Metrics** — Compute VPIN, Kyle's lambda, CVD, trade intensity, and other microstructure signals for crypto pairs - **Risk & Volatility** — Compute realized and historical volatility, drawdown, beta, momentum, reversal, and vol-of-vol - **Order Book** — Compute spread, micro-price, imbalance, depth-at-distance, concentration, and execution impact - **Options & On-chain** — Compute BTC options greeks and expected move, plus on-chain stablecoin flow, TVL momentum, and DEX efficiency - **Venue Metrics** — Read Hyperliquid, Polymarket, Kraken xStocks, and Aerodrome venue-specific microstructure and flow metrics - **Discovery** — List the available metrics, exchanges, windows, and pricing through the free catalog endpoints ## 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:** 62 / 100 - **Maturity:** AI-Aware - **Dimensions:** - Foundational Compliance: 74 / 100 - Developer Experience & Jentic Compatibility: 70 / 100 - AI-Readiness & Agent Experience: 49 / 100 - Agent Usability: 90 / 100 - Security: 50 / 100 - AI Discoverability: 54 / 100 - **View full report:** https://jentic.com/apis/dripmetrics.ai/dripmetrics/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 DripMetrics by hand means implementing the x402 per-call payment flow for paid endpoints, deciding which of its dozens of metric routes you need, and reading the catalog for current pricing. Through Jentic you install once, import DripMetrics from the API Directory, configure the payment credential once, and your agent calls it. - **Permission scoping:** DripMetrics takes the instrument, exchange, and window as query parameters rather than URL-path resources, so rules bound which metric operations your agent may call, not which market it reads. Every paid endpoint is a read-only computation, so you allow exactly the metrics the agent needs and nothing else. - **Credential handling:** The payment credential your agent uses for x402 is held 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 'compute VPIN for a crypto pair' or 'measure realized volatility', and Jentic returns the matching DripMetrics operation with its input schema so the agent calls the right metric without scanning the full route list. ## Related APIs - **BraveNewCoin** — BraveNewCoin provides crypto market data and indices, overlapping DripMetrics' analytics output - **CoinAPI** — CoinAPI supplies raw trade and order-book data that underpins the kind of metrics DripMetrics computes - **CoinGecko** — CoinGecko covers prices, market caps, and token metadata that complement DripMetrics' risk metrics - **Alpaca Trading** — Alpaca executes trades, the step DripMetrics does not perform after it computes a signal ## FAQ ### What authentication does the DripMetrics API use? Discovery endpoints such as the catalog and health checks are free and need no credential. Paid computation endpoints use the x402 payment protocol, where the request carries a PAYMENT-SIGNATURE header to authorize a per-call micropayment rather than an API key or subscription, per the OpenAPI spec. Through Jentic the payment credential your agent presents is held by your own Jentic One instance and injected at call time, so it never reaches the agent's context. ### Is there a DripMetrics MCP server? Yes, DripMetrics offers an MCP server with free discovery tools at its own endpoint. You can also connect DripMetrics directly through Jentic: your agent gets the full 73-endpoint surface without loading another server's tool definitions into its context, the payment credential is injected at call time by your self-hosted instance, and your rules decide which metric operations the agent may call. ### Can I limit what my agent is allowed to do with the DripMetrics API? Yes. Write a rule that allows only the metric operations your agent needs, such as the volatility and order-book reads, so it computes the signals you intend and nothing else, and every call it makes is logged. Because every paid endpoint is a read-only computation that takes its inputs as query parameters, scoping is about which metrics the agent may call, not which market it touches. ### Can I compute order-book metrics with the DripMetrics API? Yes. The order-book endpoints compute spread, micro-price, imbalance, depth-at-distance, concentration, and execution impact from book state. An agent sizing a trade can read the execution-impact metric for a target order size to estimate the cost of filling before it routes the order to a venue. ### What are the rate limits for the DripMetrics API? This OpenAPI spec does not specify request rate limits; access to paid endpoints is gated by per-call x402 payment rather than a request quota. Check the pricing returned by the catalog endpoint for the current per-metric cost, and the DripMetrics documentation for any usage limits. ### How do I compute a metric with the DripMetrics API through Jentic? Install Jentic One, import DripMetrics from the API Directory, and configure the payment credential once. Your agent then searches by intent, for example 'compute VPIN for a crypto pair', and Jentic returns the matching metric endpoint with its input schema. To run it on your own infrastructure, install Jentic One from its GitHub repo.