Product

How Jentic Works

From API assessment to production deployment in four simple steps.

Product Overview

PLATFORM

Jentic OneSelf-hosted, open-source control plane between your agents and any APIAPI DirectoryBrowse 10,000+ APIs ready for AI agent integrationAPI ScorecardAssess your APIs for AI-readiness with automated scoringAgentic SandboxSafely simulate AI agents with your production APIsJenticSign in to the Jentic web app

CAPABILITIES

IntegrationConnect AI agents to your existing systemsWorkflowsDiscover and capture successful agent workflowsGovernanceDefine, observe, and enforce AI policies

TOOLS

Arazzo UIVisualize Arazzo workflows as interactive documentationArazzo EditorBuild and edit multi-step API workflows visually
Pricing
Developers

GET STARTED

DocumentationGuides and API referenceQuickstartGet up and running in minutes

COMMUNITY

GitHubOpen source projects and examples
Resources
BlogLatest articles and insightsPress & MediaBrand assets and press contactOpen StandardsBuilt on open specs. Never locked in.NewsletterAPIs, AI agents, mixed with architecture and strategy.
Company
About UsOur mission and teamCareersJoin our teamContactGet in touch
Install Jentic OneBook a Demo
How Jentic WorksJentic OneAPI DirectoryAPI ScorecardAgentic SandboxJenticIntegrationWorkflowsGovernanceArazzo UIArazzo Editor
Pricing
DocumentationQuickstartGitHub
BlogPress & MediaOpen StandardsNewsletter
About UsCareersContact
Request a demoInstall Jentic One
Jentic
For Enterprises
  • Product Overview
  • Agentic Sandbox
  • Book a Demo
For Developers
  • Jentic One
  • Documentation
  • GitHub
Company
  • About Jentic
  • Careers
  • Contact Us
ISO/IEC 27001:2022 certification badge issued by Prescient Security

Information Security Management System

Certified to ISO/IEC 27001:2022 by Prescient Security

Terms & Conditions•Privacy Policy•
© 2026 Jentic. All rights reserved.
APIs / Cloud Infrastructure / Alwaysdata API
Alwaysdata API logo

Alwaysdata API

★ Only Publicly Available OpenAPI DocumentCloud InfrastructureNetworkingbasic38 EndpointsREST

For Agents

Manage Alwaysdata hosting: accounts, domains, DNS records, websites, mailboxes, databases, and SSL certificates through 38 HTTP Basic-authenticated endpoints. Useful for agents automating provisioning and DNS changes.

Use for: Add a new domain to our Alwaysdata account, Create an A record pointing example.com to a server IP, Update an MX record to switch our email provider, List all DNS records on a managed domain

Not supported: Does not provision cloud VMs, run container orchestration, or manage CDN edge configuration — use only for managing Alwaysdata hosting accounts, domains, DNS, websites, mailboxes, databases, and certificates.

Jentic publishes the only available OpenAPI specification for Alwaysdata API, keeping it validated and agent-ready. Alwaysdata is a French web-hosting provider, and this REST API exposes 38 HTTP Basic-authenticated endpoints for managing hosting accounts, domains, DNS records, websites, mailboxes, databases, and SSL certificates. Teams use it to automate provisioning, register and update domains, manage DNS at the record level, and orchestrate site and database lifecycle without logging into the control panel.

Jentic One on GithubView OpenAPI Document

Install Jentic One Beta

Connect the Alwaysdata API to your agent

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

1

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
2

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 Alwaysdata API.

List and update hosting accounts via /account/

Register, list, and delete domains through /domain/

Create, update, and delete DNS records on managed domains via /record/

Provision and manage hosted websites and their configuration

Create, list, and delete mailboxes attached to managed domains

Provision and manage databases and database users

Issue and manage SSL certificates tied to a hosted domain

Use Cases

Patterns agents use Alwaysdata API for, with concrete tasks.

★ Automated DNS Record Management

DevOps teams using Alwaysdata for DNS hosting script record changes through /record/ instead of clicking through the control panel. The endpoint exposes full CRUD on A, AAAA, CNAME, MX, and TXT records, which is enough to support deployments that need to flip records as part of cutover or to provision per-environment subdomains automatically.

POST /record/ with type=A, name='app', value='203.0.113.10', and the parent domain id, then GET /record/{id}/ to confirm propagation.

Domain Lifecycle Automation

Agencies and SaaS providers manage many client domains by automating registration, transfer, and deletion through /domain/. Combined with the DNS, mailbox, and SSL endpoints, the API supports a complete add-domain workflow: register, configure DNS, provision mailboxes, and issue an SSL certificate from a single script.

POST /domain/ to register example.com, then POST /record/ to add the A and MX records, then trigger SSL issuance for the new domain.

