Introduction
What the Pulse Intelligence public API is and how to use it
The Pulse Intelligence public API gives your organization programmatic, read-only access to the same mining and commodity intelligence data that powers the Pulse platform — companies, mining assets, publications, and people — plus the filter and lookup endpoints you need to build screens and integrations against that data. It's a thin, purpose-built projection over the same audited service layer that Pulse's own chat and MCP surfaces call, so an endpoint documented here returns the same underlying data you'd see in the product.
Base URL
Every endpoint below is mounted directly under the API root — there's no
/api prefix on the public surface:
https://api.pulseintelligence.com/v1/Endpoints
The trailing slash on each path is required — a request without it doesn't redirect, it 404s.
| Method | Endpoint | Purpose |
|---|---|---|
POST | /v1/companies/search/ | Screen mining companies by commodity, geography, listing, market cap, and more. |
GET | /v1/companies/{id}/dossier/ | Full picture for a single company — overview, financials, recent news, related assets. |
POST | /v1/mining-assets/search/ | Screen mining assets by stage, phase, commodity, geography, and more. |
GET | /v1/mining-assets/{id}/dossier/ | Full picture for a single mining asset. |
POST | /v1/publications/search/ | Search company and asset publications (filings, releases, reports). |
POST | /v1/people/search/ | Search people associated with tracked companies. |
GET | /v1/filters/{resource}/ | List the filterable fields and columns available for a resource. |
GET | /v1/options/{path}/ | Resolve valid option values for a select-type filter field. |
Access
The public API is available to Pulse organization customers. Access is
granted through organization API keys, created by an org admin from the
Pulse product UI — see Authentication for how
to create a key and use it on requests. A key authenticates your
organization as a whole, not an individual user, and only works against the
/v1/ endpoints listed above.
Versioning and stability
This is v1 of the public API. Within v1, request and response contracts
are frozen: endpoints, field names, and shapes documented here won't change
or disappear out from under you. New fields and endpoints may be added over
time, and additions like that are non-breaking — a future v2, if one is
ever needed, would be introduced as a new version rather than by changing
v1 in place.