Proprietary API overview

How the map consumes the API

The public client requests the map API bootstrap endpoint and receives a JSON document. The request asks for current content and explicitly declares the accepted format.

Before mounting any layer, the application validates the schema version, snapshot version, and vector tile path. An incompatible contract stops loading instead of displaying ambiguous data.

Snapshot contract

The response identifies the version and validity of the published dataset. It also reports operational counts so the interface can verify the delivered volume.

v1

expected schema version

JSON

response format

3

possible states per layer

• schemaVersion: expected format version.
• snapshotVersion: identifier of the loaded publication.
• generatedAt and expiresAt: snapshot generation and validity.
• counts: totals for detailed scientific cells, overview cells, and published features.

Delivered Brasil Terras Raras layers

The snapshot separates vector data, feature collections, and raster overlays. Each layer reports pending, ready, or error, allowing the map to disable only the affected part.

• States and mineral records.
• Brasil Terras Raras resource records.
• Environmental and seismic events.
• Raster overlays with their tile addresses.
• The vector tile path used by opportunity areas.

Dynamic scientific catalog

The panel also requests a versioned, localized manifest containing analysis modes, data domains, rare earths, indicator elements, geochemical profiles, and publishable layers. This catalog is independent from the legacy map and does not turn historical data into an approved scientific result.

Documented scope

This page describes the contract consumed by the public Mineral Map experience. It does not announce a general-purpose open API or grant access to internal operations.