ThreatScore RPC

JSON-RPC 2.0 method for running a ThreatScore quick scan via QuickNode.

Endpoint

POST https://YOUR_QUICKNODE_ENDPOINT_HERE.com

Your QuickNode endpoint handles authentication (URL key or headers). Replace YOUR_QUICKNODE_ENDPOINT_HERE.com with your provisioned endpoint.

Request schema (JSON-RPC 2.0)

Field	Type	Required	Value
jsonrpc	string	Yes	2.0
method	string	Yes	ss_quickscan
params	array (ordered)	Yes	[contract_address, chain_id, explorer_id]
id	string / number	Yes	Any client-chosen identifier (e.g., 1)

Params order

Param	Type	Description
contract_address	string	Target contract address (checksummed or hex).
chain_id	string	EVM chain ID (e.g., "1" for Ethereum mainnet).
explorer_id	string	Explorer/provider identifier your backend expects (e.g., "1").

Examples

cURL

curl https://YOUR_QUICKNODE_ENDPOINT_HERE.com \
  -X POST \
  -H "Content-Type: application/json" \
  --data '{
    "method": "ss_quickscan",
    "params": ["0x3A32c2BB167BCC7f5E7fE891526e97079Da4ce88", "1", "1"],
    "id": 1,
    "jsonrpc": "2.0"
  }'

Python (requests)

Responses

Success

{
  "jsonrpc": "2.0",
  "id": 1,
  "result": {
    "...": "scan details"
  }
}

Error

Notes

• Keep params exactly in order: [contract_address, chain_id, explorer_id].

• Auth is handled by your QuickNode endpoint (URL key or headers).

• Use string values for chain_id and explorer_id.