Countries & territories

When to choose it

An operations agent uses the same territory labels across forms, reports, and customer records.

Dataset facts

Source

Unicode CLDR · English labels (unicode-cldr)

Identifier

CLDR territory code

Coverage

English territory labels; no geocoding or boundary geometry.

Freshness

Pinned CLDR 48.0.0 edition; no live release freshness is claimed.

Limitations

Not a source of geopolitical adjudication. No geocoding, boundary geometry, or live political-status adjudication.

Access

Paid data operation after live availability and price checks. Discovery is free.

Usage terms

Unicode-3.0 permits redistribution with attribution. Preserve the complete Unicode License V3 notice published at the API attribution endpoint.

Reference domain

cldr-territories-en

Approved source fields

• Territory code
• English display name

Source fields describe the collection; use the API schema for response structure. No record counts or ingestion timestamps are asserted here.

Query capabilities

• Exact territory codes
• Case-insensitive substring query against code or English label
• Validity selection
• Cursor pagination, 1–500 values per page

Reference request shape

Illustrative arguments for get_reference_data, not an executed request or a sample result. Check live availability and authorize the quoted spend before calling.

{
  "domain": "cldr-territories-en",
  "codes": [
    "US"
  ],
  "include_inactive": true,
  "limit": 1
}

include_inactive: true intentionally includes values whose validity is unknown. Preserve active: null and reference_value_validity_unknown; do not relabel them as known active. Use include_inactive: false if your task accepts only known-active values.

Exact input schema · Result envelope

Before accepting a result

Inspect the response’s source licenses, public-use terms, version, warnings and available source timestamps. An absent retrieval timestamp is unknown freshness, not today’s data.

Read the agent guide