Department of Interior
The U.S. Department of the Interior (DOI) manages and conserves federal lands and natural resources across America. DOI's bureaus and offices provide REST APIs and data services covering national park information, water resources, earthquake data, mineral resources, geospatial federal land boundaries, and wildlife data. Key API providers include the National Park Service (NPS), the U.S. Geological Survey (USGS), and the Bureau of Land Management (BLM).
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles Department of Interior the way a machine reads it — 57 machine-readable artifacts across 41 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 Interior scores 48.6/100 (developing), with a separate agent-readiness read of 48/100 (agent ready). 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.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Department of Interior
Each block below is one kind of artifact we hold for Department of Interior. 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 41
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.
NPS Data API
The National Park Service Data API provides authoritative data about NPS sites including parks, alerts, campgrounds, events, visitor centers, news releases, articles, and educat...
USGS Earthquake Hazards Web Services
Real-time earthquake data feeds, notifications, and web services providing access to seismic event data including location, magnitude, depth, and related hazard information. Sup...
USGS Mineral Resources Data API
API access to the USGS Mineral Resources Data System (MRDS) and related mineral deposit databases. Supports geographic queries, bounding box searches, point queries, and access ...
BLM GIS REST Services
Bureau of Land Management geospatial REST services providing access to federal land status, cadastral data (Public Land Survey System), mineral rights boundaries, and other BLM-...
USGS ScienceBase API
ScienceBase provides collaborative scientific data management infrastructure enabling upload, documentation, sharing, and discovery of USGS scientific data using standards-compl...
Department of Interior agency-codes API
Code identifying the agency or organization used for site information, data sources, and permitting agencies. Agency codes are fixed values assigned by the National Water Inform...
Department of Interior altitude-datums API
The recommended vertical datum is NAVD88 (North American Vertical Datum of 1988) where applicable as stated in Office of Information Technical Memo 2002.01. NGVD29 (National Geo...
Department of Interior aquifer-codes API
Local aquifers in USGS data are identified by an aquifer name and geohydrologic unit code (a three-digit number related to the age of the formation, followed by a 4 or 5 charact...
Department of Interior aquifer-types API
Groundwater occurs in aquifers under two different conditions. Where water only partly fills an aquifer, the upper surface is free to rise and decline. These aquifers are referr...
Department of Interior channel-measurements API
Channel measurements taken as part of streamflow field measurements.
Department of Interior citations API
Citations associated with water measurement methods.
Department of Interior combined-metadata API
This endpoint combines metadata from timeseries and field measurements collections by site.
Department of Interior continuous API
Continuous data are collected via automated sensors installed at a monitoring location. They are collected at a high frequency and often at a fixed 15-minute interval. Depending...
Department of Interior coordinate-accuracy-codes API
Appropriate code on the schedule to indicate the accuracy of the latitude-longitude values.
Department of Interior coordinate-datum-codes API
Horizontal datum code for the latitude/longitude coordinates. There are currently more than 300 horizontal datums available for entry.
Department of Interior coordinate-method-codes API
Methods used to determine latitude-longitude values.
Department of Interior counties API
The name of the county or county equivalent (parish, borough, planning reagion, etc.) in which the site is located. List includes Census Bureau FIPS county codes, names and asso...
Department of Interior countries API
FIPS country codes and names.
Department of Interior daily API
Daily data provide one data value to represent water conditions for the day. Throughout much of the history of the USGS, the primary water data available was daily data collecte...
Department of Interior field-measurements API
Field measurements are physically measured values collected during a visit to the monitoring location. Field measurements consist of measurements of gage height and discharge, a...
Department of Interior field-measurements-metadata API
This endpoint provides metadata about field measurement collections, including when the earliest and most recent observations for a parameter occurred at a monitoring location a...
Department of Interior hydrologic-unit-codes API
Hydrologic units are geographic areas representing part or all of a surface drainage basin or distinct hydrologic feature identified by a unique number (HUC), and a name. The Un...
Department of Interior latest-continuous API
This endpoint provides the most recent observation for each time series of continuous data. Continuous data are collected via automated sensors installed at a monitoring locatio...
Department of Interior latest-daily API
Daily data provide one data value to represent water conditions for the day. Throughout much of the history of the USGS, the primary water data available was daily data collecte...
Department of Interior latest-field-measurements API
Field measurements are physically measured values collected during a visit to the monitoring location. Field measurements consist of measurements of gage height and discharge, a...
Department of Interior medium-codes API
Medium refers to the specific environmental medium from which the sample was collected. Medium type differs from site type because one site type, such as surface water, could ha...
Department of Interior method-categories API
Categorical standards for methods describing the associated data's appropriateness for an intended use.
Department of Interior method-citations API
Citation identifiers for water measurement methods.
Department of Interior methods API
Water measurement or water-quality analytical methods. Codes and descriptions defining a method for calculating or measuring the value of a water quality or quantity parameter. ...
Department of Interior monitoring-locations API
Location information is basic information about the monitoring location including the name, identifier, agency responsible for data collection, and the date the location was est...
Department of Interior national-aquifer-codes API
National aquifers are the principal aquifers or aquifer systems in the United States, defined as regionally extensive aquifers or aquifer systems that have the potential to be u...
Department of Interior parameter-codes API
Parameter codes are 5-digit codes and associated descriptions used to identify the constituent measured and the units of measure. Some parameter code definitions include informa...
Department of Interior peaks API
Annual peak flow values are the maximum instantaneous streamflow values recorded at a particular site for the entire water year from October 1 to September 30. Note that the ann...
Department of Interior reliability-codes API
Code indicating the reliability of the data available for the site.
Department of Interior server API
These APIs provide OGC-compliant interfaces to USGS water data, letting you download continuous sensor measurements, discrete field measurements, metadata about monitoring locat...
Department of Interior site-types API
The hydrologic cycle setting or a man-made feature thought to affect the hydrologic conditions measured at a site. Primary and secondary site types associated with data collecti...
Department of Interior states API
State name or territory. Includes U.S. states and foreign entities classified under FIPS as 'Principal Administrative Divisions'.
Department of Interior statistic-codes API
Statistic codes.
Department of Interior time-series-metadata API
Daily data and continuous measurements are grouped into time series, which represent a collection of observations of a single parameter, potentially aggregated using a standard ...
Department of Interior time-zone-codes API
The ISO 8601 standard defines time zone offsets as a numerical value added to a local time to convert it to Coordinated Universal Time (UTC), either as +hh:mm or -hh:mm, or repr...
Department of Interior topographic-codes API
The code that best describes the topographic setting in which the site is located. Topographic setting refers to the geomorphic features in the vicinity of the site.
Scroll within the panel for all 41 ·
Pricing 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 six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Doi Plans Pricing
PLANSRate 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.
Doi 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.
Doi Finops
FINOPSSemantic 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.
Doi 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 Interior API Rules
SPECTRALJSON Schema 5
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.
Error
JSON SCHEMAQueryable
JSON SCHEMAQueryables
JSON SCHEMATilematrixsetlink
JSON SCHEMATiles
JSON SCHEMAExamples 3
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
Usgs Water Error Example
EXAMPLESecurity Posture 2
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 Interior — 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.
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Operate 1
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/doi · machine-readable index on apis.io