Jentic OSThe workplace. An in-house AI platform for every employeeJentic OneSafe access. Agents reach your systems without holding keysJentic AIRThe foundation. Gets your existing platforms ready for AI
Pricing

GET STARTED

API DirectoryBrowse 10,000+ APIs ready for AI agent integrationDocumentationGuides and API reference

TOOLS

API ScoringCheck your AI readiness using our scorecardArazzo UIVisualize Arazzo workflows as interactive documentationArazzo EditorBuild and edit multi-step API workflows visually

COMMUNITY

GitHubOpen source projects and examplesOpen StandardsBuilt on open specs. Never locked in.
All ResourcesEverything in one placeBlogLatest articles and insightsTech Talk NewsletterAPIs, AI agents, architecture and strategyWebinarsLive sessions and on-demand recordingsReports & WhitepapersOriginal research on enterprise AI
About UsOur mission and teamCareersJoin our teamContactGet in touch
Try it now
Jentic OSJentic OneJentic AIR
Pricing
API DirectoryDocumentationAPI ScoringArazzo UIArazzo EditorGitHubOpen Standards
All ResourcesBlogTech Talk NewsletterWebinarsReports & Whitepapers
About UsCareersContact
Try it now
JenticJentic
Products
  • Jentic OS
  • Jentic One
  • Jentic AIR
For Developers
  • API Directory
  • Documentation
  • GitHub
Company
  • About Jentic
  • Careers
  • Contact Us
  • Trust Centre
ISO/IEC 27001:2022 certification badge issued by Prescient SecurityISO/IEC 27001:2022 certification badge issued by Prescient Security

Information Security Management System

Certified to ISO/IEC 27001:2022 by Prescient Security

AICPA SOC for Service Organizations logoAICPA SOC for Service Organizations logo

SOC 2® Type 1 report

Audited by Prescient Assurance

Terms & Conditions•Privacy Policy•
© 2026 Jentic Technology Ltd. All rights reserved.
2 Grattan Court East, Dublin, D02 VX86, Ireland
Switch to light modeSwitch to dark mode
APIs / Data Enrichment / REST Countries API
REST Countries API logo

REST Countries API

66
AI ReadinessAI-Aware (B)66/100
See full scorecard
Agent-ready OpenAPI document · curated by JenticData EnrichmentData Transformationbearer5 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Look up country reference data such as capitals, currencies, languages, timezones, calling codes, and borders by ISO code, fuzzy name search, currency, or region.

Use for: Get the capital and currency of Japan, Find all countries that use the euro, List all countries in Oceania with their populations, Retrieve the calling code for a country by its ISO code

Not supported: Does not handle geocoding, address validation, states or cities, or exchange rates. Use for country-level reference data lookups only.

The REST Countries API returns reference data for more than 250 countries, including names, ISO codes, capitals, flag, region and subregion, population, area, borders, calling codes, currencies, languages, timezones, top-level domains, and memberships. A country can be fetched by its ISO 3166-1 alpha-2 or alpha-3 code, found with fuzzy search across names, capitals, and codes, or listed by the currency it uses or the region it sits in. Responses can be trimmed with response_fields or omit_fields, and the spec states the data is synced every 4 hours from more than 35 sources.

Jentic One on GithubView OpenAPI Document

Install Jentic One Beta

Connect the REST Countries API to your agent

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

1

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%2Frestcountries.com%2Frestcountries" | sh
2

Step 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%2Frestcountries.com%2Frestcountries" | 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 REST Countries API.

Fetch a country's full record by ISO 3166-1 alpha-2 code such as FR or alpha-3 code such as JPN

Fuzzy-search countries by name, capital, or code with limit and offset pagination

List every country that uses a given currency code such as EUR

List countries in a region such as Europe, Americas, Asia, Africa, or Oceania

Trim responses to the fields you need with response_fields or exclude fields with omit_fields

Use Cases

Patterns agents use REST Countries API for, with concrete tasks.

★ AI agent answering country questions

An assistant agent asked about a country's capital, currency, or timezones should answer from data rather than memory. Through Jentic the agent searches for 'look up country details', loads the getCountryByAlpha2 or searchCountries operation, and requests only the fields it needs with response_fields. The bearer key is injected by Jentic at call time.

Call GET /countries/v5 with q 'nether' and response_fields 'names,capitals,currencies,timezones', then answer the user's question about the Netherlands

Normalising country fields in user data

Signup forms and CRM exports collect countries as free text, two-letter codes, or three-letter codes. Fuzzy search on GET /countries/v5 maps messy input to a country record, and the alpha-2 and alpha-3 lookups confirm a code and return its canonical names and codes, so a pipeline can store one consistent format.

For each country string in a CSV, call GET /countries/v5 with q set to the string and limit 1, and write the returned alpha-2 code from codes into a new column

Building country pickers and regional views

Checkout and settings screens need country lists with flags and calling codes, often grouped by region or filtered by currency. GET /countries/v5/region/{region} lists countries in a region and GET /countries/v5/currencies/{currency_code} lists the countries for a currency, each trimmed with response_fields to keep payloads small.