Hosted Mailbox Provisioning

Teams using Alwaysdata for email automate mailbox creation when new staff arrive instead of sharing the control panel. The API surfaces mailbox CRUD tied to the parent domain, and DNS endpoints sit alongside it so deliverability records (MX, SPF in TXT) can be updated in the same script.

POST a mailbox creation request for the new hire's address against the appropriate domain id, then verify the MX record is in place via GET /record/.

AI Agent Hosting Operator via Jentic

An AI ops agent built on Jentic can take 'point staging.example.com to 203.0.113.10' and resolve it to the right /record/ create call without the agent ever holding the Alwaysdata Basic auth credential. MAXsystem stores the credential and Jentic injects the Authorization header at call time.

Search Jentic for 'create a DNS record', load the POST /record/ schema, and execute it with type=A, name='staging', value=the supplied IP, and the matching domain id.

Key Endpoints

38 endpoints — jentic publishes the only available openapi specification for alwaysdata api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/account/

List hosting accounts

GET

/domain/

List managed domains

POST

/domain/

Register or add a domain

DELETE

/domain/{id}/

Delete a domain

GET

/record/

List DNS records

POST

/record/

Create a DNS record

PUT

/record/{id}/

Update an existing DNS record

DELETE

/record/{id}/

Delete a DNS record

GET

/account/

List hosting accounts

GET

/domain/

List managed domains

POST

/domain/

Register or add a domain

DELETE

/domain/{id}/

Delete a domain

GET

/record/

List DNS records

POST

/record/

Create a DNS record

PUT

/record/{id}/

Update an existing DNS record

DELETE

/record/{id}/

Delete a DNS record

Why Jentic?

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

Credential management

Credential isolation

Alwaysdata HTTP Basic credentials (the account API key) are stored encrypted in the Jentic vault (MAXsystem). Agents never see the raw credential; the Authorization header is injected at call time.

Intent-based discovery

Intent-based discovery

Agents search Jentic by intent (e.g., 'create a DNS record', 'register a domain') and Jentic returns the matching Alwaysdata operation with its schema, so the agent can fill in record type, name, value, and domain id without reading the spec.

Time to first call

Time to first call

Direct Alwaysdata integration: half a day to a day for auth, resource id juggling between domains and records, and pagination. Through Jentic: under an hour to search, load, and execute the first DNS or domain operation.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Cloudflare API

→

Global DNS, CDN, and edge security platform with extensive automation

Choose Cloudflare when the workflow needs anycast DNS, edge caching, and a deeper security/CDN feature set than Alwaysdata's hosting API.

Alternative

DigitalOcean API

→

Cloud infrastructure provider with Droplets, managed databases, and DNS

Choose DigitalOcean when the team needs cloud VMs and managed databases at scale rather than shared hosting plus DNS.

Alternative

Linode API

→

Cloud compute, networking, and DNS from Akamai-owned Linode

Choose Linode when the workflow centres on programmable Linux VMs and the team wants stronger compute primitives than Alwaysdata's hosting model.

Complementary

OpenAI API

→

Use a language model alongside Alwaysdata to plan or summarise infrastructure changes

Use OpenAI alongside Alwaysdata when an agent needs to reason about a change request before executing the corresponding /record/ or /domain/ call.

FAQs

Specific to using Alwaysdata API through Jentic.

Why is there no official OpenAPI spec for Alwaysdata API?

Alwaysdata does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Alwaysdata API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the Alwaysdata API use?

Alwaysdata uses HTTP Basic authentication with an account-issued API key as the username. Through Jentic, the credential is stored encrypted in the MAXsystem vault and the Authorization header is injected at call time.

Can I create DNS records with the Alwaysdata API?

Yes. POST to /record/ with the record type, name, value, and parent domain id to create A, AAAA, CNAME, MX, or TXT records. PUT /record/{id}/ updates an existing record and DELETE /record/{id}/ removes one.

What are the rate limits for the Alwaysdata API?

Specific limits are not in the spec. Treat the API as account-throttled and add retry-with-backoff for 429 responses. Batch DNS changes to limit bursts during deploy windows.

How do I add a domain through Jentic?

Run pip install jentic and search with 'register a domain in Alwaysdata'. Load the POST /domain/ schema and execute it with the domain name. Follow up with POST /record/ to configure DNS for the new domain.

Does the Alwaysdata API let me issue SSL certificates?

Yes. The SSL certificate endpoints expose listing, issuing, and deletion tied to a hosted domain id, so you can request a certificate as part of the same automation that adds the domain and DNS records.

GET STARTED

Start building with Alwaysdata API

Explore with Jentic
View OpenAPI Document