---
title: "Match a kit or malware fingerprint ID against the corpus"
method: POST
path: "/v1/payg/scamkit-match"
tags: ["x402 pay-per-call"]
---

# Match a kit or malware fingerprint ID against the corpus

`POST /v1/payg/scamkit-match`

## Request

- Base URL: `https://api.relayshield.net`
- URL: `https://api.relayshield.net/v1/payg/scamkit-match`
- Auth: none required

Cheap re-check for dashboards and bots watching for kit reuse: look up an existing kit_<sha256> or malware_<sha256> fingerprint ID and get its family (auto-suggested, pending approval), confidence, verdict, evidence, and sighting history. Malware rows return malware_family plus the live Malpedia detail record. An unknown ID is never reported as safe — only as no-match with an explicit not-a-guarantee caveat.

**Billing.** $0.10 in USDC per call over x402, on Base or Solana. No API key, no signup and no
subscription. Send the request with no payment header, take the `402` challenge that comes back,
pay it, and repeat the request. Only successful calls are charged.

## Request body

- object
  - `fingerprint_id` string, required: kit_<sha256> or malware_<sha256> fingerprint ID to match (64 hex chars after the prefix).

## Response `200`

Payment settled and the check ran. `ok` is true and `data` holds the result.

- object
  - `ok` true, required
  - `data` object, required

## Other responses

- `400`: A required field is missing or malformed. Never billed.
- `402`: Payment required. The body carries a complete x402 version 2 challenge with the accepted networks, the amount in USDC base units, and the recipient. Pay it and repeat the request with the payment header.
- `405`: Wrong HTTP method. Every endpoint is POST.

---

[API](https://skmtc.dev/relayshield/apis/relayshield-api.md) · [All operations](https://skmtc.dev/relayshield/apis/relayshield-api/llms.txt) · [OpenAPI document](https://skmtc.dev/relayshield/apis/relayshield-api/revisions/4d4721b936dd?raw)