Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the GoDaddy Countries 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://jentic.com/install.sh?src=apis&api=%2Fapis%2Fote-godaddy.com%2Fcountries" | shStep 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fote-godaddy.com%2Fcountries" | sh
jentic register # connects your agent to your Jentic One instanceJentic 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.
What an agent can do with GoDaddy Countries API.
Retrieve summary country lists filtered by market ID with ISO codes and calling codes
Look up detailed country information including all states and provinces
Access localized country names based on market language preferences
Validate ISO country codes against supported country database
Query calling code prefixes for phone number validation
GET STARTED
Patterns agents use GoDaddy Countries API for, with concrete tasks.
★ International Checkout Forms
Build localized checkout and registration forms with country and state dropdowns populated from GoDaddy's validated dataset. The API returns country names in the appropriate language based on market ID, ISO country codes for backend processing, and state/province lists for address validation. Supports BCP-47 market codes for 20+ languages.
Retrieve all countries for market 'en-US' and then fetch detailed state information for country code 'US' to populate a checkout address form
Phone Number Validation
Validate and format international phone numbers by looking up calling code prefixes for each country. The API provides the dialing prefix for every supported country, enabling real-time phone validation in user input forms and normalizing phone numbers to E.164 format before storage.
Look up the calling code for country 'GB' to validate a UK phone number format
Market-Specific Localization Testing
Test application behavior across different market locales by retrieving country data with localized labels. The OTE environment allows developers to verify that country names display correctly in each supported language before deploying to production. Essential for QA workflows on international SaaS platforms.
Compare country name localization by fetching the full country list for market 'fr-FR' and 'en-US' to verify French translations
AI Agent Address Validation
AI agents use this API through Jentic to validate user-provided addresses during automated workflows like order processing or account setup. By searching for country validation operations in Jentic, agents can verify ISO codes, retrieve state lists for data normalization, and localize country names without manual API integration. The no-auth design makes it ideal for agent-driven validation tasks.
Search Jentic for 'validate country and state data' to retrieve the GoDaddy Countries API schema, then call GET /v1/countries/{countryKey} with marketId to validate an address
2 endpoints — retrieve localized country information including iso codes, calling codes, and state/province data.
METHOD
PATH
DESCRIPTION
/v1/countries
List all countries with summary information (ISO code, label, calling code) for a market
/v1/countries/{countryKey}
Retrieve detailed country information including states and provinces for a specific country code
/v1/countries
List all countries with summary information (ISO code, label, calling code) for a market
/v1/countries/{countryKey}
Retrieve detailed country information including states and provinces for a specific country code
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the GoDaddy Countries API by hand means targeting the developer.godaddy.com test host and handling retries yourself for simple metadata reads. Through Jentic you install once, import the GoDaddy Countries API from the API Directory, and your agent calls it.
Permission scoping
The Countries API puts the country key in the URL path (/v1/countries/{countryKey}), so a rule can pin your agent to reading one country or the country list. You choose the operations it may call, and since the surface is read-only country metadata, nothing beyond those lookups is included.
Credential isolation
Any access value this test-environment metadata service requires is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'look up country metadata' or 'get details for one country', and Jentic returns the matching GoDaddy Countries operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Alternatives and complements available in the Jentic catalogue.
Specific to using GoDaddy Countries API through Jentic.
What authentication does the GoDaddy Countries API use?
None. The GoDaddy Countries API does not require authentication. It provides public access to country metadata, ISO codes, calling codes, and state lists. This is an OTE (test environment) endpoint designed for development and testing.
Can I retrieve state lists for specific countries with the GoDaddy Countries API?
Yes. Use GET /v1/countries/{countryKey} with a valid ISO country code and marketId query parameter. The response includes an array of states with their state keys and localized labels. For example, calling /v1/countries/US returns all US states and territories.
What are the rate limits for the GoDaddy Countries API?
Rate limit violations return HTTP 429 with a retryAfterSec field indicating the wait time before retrying. Specific rate limits are not documented in the OpenAPI spec. The OTE environment is designed for testing and may have different limits than production GoDaddy APIs.
How do I get localized country names with the GoDaddy Countries API through Jentic?
Search Jentic for 'retrieve localized country data' to find the GoDaddy Countries API operations. Load the schema for GET /v1/countries, then execute with a BCP-47 marketId parameter like 'fr-FR' or 'es-ES'. The API returns country labels localized to that market's language. Install via pip install jentic and run it through Jentic One, the self-hosted execution layer.
What is the difference between the summary and detailed country endpoints?
GET /v1/countries returns summary data for all countries (countryKey, label, callingCode only). GET /v1/countries/{countryKey} returns detailed information for one country including the full states array with stateKey and label fields. Use the summary endpoint for dropdowns, and the detailed endpoint when you need state/province lists.
Is the GoDaddy OTE Countries API free?
Yes. This is a test environment endpoint (OTE = Operational Test Environment) provided by GoDaddy for developers building applications. It requires no authentication or payment. For production use, verify whether GoDaddy offers a production version of this API and check their pricing.
Can AI agents use the GoDaddy Countries API for address validation?
Yes. AI agents discover this API through Jentic by searching for intents like 'validate country code' or 'get state list'. Jentic returns the operation schemas, and agents call the endpoints directly. The no-auth design makes it particularly simple for agent integration. Common agent tasks include validating ISO codes, populating country dropdowns, and normalizing address data.
Can I limit what my agent is allowed to do with the GoDaddy Countries API?
Yes. Because you run Jentic One yourself, your own rules decide which operations the agent may call, so you can allow just the country lookups it needs. Since this API puts the country key in the URL path (/v1/countries/{countryKey}), a rule can pin the agent to reading a single country or only the summary list from GET /v1/countries. The surface is read-only country metadata, so nothing beyond those lookups is ever exposed.
For Agents
Look up country metadata, calling codes, and state lists filtered by market for localization and international form validation.
Use for: I need to populate a country dropdown for checkout forms, Look up the calling code for a specific country, Get a list of states for a country code, Validate whether a country code is supported
Not supported: Does not handle production GoDaddy domain services, DNS management, or hosting operations-use for country metadata lookup in test environments only.
Retrieve localized country information including ISO codes, calling codes, and state/province data. This test environment (OTE) provides summary and detailed country data filtered by market ID for building and testing international applications. No authentication required for public country metadata access.