Department of State
The U.S. Department of State leads U.S. foreign policy, conducts diplomacy with foreign governments, issues U.S. passports and visas, supports U.S. citizens abroad, and publishes country-specific information and travel advisories. It operates no unified developer portal and issues no API keys, but it does serve several real, anonymous, machine-readable surfaces: the state.gov Content API at https://www.state.gov/wp-json, where 473 WordPress REST routes expose press releases, briefings, reports, biographies, bureaus and country and policy content as structured JSON with no credential; the Office of the Historian Ebook Catalog API, an OPDS Catalog 1.1 feed of the Foreign Relations of the United States series and the only surface the Department documents on a developer page of its own; a DCAT-US 3.0 open data catalog of 397 datasets at https://www.state.gov/data.json; and the Travel Advisories RSS feed. Discovery is the weak point rather than supply — none of the nine State hosts probed serves any /.well-known/ document, three of the four State APIs listed in the federal inventory have been retired without notice, and travel.state.gov and the Bureau of Consular Affairs data catalog refuse non-browser clients outright.
Limited machine-readable signal and partial portal coverage — documentation a human can read, but little a machine or agent can consume without scraping.
API Evangelist profiles Department of State the way a machine reads it — 32 machine-readable artifacts across 4 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Department of State scores 38.1/100 (thin), with a separate agent-readiness read of 26/100 (agent aware). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance. Every facet and dimension name is a link: it opens that measurement's page on APIs.io, where the rating runs across the whole catalog — the exact checks that feed it, how every profiled provider distributes on it, and who is at the top of it.
Kin Score
How this is scored →scored 2026-09-08 · rubric v0.20.0
Put this on your own site. The badge is drawn live from Department of State's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/department-of-state/"
title="Department of State on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/department-of-state.svg"
alt="Department of State Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/department-of-state/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/department-of-state/"
title="Department of State on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/department-of-state/card.svg"
alt="Department of State Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>More shapes, themes and sizes → · Score as JSON · How badges work
How we profile Department of State
Each block below is one kind of artifact we hold for Department of State. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 12
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
state.gov Content API
The Department of State runs www.state.gov on WordPress and exposes the WordPress REST API anonymously at https://www.state.gov/wp-json. Alongside the core WordPress resources t...
Office of the Historian Ebook Catalog API
A RESTful, OPDS Catalog 1.1 feed of the Foreign Relations of the United States series — the official documentary record of major U.S. foreign policy decisions — published by the...
Department of State Open Data Catalog
The Department's Project Open Data catalog, served as a single machine-readable DCAT-US 3.0 document at https://www.state.gov/data.json. 397 dataset entries covering Foreign Rel...
State Department Travel Advisories
Country-by-country travel advisories (Levels 1-4) issued by the Bureau of Consular Affairs, with RSS distribution.
Country Information Pages
Per-country pages covering entry/exit requirements, local laws, safety, health, and U.S. embassy contacts.
Smart Traveler Enrollment Program (STEP)
Voluntary enrollment system for U.S. citizens traveling or residing abroad to receive embassy alerts.
U.S. Visa Information
Reference information on nonimmigrant and immigrant visa categories, processing times, and reciprocity schedules.
U.S. Passport Services
Public-facing passport application, renewal, and status-check resources from the Bureau of Consular Affairs.
Foreign Affairs Manual (FAM) and Handbook (FAH)
Department-wide policy and procedural manuals issued by the Office of Directives Management.
ConsularLookout (CLASS)
Government-internal name-check system used during visa and passport adjudication. Referenced here for completeness; no public API.
eCASE Enterprise Case Management
State Department-wide enterprise case-management platform. Internal system; referenced here for organizational completeness.
State Department Open Data on data.gov
Public datasets published by the State Department through the federal open-data catalog.
Scroll within the panel for all 12 ·
MCP Servers 1
Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.
Model Context Protocol servers that expose these APIs to AI agents.
Department of State MCP Server
MCP SERVERPricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the things the Kin Score reads for access clarity — renamed from commercial clarity in rubric 0.12, because a free statutory interface has access terms and no commercial ones.
Published pricing tiers and plan structures.
Rate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Department Of State Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Semantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
State Context
JSON-LDSpectral Rules 1
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
Department of State API Rules
SPECTRALJSON Schema 10
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
state_biography
JSON SCHEMAstate_briefing
JSON SCHEMAstate_bureau
JSON SCHEMAstate_country
JSON SCHEMAstate_ext_content
JSON SCHEMAstate_people
JSON SCHEMAstate_policy_issue
JSON SCHEMAstate_press_release
JSON SCHEMAstate_report
JSON SCHEMAstate_trip_travel
JSON SCHEMAScroll within the panel for all 10 ·
Security Posture 3
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for Department of State — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 3
Portal, sign-up, and the first successful call
Documentation 5
Reference material describing how the API behaves
Agent Surfaces 4
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 5
Pagination, idempotency, versioning, errors, and events
Build 3
SDKs, sample code, and the tooling you integrate with
Access & Security 4
Authentication, authorization, and security posture
Operate 2
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API
Other 3
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/department-of-state · machine-readable index on apis.io
This is an independent, third-party profile of Department of State, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.