Recorded Future
Recorded Future · Developer tools
Threat intelligence: IPs, domains, hashes, vulnerabilities and alerts
The client pastes their API token from Recorded Future's settings. We store it encrypted.
Tested against Recorded Future's live API.
Building with Recorded Future? The docs have setup steps and code for every tool.
Open the Recorded Future docsTools
Your agent calls any endpoint of Recorded Future's API with the request tool, with the client's access attached.
Base URL for request
https://api.recordedfuture.com/v2
request
HTTPS ANY /v1/clients/{clientId}/recorded-future/{path}
Any endpoint of Recorded Future's own API, with the client's access attached.
- servicestringrequired
- This service: recorded-future
- methodstringrequired
- GET, POST, PUT, PATCH or DELETE
- pathstringrequired
- The path under https://api.recordedfuture.com/v2
- 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 Recorded Future 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.