Pulsedive
Pulsedive · Developer tools
Threat intelligence on IPs, domains and URLs
The client pastes their API key from Pulsedive's settings. We store it encrypted.
Tested against Pulsedive's live API.
Building with Pulsedive? The docs have setup steps and code for every tool.
Open the Pulsedive docsTools
Your agent calls any endpoint of Pulsedive's API with the request tool, with the client's access attached.
Base URL for request
https://pulsedive.com
request
HTTPS ANY /v1/clients/{clientId}/pulsedive/{path}
Any endpoint of Pulsedive's own API, with the client's access attached.
- servicestringrequired
- This service: pulsedive
- methodstringrequired
- GET, POST, PUT, PATCH or DELETE
- pathstringrequired
- The path under https://pulsedive.com
- queryobjectoptional
- Query parameters
- bodyobjectoptional
- A JSON body
Over MCP every tool also takes client_id, from list_clients. Over HTTPS send it as clientId to https://api.operate.as/v1.
What the client approves
- Use the Pulsedive key you paste, with only the access you gave that key
Get started
Send your next client one link
Add a client, select the services, copy the link. You'll get an email the moment their access is ready. Start free, no card required. Paid plans are one flat monthly price, and a busy month never takes your agents offline.