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.