rentadomain.sh API Before you start A person rents the name first: they sign in, verify their legal name with a government ID, sign the lease and pay. That person then creates your token from the dashboard at /app/:lease. A token cannot rent, sign or pay. Who can rent: You rent for your business or another commercial purpose. The lease is not for personal, family or household use. If you sign for a company, you confirm you can bind it. Bearer token auth. Tokens look like rd_ followed by 40 letters and digits and are shown once, when they are created. One token works on one lease. Scopes: dns:read, dns:write GET /api/v1/names GET /api/v1/names/:host No token. Every listed name, or one name: status, the rent, total, floor and ceiling for each term, and the URL where a person rents it. curl https://rentadomain.sh/api/v1/names GET /api/v1/leases List the leases the token can see. curl https://rentadomain.sh/api/v1/leases \ -H "authorization: Bearer rd_1a2b3c4d5e6f7g8h9i0jklmnopqrstuvwxyzABCD" GET /api/v1/leases/:id/records List the DNS records on one lease. curl https://rentadomain.sh/api/v1/leases/l_abc123/records \ -H "authorization: Bearer rd_1a2b3c4d5e6f7g8h9i0jklmnopqrstuvwxyzABCD" POST /api/v1/leases/:id/records/plan Propose a change. Returns a plan id and a verdict. Nothing is written yet. curl https://rentadomain.sh/api/v1/leases/l_abc123/records/plan \ -H "authorization: Bearer rd_1a2b3c4d5e6f7g8h9i0jklmnopqrstuvwxyzABCD" \ -H "content-type: application/json" \ -d '{"ops":[{"op":"create","record":{"type":"CNAME","name":"www","content":"example.com"}}]}' POST /api/v1/leases/:id/records/apply Apply a proposed plan by id. curl https://rentadomain.sh/api/v1/leases/l_abc123/records/apply \ -H "authorization: Bearer rd_1a2b3c4d5e6f7g8h9i0jklmnopqrstuvwxyzABCD" \ -H "content-type: application/json" \ -d '{"planId":"p_xyz789"}' GET /api/v1/leases/:id/plans/:planId Where a plan stands: proposed, pending_review, applied, expired, rejected or failed, with the reason. What a token cannot apply CAA, SPF, DKIM and DMARC records, any wildcard record, any TXT at the apex, and any plan with more than 10 changes. The verdict on such a plan says protected: true, and apply answers 403 protected. A person applies it in the dashboard with a passkey or an authenticator code. Limits - 60 record changes per hour on a lease. - A plan lives 15 minutes. Apply it before then, or plan again. - The first plan applied on a new lease is held for a person on our side to review. Apply answers 202 with pending_review: true and a status_url. Poll that URL. Do not apply the plan again. Errors Every error is JSON: {"error":{"code":"...","message":"..."}} - 400 bad_ops, bad_plan: the body is not what the route takes. - 401 unauthorized: no token, or a token that is revoked or unknown. - 403 forbidden: the token lacks the scope. - 403 protected: the plan needs a person. See above. The error also carries plan_id, dashboard_url and protected_reasons. - 403 identity_required: the renter has not finished the identity check. - 403 https_required: a token route was asked over plain HTTP. The API answers over HTTPS only. - 404 not_found: no such lease, plan, name or route for this token. - 409 expired, not_proposed, lease_inactive, policy, failed, not_yours, apply_failed: the plan was not applied. The message says why. - 500 internal: our side failed. It is logged. - 503 records_paused: DNS for the name is paused on our side. Nothing you set is lost. OpenAPI 3.1: https://rentadomain.sh/openapi.json API catalog (RFC 9727): https://rentadomain.sh/.well-known/api-catalog MCP server (no token to search, price or read terms): https://rentadomain.sh/mcp Full docs, and how to connect any client: https://rentadomain.sh/for-agents