Is there a LiquidCompute MCP server?

You don't need an MCP server to give your agent the LiquidCompute API. Jentic connects it directly from the API Directory: import it, store your API key once, and your agent discovers the index and GPU price operations on demand.

Can I get current H100 prices with the LiquidCompute API?

Yes. The current GPU prices operation returns the comparable vendor offers from the newest completed price scrape, normalized to USD per GPU-hour. For one model over time, the GPU price history operation takes gpu_model, such as h100, with a start and end date, and the changes operation lists price moves since a date.

What are the rate limits for the LiquidCompute API?

Per the spec, limits are token buckets per API key: you can burst up to your bucket size and sustain your refill rate. The X-RateLimit-Limit, X-RateLimit-Remaining, and X-RateLimit-Reset headers report your bucket, and Retry-After is set on 429 responses. The spec does not publish the bucket sizes; see https://docs.liquidcompute.com for your plan.

Can I limit what my agent is allowed to do with the LiquidCompute API?

Yes. The API is read-only, so the question is which data your agent may read. For example, allow only the current GPU prices and transaction index operations, so the agent can answer pricing questions while private transactions and commitment pricing stay outside its reach. Every call it makes is logged.

How do I read the GPU transaction index through Jentic?

Search Jentic for 'get the GPU transaction index', load the current transaction index operation, and pass filters such as gpu_family hopper, region_group US, and contract_type combined. Jentic injects your X-API-Key at call time. To run it on your own infrastructure, install Jentic One from its GitHub repo.