Exploring API access
Pull the same mining intelligence you see on the platform directly into your own models, dashboards, and workflows.
Please note: API and MCP access are available as a separate add-on to your Pulse subscription and are set up for you directly by the Pulse team.
Why use the API
If you’re building your own dashboard, feeding a model, or connecting an AI assistant to Pulse data, the API gives you the same coverage as the platform - including companies, assets, financials, drilling, reserves, and more - as structured, queryable data rather than information you’d have to copy out of the product by hand.
What you can access
The public API is a thin, read-only layer over the same audited data that powers the platform, Pulse AI, and MCP.
It covers companies, mining assets, publications, and people, as well as the filter and lookup endpoints you need to build screens and integrations against that data.
Because it is a projection over the same service layer, an endpoint documented here returns the same data you’d see in the product.
The full coverage, down to the specific fields and endpoints available, is set out in the documentation at docs.pulseintelligence.com.
For AI tools specifically, Pulse also runs a Model Context Protocol (MCP) server, so an assistant such as Claude can query your coverage directly and cite the filing behind each answer, without requiring a separate integration.
To connect an AI assistant directly to your Pulse coverage using the Model Context Protocol:
→ Read: Connecting Pulse via MCP
Getting API or MCP access
API and MCP access is a paid add-on, separate from your platform seats, and is set up for you directly by the Pulse team.
Email sales@pulseintelligence.com to request pricing and access to the API or MCP.
Once the add-on is in place, an organisation admin can create the key from Settings → API Keys.
A fresh MFA re-verification is required because a key is a standing credential.
The key is shown once, at creation. Copy it immediately into a secrets manager or environment variable.
Please note: Pulse never stores or displays the plaintext again, so if the key is lost, the only way to regain access is to revoke it and create a new one.
Use the key in the Authorisation header on your requests, for example:
Bearer pulse_a1b2c3d4_
Keys authenticate as your organisation rather than as an individual, so they continue working through staff changes and don’t inherit any one person’s platform permissions.
Actions you can take
From the API and MCP access process, you can:
- Request the add-on for your organisation via sales@pulseintelligence.com.
- Create or revoke a key yourself from Settings → API Keys, if you’re an organisation admin.
- Screen companies or assets by any field available in the product and pull results straight into Python, a notebook, or a warehouse.
- Pull a full company or asset dossier in a single call rather than assembling it from multiple pages.
- Connect an AI client, including Claude, Claude Code, Cursor, or Gemini, via the MCP server, authenticated over OAuth against your own Pulse account.
Where to find full documentation
The complete field-level reference, including every endpoint, its parameters, and worked request and response examples, is available at docs.pulseintelligence.com.
Next steps
To connect Pulse directly to an AI client using MCP:
→ Read: Connecting Pulse via MCP