API and MCP
API keys — which key for which task
Ready sets of rights for typical tasks — reports, certificates, DNS, an AI agent, purchases — and the rules people and AI assistants use to pick a key.
This page is for you and for an AI assistant that helps you set up a key. Find your task in the table, pick the listed template in the “New key” form and fill in “Where it works” and “Conditions” as written. How the form itself works is in API keys.
Task → key
| Task | Template in the form | Rights | Where it works | Conditions |
|---|---|---|---|---|
| A script or dashboard reads domains and terms | “Read only” | domain.read, monitor.read | all domains | IPs optional, term up to 365 days |
| Accounting or a report sees the balance | “Balance and domains” | domain.read, billing.read | all domains | IPs optional, term up to 365 days |
| A program puts domains under monitoring | “Monitoring” | monitor.read, monitor.edit | all or selected domains | server IP, 90 days |
| A server updates its certificate files itself | “SSL certificates” | ssl.read, ssl.reissue | only that server's domains | server IP, 90 days |
| A program orders certificates | “SSL — ordering” | ssl.read, ssl.reissue, ssl.order, billing.read | selected or all domains | IPs required, daily limit (required for all domains), 30 days |
| A manager or contractor edits records of several sites | “DNS zones — for a manager” | dns.read, dns.edit | selected domains only | personal key, 90 days |
| An AI agent or automation runs all zones | “DNS zones — full access” | dns.read, dns.edit, dns.zone_create, keys.zones_grant | all domains | organization key, server IP, 90 days |
| Scheduled renewal | “Domain renewal” | domain.read, domain.renew, billing.read | all or selected domains | IPs required, daily limit, 30 days |
| Registering new domains | “Domain registration” | domain.read, domain.register, billing.read | all domains | IPs required, daily limit, 30 days |
| An agent takes a domain from purchase to DNS records | “Domains and DNS — for AI” | registration, renewal, all DNS rights except granting zones, and the balance | all domains | IPs required, daily limit, 30 days |
A template only fills in the rights. You can remove them or add a row under “What the key may do”.
“DNS zones — full access” does not allow registering domains. This key creates a new zone for a domain already in the organization, or for a name registered elsewhere that you point to our name servers. A domain that does not exist yet has to be registered first.
One key or two
An agent that both buys domains and runs DNS is better off with two keys:
- DNS key — “DNS zones — full access”, term 90 days or more.
- Purchase key — “Domain registration” or “Domain renewal”, term 30 days, a daily limit for 1–2 domains.
If the purchase key leaks, the loss is capped by the daily limit and the short key soon switches off by itself. The DNS key never touches the balance. The “Domains and DNS — for AI” template is simpler, but lives no longer than 90 days, and a leak puts both the records and the money at risk.
How to pick a key — rules for a person and an AI assistant
Task first, then rights. What the program will do, with which domains, from which server. Give the fewest rights that cover the task: the “Read” level if no changes are needed.
Money goes in a separate key. The
ssl.order,domain.renewanddomain.registerrights require allowed IPs, and such a key lives no longer than 90 days. A daily limit is required for renewal and registration and for any money key on all domains; always set one. A registration key takes as owner only a "Contacts" record with a full address and the authority box ticked: create it before issuing the key — the key form warns you if there is none yet.Whose key. For a server, CI or an integration — “Organization”: it outlives changes of people. For yourself or your assistant on your own computer — “Personal”.
Allowed IPs are where the calls come from. For a server — the server's address. For an assistant on your computer — the computer's address: the form shows it under the field and adds it with the “Add” button. A home address may change; then the key stops working and the address needs updating.
Selected domains when possible. A manager and a certificate server need only their own domains. Only new zones, granting zones to other keys and registering new names work on all domains.
Several organizations. A personal key — “This one and selected”; “All my organizations” takes reading rights only. A key that spends money and an organization key work in one organization.
A short term. A key nobody called for 90 days switches off by itself. When the task is done, revoke the key.
The key goes into secrets only. Not into a chat, page code or a repository. Give it to an AI assistant through an environment variable or a secrets file, not as message text.
Check. After issuing:
curl -H "Authorization: Bearer zr_live_..." https://api.zrazu.com/v1/api-keys/currentThe answer shows the rights, domains, IPs and term. If something is missing, issue a new key with the right set; the rights of an existing key cannot be changed.
What no key will give
Changing contacts and locks, getting the transfer code, revoking certificates, managing people, keys and payments. These actions exist only in the cabinet. An assistant should not advise looking for rights for them — there are none.