DripMetrics API
62
AI ReadinessAI-Aware (B-)62/100
Official vendor OpenAPI document · agent-readyAnalyticsBusiness Intelligencex40273 EndpointsREST
For 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.
Use for: Compute VPIN for a crypto trading pair, Measure the realized volatility of an asset, Get the order-book imbalance for a market, Score a Polymarket market for probability shocks
Not supported: Does not handle trade execution, order placement, or portfolio custody. Use for computing crypto market microstructure, risk, and on-chain metrics only.
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.
Install Jentic One Beta
Connect the DripMetrics API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the DripMetrics 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.
1
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%2Fdripmetrics.ai%2Fdripmetrics" | sh2
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%2Fdripmetrics.ai%2Fdripmetrics" | sh
jentic register # connects your agent to your Jentic One instanceJentic 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 DripMetrics API.
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
Patterns agents use DripMetrics API for, with concrete tasks.
★ 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.
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.
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.
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.
Read the on-chain stablecoin flow and the BTC options gamma exposure, then summarize the combined positioning signal.
Key Endpoints
73 endpoints — the dripmetrics api computes crypto market microstructure, risk, and on-chain metrics on demand and returns them as structured json.
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
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
Jentic AI Readiness Score
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.
D
DripMetrics API
- AI-Aware (B-)62/100
74
Foundational Compliance70
Developer Experience & Jentic Compatibility49
AI-Readiness & Agent Experience90
Agent Usability50
Security54
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.2
Show dimension breakdown
74
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: A-Signals: 4
95%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
0%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
100%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
70
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: A-Signals: 4
9%
Example Density
How richly the API is illustrated with examples.
100%
Example Validity
Percentage of examples that conform to their schemas.
72%
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.
49
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: D+Signals: 4
46%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
100%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
49%
Summary Coverage
Coverage of summaries across operations/tags/info.
90
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: A+Signals: 1
90%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
50
Security
Trust, risk posture, and security compliance.
Grade: C-Signals: 1
50%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
54
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: CSignals: 1
54%
Descriptive Richness
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
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 isolation
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.
Intent-based discovery
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
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using DripMetrics API through Jentic.
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.
GET STARTED