Ola CV Domain API

Name: Ola CV Domain API
Brand: Ola CV Domain API
Availability: InStock

✓ Official Vendor SpecCloud InfrastructureNetworkingbearer18 EndpointsREST

For Agents

Install Jentic One Beta

Connect the Ola CV Domain API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Ola CV Domain 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.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic 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 Ola CV Domain API.

Check whether a .cv domain is available for registration

Renew an existing .cv domain for a chosen term

Create and update DNS zones for a registered domain

GET STARTED

Start building with Ola CV Domain API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Ola CV Domain API for, with concrete tasks.

★ Domain registration and renewal automation

Automate .cv domain lifecycle management for hosting providers and resellers. Check availability, create the registrant contact, register the domain, and schedule renewal — all through API calls rather than the Ola.cv web UI. New customer onboarding for a .cv domain drops from a multi-step manual process to a single sequence of API calls.

Check availability of a .cv domain, create or reuse a registrant contact, then call POST /domains to register the domain for one year

DNS provisioning for new sites

When provisioning a new site, automate the DNS layer by creating a zone for the domain and inserting the A, CNAME, and MX records the application needs. The DNS-record endpoints support standard record types and TTL control, so a deployment workflow can ship infrastructure and DNS in one motion.

Create a DNS zone for a newly registered domain and insert an A record for the apex and a CNAME record for www

Bulk DNS migrations

When a team migrates a .cv domain to a new mail provider or CDN, update MX or CNAME records across many zones programmatically. The list, update, and delete endpoints on DNS records let a migration script touch each affected record without manual editing in the registrar UI.

List all MX records under a zone, delete the existing entries, and create new MX records pointing to a different mail provider

AI agent domain assistant via Jentic

An AI agent acting as an infrastructure assistant uses Jentic to manage .cv domains and DNS without holding the bearer token directly. The agent searches Jentic for an intent like 'check .cv domain availability' or 'add a DNS record', loads the schema, and executes through the Jentic vault.

Search Jentic for 'add DNS record', load the schema for the create-record operation, and execute it with the zone, name, type, and value supplied by the user

Key Endpoints

18 endpoints — ola.

METHOD

PATH

DESCRIPTION

GET

/domains/check

Check whether a .cv domain is available

POST

/domains

GET

/domains/{id}

Retrieve a domain by ID

POST

/domains/{id}/renew

Renew a domain

GET

/domains/{id}/zone

Retrieve the DNS zone for a domain

GET

/zones

List DNS zones

GET

/contacts

List contact records

GET

/domains/check

Check whether a .cv domain is available

POST

/domains

GET

/domains/{id}

Retrieve a domain by ID

POST

/domains/{id}/renew

Renew a domain

GET

/domains/{id}/zone

Retrieve the DNS zone for a domain

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Ola.cv bearer tokens are stored encrypted in the Jentic vault. The Authorization header is constructed at request time with a scoped execution token, so the agent never holds the raw bearer value.

Intent-based discovery

Eighteen endpoints span domains, zones, records, and contacts. Agents search Jentic by intent (for example 'register a .cv domain' or 'add an A record') and Jentic returns the matching operation with the right path and method.

Time to first call

Direct integration including token provisioning, contact-record bootstrap, and DNS-record schema reading: half a day to a day. Through Jentic: under 30 minutes.

FAQs

Specific to using Ola CV Domain API through Jentic.

What authentication does the Ola CV Domain API use?

The API uses bearer-token authentication; pass your Ola.cv API token in the Authorization header as 'Bearer {token}'. Through Jentic, the token is stored encrypted in the vault and injected at request time, so the raw token never enters the agent's context.

Can I check .cv domain availability with the API?

Yes. GET /domains/check with the candidate domain name returns whether it is available for registration along with registry pricing where applicable. Use this before calling POST /domains to avoid registration attempts that will be rejected.

What are the rate limits for the Ola CV Domain API?

Ola.cv applies per-account rate limits intended to prevent abusive availability scanning. The current spec does not publish exact thresholds. Cache availability results, throttle bulk checks, and back off on 429 to stay within the limits.

How do I add a DNS record through Jentic?

Search Jentic for 'add DNS record', load the schema for the create-record operation under /zones/{id}/records (or the equivalent path), and execute with the record name, type (A, CNAME, MX, etc.), value, and TTL. Jentic handles the bearer header and returns the created record's ID.

Does the Ola CV Domain API support contact management?

Yes. The /contacts endpoints let you create, list, retrieve, and update registrant, admin, and tech contact records. Reusable contact IDs can be passed when registering new domains, so a hosting provider does not need to re-enter registrant data per registration.

Can I renew a .cv domain through the API?

Yes. POST /domains/{id}/renew with the desired term renews the domain and applies the registry charge. Combine with a scheduled job that lists domains nearing expiry to automate renewals across a portfolio.

Ola CV Domain API

Connect the Ola CV Domain API to your agent

Capabilities

Start building with Ola CV Domain API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs