canonical: https://jentic.com/apis/ovh.com/ovh

# Ovh OVHcloud API

The OVHcloud API manages public cloud, dedicated servers, VPS, domains, DNS, IP addresses, SSL certificates, and billing across OVHcloud regions. It provisions and controls cloud instances, volumes, and private networks, reboots and reinstalls dedicated servers and VPS, and edits DNS zones and records including DNSSEC and reverse DNS. Account operations expose bills, orders, debt, and SSL certificate status so infrastructure and spend can be driven together.

## For AI agents

Provision cloud instances, manage dedicated servers and VPS, edit DNS and IP configuration, and read billing across OVHcloud. Authenticates with an application key.

## Scope

Does not handle application code deployment, container orchestration, or managed databases. Use for OVHcloud infrastructure, DNS, and account management only.

## Capabilities

- Provision and manage public cloud instances, volumes, and private networks
- List and reboot dedicated servers and track their provisioning tasks
- Start, stop, and reinstall VPS instances and manage their snapshots
- Manage DNS zones and records, including DNSSEC and reverse DNS
- Configure IP firewall rules, reverse DNS, and DDoS mitigation
- Read account billing, orders, and SSL certificate status

## Use cases

### AI Agent Infrastructure Operations

An AI agent running ops tasks can create instances, manage DNS, and check billing across OVHcloud through Jentic. The agent searches for the operation it needs, supplies the service name and parameters, and runs the call, without the developer hand-building the application key header or paging through the OVHcloud reference docs.

Example prompt: Call POST `/cloud/project/{serviceName}/instance` to create a new instance in a project

### DNS Automation

DevOps pipelines keep DNS in sync with deployments. OVHcloud exposes zone and record operations, so an agent can add an A record for a new service, refresh the zone, and confirm the change through the zone status operation.

Example prompt: Call POST `/domain/zone/{zoneName}/record` to add a DNS record, then POST `/domain/zone/{zoneName}/refresh`

### Server Fleet Management

Teams managing bare-metal and virtual fleets reboot, reinstall, and inspect machines at scale. OVHcloud lists dedicated servers and VPS instances and exposes reboot, reinstall, and task-tracking operations, so an agent can act on a host and watch the resulting task to completion.

Example prompt: Call GET `/dedicated/server` to list servers, then POST `/dedicated/server/{serviceName}/reboot` to reboot one

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/cloud/project` | List public cloud projects |
| POST | `/cloud/project/{serviceName}/instance` | Create a cloud instance |
| GET | `/domain/zone/{zoneName}/record` | List DNS records in a zone |
| POST | `/domain/zone/{zoneName}/record` | Create a DNS record |
| GET | `/dedicated/server` | List dedicated servers |
| GET | `/vps` | List VPS instances |
| GET | `/ip` | List IP addresses |
| GET | `/me/bill` | List account bills |

## Key resources

- **Cloud** — Public cloud projects, instances, volumes, networks, and snapshots
- **Dedicated and VPS** — Dedicated servers and VPS instances with reboot, reinstall, and task tracking
- **Domain and DNS** — DNS zones, records, DNSSEC, and domain name servers
- **IP** — IP blocks, firewall rules, reverse DNS, and DDoS mitigation
- **Account** — Billing, orders, debt, and SSL certificates

## 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:** 66 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 99 / 100
  - Developer Experience & Jentic Compatibility: 63 / 100
  - AI-Readiness & Agent Experience: 52 / 100
  - Agent Usability: 84 / 100
  - Security: 50 / 100
  - AI Discoverability: 79 / 100
- **View full report:** https://jentic.com/apis/ovh.com/ovh/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 <openapi-url>
```

## Why Jentic

- **Setup:** Wiring the OVHcloud API by hand means signing requests with your application key, choosing the right regional host for your account, and tracking asynchronous server tasks yourself. Through Jentic you install once, import OVHcloud from the API Directory, store the key once, and your agent calls it.
- **Permission scoping:** OVHcloud puts the service name in the URL path, so a rule can keep your agent on the operations and services you pick, such as reading cloud projects and DNS records. You choose the operation set, so destructive operations like deleting an instance or terminating a dedicated server are not included unless you add them.
- **Credential handling:** Your OVHcloud application key is stored once, encrypted, 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 'create a cloud instance' or 'add a DNS record', and Jentic returns the matching OVHcloud operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **DigitalOcean** — Cloud droplets, networking, and managed services
- **Linode** — Linux cloud compute, storage, and networking
- **Cloudflare** — DNS, CDN, and edge security in front of your infrastructure

## FAQ

### What authentication does the OVHcloud API use?

The OVHcloud API authenticates with an application key sent in the `X-Ovh-Application` header, per its OpenAPI spec; most operations require it, while the credential-request and server-time endpoints are open. Through Jentic the key is stored encrypted by your own Jentic One instance and injected at call time, so it never enters the agent's prompt or logs.

### 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.