Can I create a cloud instance with the OVHcloud API?

Yes. The cloud instance operation creates an instance in a project from a chosen flavor and image, and companion operations list flavors, images, and the resulting instance so you can confirm it came up. Volumes and private networks are managed through their own operations in the same project.

What are the rate limits for the OVHcloud API?

The OpenAPI spec does not specify rate limits; OVHcloud applies limits per application and account. Current limits are documented in the vendor documentation at https://api.ovh.com/.

How do I manage DNS with the OVHcloud API through Jentic?

Install Jentic One with `curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh`, import OVHcloud from the API Directory, and store your application key once. Your agent then searches for an intent such as 'add a DNS record', and Jentic returns the matching operation with its input schema. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Is there an OVHcloud MCP server?

You do not need an MCP server to give your agent the OVHcloud API. Jentic connects it directly from the API Directory: import the API, store your key once, and your agent calls the cloud, DNS, and billing operations on demand, which keeps your agent's context free of an extra server's tool definitions.

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

Yes. OVHcloud is a large write-capable API, so you can allow your agent just the operations a task needs, such as listing servers and reading bills, and leave out destructive ones like deleting an instance or terminating a dedicated server. Because you run Jentic One yourself, the agent operates only within the operation set you grant, and every call is logged.