Recorded Future · Schema
ThreatActorsRequest
JSON object specifying pagination of the threat actor list
CybersecurityThreat IntelligenceIntelligence CloudBrand IntelligenceIdentity IntelligenceVulnerability IntelligenceAI Analyst
Properties
| Name | Type | Description |
|---|---|---|
| name | string | This string value can be used for a case insensitive, free text search of threat actor names, common names, or aliases. For example, using `name":"panda"` will yield a search result with over 300 thre |
| limit | integer | This integer value sets the upper limit on the number of threat actors returned. |
| offset | string | This string value should be received in a prior search, and is used to deliver the next set of threat actors in the search response. |
JSON Schema
{
"$schema": "https://json-schema.org/draft/2020-12/schema",
"$id": "https://raw.githubusercontent.com/api-evangelist/recorded-future/main/json-schema/recorded-future-threat-actors-request-schema.json",
"title": "ThreatActorsRequest",
"description": "JSON object specifying pagination of the threat actor list",
"x-generated": "2026-10-20",
"x-method": "derived",
"x-generator": "derive-json-schema.py",
"x-source": "openapi/recorded-future-threat-api-openapi.yml#/components/schemas/ThreatActorsRequest",
"type": "object",
"properties": {
"name": {
"description": "This string value can be used for a case insensitive, free text search of threat actor names, common names, or aliases. For example, using `name\":\"panda\"` will yield a search result with over 300 threat actors that have the word \"panda\" somewhere in its name, common names, or aliases. Advanced searches are supported using a prefix in the search string. For example, using `\"name\":\"exact:panda\"`yields only threat actor(s) whose name is just \"Panda\". <table> <tr> <th>Prefix</th> <th>Match type</th> <th>Description</th> </tr> <tr> <td>no prefix</td> <td>freetext match (default)</td> <td>Returns threat actors where the search string matches somewhere in a name, a common name or an alias (case-insensitive).</td> </tr> <tr> <td>exact:</td> <td>exact match</td> <td>Returns threat actors where the search string exactly matches a name, a common name or an alias.</td> </tr> <tr> <td>prefix:</td> <td>prefix match</td> <td>Returns threat actors where the search string matches the beginning of a name, a common name or an alias.</td> </tr> <tr> <td>infix:</td> <td>infix match</td> <td>Returns threat actors where the search string is contained anywhere in a name, a common name or an alias.</td> </tr> <tr> <td>relevance:</td> <td>1 word: relevance match<br/> 2+ words: relevance phrase match</td> <td>Returns threat actors that have text attributes relevant to the given search word or search phrase (in the same order). The results are sorted by decreasing relevance.</td> </tr> </table>",
"type": "string"
},
"limit": {
"description": "This integer value sets the upper limit on the number of threat actors returned.",
"type": "integer",
"format": "int32",
"minimum": 1,
"maximum": 10000,
"default": 10000
},
"offset": {
"description": "This string value should be received in a prior search, and is used to deliver the next set of threat actors in the search response.",
"type": "string"
}
},
"required": [
"limit"
]
}
Work with this as data
Every JSON Schema here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for schemas
4 MCP tools reach this
find_json_schemasBrowse and filter every JSON Schema in the catalog.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
This JSON Schema
curl "https://apis.io/api/v1/json-schemas/recorded-future-threat-actors-request"
All schemas
curl "https://apis.io/api/v1/json-schemas?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.
A second provider on the same verified email joins the account you already have.