Company assets and geography
Company/assets and /fleet, plus /geo/layers and /geo/features, expose
the held physical-asset registry. An asset has a source, a lifecycle status, an
ownership/operating role and an explicitly declared location precision. Respect
license attribution and any withheld geometry. Empty reviewed coverage does not
mean a company owns no assets.
For bounded research without geometry, use view=attributes and the supported
kind/status/country/search filters. /geo/features/{key}/data retrieves the data
attached to a selected feature. MCP get_company_assets, search_assets and
other asset tools expose the licensed attributes their schemas allow; consult
the generated reference for exact names and paths.
FX
GET /api/v1/fx serves reference rates; base, region and codes select a
rebased board. /api/v1/fx/pairs/{pair}/prices serves a pair’s history. These
are official/reference-rate observations, not executable dealer quotes.
Countries and institutions
Country profiles can be requested withview=profile; series catalogs with
view=catalog, query/category filters and limit/offset. Regional and government
entity catalogs are also available. Read histories from the returned series
identifiers and keep their units, geography and publisher.
/military/conflicts and /foreign-relations/organisations expose published
registry rows. The organisation-country relationship has its own route.
Draft rows stay out of production; a local development response can include
different coverage. The unreleased bilateral and country-military MCP tools
are not part of the public tool set.
Tracking endpoints are documented in the API Reference and callable through
the CLI’s operation interface. They do not imply that every tracking, imagery
or price dataset is redistributable through MCP. Each interface preserves its
own license filters and release gates.