Call GET /countries/v5/region/Europe with response_fields 'names,flag,calling_codes' and build a sorted country picker list

Key Endpoints

5 endpoints — the rest countries api returns reference data for more than 250 countries, including names, iso codes, capitals, flag, region and subregion, population, area, borders, calling codes, currencies, languages, timezones, top-level domains, and memberships.

METHOD

PATH

DESCRIPTION

GET

/countries/v5/codes.alpha_2/{code}

Get country by ISO alpha-2 code

GET

/countries/v5/codes.alpha_3/{code}

Get country by ISO alpha-3 code

GET

/countries/v5

Search countries

GET

/countries/v5/currencies/{currency_code}

Get countries by currency

GET

/countries/v5/region/{region}

Get countries by region

GET

/countries/v5/codes.alpha_2/{code}

Get country by ISO alpha-2 code

GET

/countries/v5/codes.alpha_3/{code}

Get country by ISO alpha-3 code

GET

/countries/v5

Search countries

GET

/countries/v5/currencies/{currency_code}

Get countries by currency

GET

/countries/v5/region/{region}

Get countries by region

Jentic AI Readiness Score

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

R

REST Countries API

- AI-Aware (B)
66/100
100
Foundational Compliance
59
Developer Experience & Jentic Compatibility
45
AI-Readiness & Agent Experience
94
Agent Usability
60
Security
95
AI Discoverability
Powered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.2
Show dimension breakdown
100

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A+Signals: 4
99%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

100%

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

100%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

59

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: C+Signals: 4
0%

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

35%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

45

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: DSignals: 4
28%

Description Coverage

Coverage of descriptions across API elements.

0%

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

100%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

50%

Summary Coverage

Coverage of summaries across operations/tags/info.

94

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1
94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

60

Security

Trust, risk posture, and security compliance.

Grade: B-Signals: 1
60%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

95

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: A+Signals: 1
95%

Descriptive Richness

Clarity and depth of descriptions across API elements.

View full reportHow the score is calculatedMore about the dimensions

Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

Score your own APIScoring CLI agent skill
npx @jentic/api-scorecard-cli score <openapi-url>

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring REST Countries by hand means attaching the bearer key to each call and knowing which lookup path fits the input you have: alpha-2, alpha-3, currency, region, or fuzzy search. Through Jentic you install once, import REST Countries from the API Directory, store the key once, and your agent calls it.

Permission scoping

REST Countries puts the country code, currency code, and region in the URL path (/countries/v5/region/{region}, /countries/v5/currencies/{currency_code}), so a rule can pin your agent to one region or one currency. Every operation is a read, so scoping here limits which data the agent pulls rather than guarding writes.

Credential isolation

Your REST Countries key 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 'find countries that use the euro' or 'look up country details', and Jentic returns the matching REST Countries operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Countrylayer API

→

Country reference data by name, code, capital, currency, and region.

Choose Countrylayer if the project already uses an apilayer key; choose REST Countries for fuzzy search and field trimming.

Alternative

Country State City API

→

Countries with their states and cities.

Choose Country State City when the agent needs subdivisions and cities; choose REST Countries for country-level currencies, languages, timezones, and memberships.

Complementary

ExchangeRate-API

→

Currency exchange rates.

Use REST Countries to find a country's currency code, then ExchangeRate-API to convert prices into it.

FAQs

Specific to using REST Countries API through Jentic.

What authentication does the REST Countries API use?

The OpenAPI spec declares bearerAuth as the global security scheme: an API key sent as a Bearer token in the Authorization header on each of its operations. Through Jentic the key is held by your own instance and attached at call time, so the agent never handles it.

Can I get only some fields for a country?

Yes. Every operation accepts response_fields, a comma-separated list of fields to include, and the code and search lookups also accept omit_fields to exclude fields. The Country schema includes names, codes, capitals, flag, region, subregion, population, area, borders, calling_codes, currencies, languages, timezones, tlds, and memberships.

What are the rate limits for the REST Countries API?

The OpenAPI spec does not specify rate limits. Check https://restcountries.com for current usage terms.

Is there a REST Countries MCP server?

You don't need an MCP server to give your agent REST Countries. Jentic connects it directly from the API Directory: import it, store your key once, and your agent calls the lookup and search operations it needs on demand, without extra tool definitions sitting in its context.

Can I limit what my agent is allowed to do with the REST Countries API?

Yes. For example, write a rule that allows only GET /countries/v5/region/Europe and GET /countries/v5/codes.alpha_2/{code}, so the agent can read European country lists and single-country records but not run open-ended searches. Every call it makes is logged.

How do I look up a country through Jentic?

Add the REST Countries API to your Jentic One instance from the directory and store your key. Your agent searches for 'look up country details', loads the getCountryByAlpha3 operation, and calls GET /countries/v5/codes.alpha_3/{code} with a code such as FRA. To run it on your own infrastructure, install Jentic One from its GitHub repo.

GET STARTED

Start building with REST Countries API

Explore with Jentic One
View OpenAPI Document