Developers — Open Pulse
Two ways in: an MCP server at https://api.openpulse.cloud/mcp for assistants, and a REST API under https://api.openpulse.cloud/v1 for programs. Both read one workspace's own data and both need credentials a workspace admin creates.
What this page answers
Does Open Pulse have an API?
Yes. A REST API under https://api.openpulse.cloud/v1, described by an OpenAPI 3.1 document generated from the real route table at https://api.openpulse.cloud/openapi.json, and an MCP server at https://api.openpulse.cloud/mcp.
How do I authenticate?
The REST API takes a workspace API key as a bearer token. Keys are prefixed `op_live_` and are created by a workspace admin. The MCP server is an OAuth 2.1 resource server: it verifies bearer tokens and issues none, and an unauthenticated request returns 401 with the metadata pointing at the authorisation server.
What can a key do?
Whatever its scopes allow, and never more than a member can do. There is deliberately no way to express an administrative action as a scope, so a key cannot administer keys, billing or membership. The 8 scopes are listed below.
Can I use it from Claude or ChatGPT?
Open Pulse is an MCP server, so Claude, ChatGPT, Grok and the Claude Code CLI can read your workspace directly. Ask for this week's high-intent signals and get them, in the chat you already work in.
At a glance
- REST base URL
- https://api.openpulse.cloud/v1
- MCP endpoint
- https://api.openpulse.cloud/mcp (streamable HTTP)
- OpenAPI
- https://api.openpulse.cloud/openapi.json
- MCP server card
- https://api.openpulse.cloud/.well-known/mcp/server-card.json
- API key prefix
- op_live_
- REST auth
- Bearer token, workspace API key
- MCP auth
- OAuth 2.1, resource server only
Scopes
| Scope | Grants |
|---|---|
| signals:read | Read signals — List and read signals, their scores and their reasoning. |
| accounts:read | Read accounts — List companies and what has been found about them. |
| listeners:read | Read listeners — List listeners and read their configuration. Cannot change one. |
| listeners:analyse | Analyse a website — Turn a URL into a listener plan: keywords, exclusions and per-source queries. Rate limited, and counted against your monthly allowance. |
| pipeline:read | Read pipeline — List deals, their stages and the return figures. |
| pipeline:write | Change pipeline — Add deals and move them between stages. |
| collections:write | Manage lists — Save signals to lists, and write notes. |
| export:read | Export — Download the CSV exports. Filtered only: a key is never an admin. |
MCP tools
The server answers `tools/list` with the current set; it is not restated here, because a second copy is a second thing to keep in step and no test can see both.
The tools today are search_signals, get_rollup, get_quality_report.
They are read-only apart from rating a signal and queueing a run. An agent can never create or delete a listener.
Webhooks
The same information in a shape another system can act on. HMAC-signed, retried with backoff, and every attempt kept with its request and response so a failure is debuggable from your side.
Events: signal.created, run.completed, run.failed.
Next
- API reference — Every endpoint, generated from the OpenAPI document.
- MCP guide — Connecting Claude, ChatGPT, Grok or Claude Code.
- Webhook guide — Signature verification and retry behaviour.
- Start the free trial — Creates a workspace. A card is taken up front and nothing is charged during the trial.