Build with Register.gy

Overview

Register.gy is an accredited .gy domain registrar. The developer platform exposes the same tools customers use in the Client Area, so an assistant or an app can:

• Check availability of .gy, .com.gy, .co.gy, .net.gy and .org.gy names, with price and a registration link. No sign-in needed.
• List a customer's domains and read their DNS records.
• Connect a website: send the records a website builder shows (Lovable, Bolt, Replit, v0, Netlify, Shopify…), get a preview, then apply. Every change can be undone for 7 days.
• Check that a site is live: DNS visibility and https.

By design the platform never changes email (MX) records or nameservers, transfers domains or touches payments. Registry-level changes are applied by the Register.gy team.

Quickstart

1. Check a name (no key)

Copycurl "https://register.gy/wp-json/rgy/v1/availability?domain=mybakery.gy"

2. Create an API key

Log in to the Client Area, open API & AI assistants and click Create API key. It is shown once.

3. List your domains

Copycurl -H "Authorization: Bearer rgy_live_YOUR_KEY" https://register.gy/wp-json/rgy/v1/domains

4. Preview, then connect a website

Copycurl -X POST https://register.gy/wp-json/rgy/v1/domains/mybakery.gy/connect/preview \
  -H "Authorization: Bearer rgy_live_YOUR_KEY" -H "Content-Type: application/json" \
  -d '{"records":[{"type":"A","name":"@","value":"185.158.133.1"},{"type":"TXT","name":"_lovable","value":"lovable_verify=…"}]}'

If the preview looks right, send the same body to /connect/apply. Undo with /connect/undo within 7 days.

Connect an AI assistant

Register.gy runs a remote MCP server (the standard way assistants use outside tools). Assistants that support sign-in will open a Register.gy window: the customer enters their email, types the 6-digit code we send, and approves what the assistant may do.

Copyhttps://register.gy/wp-json/rgy/v1/mcp

Copyhttps://register.gy/wp-json/rgy/v1/mcp

Copyclaude mcp add --transport http register-gy https://register.gy/wp-json/rgy/v1/mcp

Copy{
  "mcpServers": {
    "register-gy": {
      "url": "https://register.gy/wp-json/rgy/v1/mcp",
      "headers": { "Authorization": "Bearer rgy_live_YOUR_KEY" }
    }
  }
}

Then ask, for example: "Is mybakery.gy available?" or "Connect my Lovable site to mybakery.gy." The assistant shows the planned changes and asks before applying them.

Public, search-only endpoint (no sign-in): https://register.gy/wp-json/rgy/v1/mcp/public

Authentication

OAuth 2.1 (recommended for assistants and apps used by other people)

• Authorization code flow with PKCE (S256 only). Public and confidential clients.
• Dynamic client registration (RFC 7591) at https://register.gy/oauth/register. Redirect URIs must be https, or http on localhost.
• Discovery: /.well-known/oauth-authorization-server (RFC 8414) and /.well-known/oauth-protected-resource (RFC 9728). The MCP endpoint answers unauthenticated requests with 401 and a WWW-Authenticate header pointing to the resource metadata.
• Access tokens last 1 hour; refresh tokens 30 days and rotate on every use. Reusing an old refresh token ends the whole connection.
• Revocation: https://register.gy/oauth/revoke (RFC 7009). Customers can also disconnect apps in the Client Area.

API keys (your own scripts and tools)

Create up to 5 keys in the Client Area. Send them as Authorization: Bearer rgy_live_… or X-API-Key: rgy_live_…. Keys have both scopes. They are stored hashed, and the owner is emailed when one is created.

MCP server

Streamable HTTP transport, JSON responses (no event stream), protocol versions 2025-06-18, 2025-03-26, 2024-11-05.

REST API

Base URL https://register.gy/wp-json/rgy/v1. JSON in, JSON out. Errors look like {"error":{"code":"not_found","message":"…"}}.

Connect request body

Either a list of records, or the raw text your builder shows (a table or list). Only A, AAAA, CNAME (ALIAS) and TXT are set; anything else is listed under skipped with the reason.

Copy{
  "records": [
    { "type": "A", "name": "@", "value": "185.158.133.1" },
    { "type": "CNAME", "name": "www", "value": "mysite.netlify.app" }
  ]
}

Limits and errors

Security

• Keys and tokens are stored only as SHA-256 hashes. Sign-in codes are single-use, expire in 10 minutes and are rate limited.
• Each key or connection only sees the domains of the customer who created it.
• Every change through the API is logged and can be undone for 7 days. Website records are set DNS-only so builders can issue their https certificates.
• Found a security problem? Email contact@iis.gy with "Security" in the subject. Please give us a chance to fix it before telling others.

Changelog

• 8 Oct 2026 OAuth 2.1 sign-in (PKCE, dynamic client registration, refresh rotation), connected apps in the Client Area, public search-only MCP endpoint.
• 8 Oct 2026 REST API and MCP server launched: availability, domains, records, connect preview/apply/undo, live check. API keys in the Client Area.

Support and terms

Questions, ideas or partnership requests: contact@iis.gy or +592-623-1721.

Use of the API is covered by our privacy policy. Dedicated API terms are being finalised.