Check device characteristic consistency API

Compare caller-supplied device type, OS, model, screen, and architecture. No device identity is looked up.

The Check device characteristic consistency operation is part of the Ad Fraud Intelligence API on BRAINIAC.software. Compare caller-supplied device type, OS, model, screen, and architecture. No device identity is looked up. It is exposed as POST /api/v1/ad-fraud/device-consistency-check and priced at $0.03 USDC on Base. Payment uses the x402 exact scheme: an unpaid call returns HTTP 402 with payment requirements; after paying the exact USDC amount, retry the same request with a payment-signature header and Idempotency-Key. No account and no API key are required. Data sources for this product: Caller-supplied click, browser, device, conversion, and campaign records processed locally Limitations: No ad platform, IP intelligence, or device-reputation service is contacted. An IP address is not used to call a visitor a bot, and location is not inferred from it. User-Agent strings, JavaScript signals, and fingerprints are caller-supplied and can be forged. A single click or a weak indicator is not a fraud accusation. Missing fields lower confidence and do not add risk. Historical duplicates and campaign patterns are visible only when those records are included in the request. Outputs are compliance prechecks, drafts, or data lookups for human review. They are not official determinations, legal advice, identity confirmation, or certified filings. Related operations in this group include Detect ad-click automation signals, Check browser property consistency, Analyze click timing, Detect duplicate click identifiers. Open the group documentation for the full request schema, field notes, and response examples before integrating.

POST$0.03 USDC
/api/v1/ad-fraud/device-consistency-check

Example request

curl -i -X POST "https://www.brainiac.software/api/v1/ad-fraud/device-consistency-check" \
  -H 'content-type: application/json' \
  -H 'Idempotency-Key: <fresh-64-character-random-hex-key>' \
  --data-binary @- <<'JSON'
{
  "device": {
    "deviceType": "phone",
    "os": "Android",
    "model": "iPhone 15",
    "screenWidth": 390,
    "screenHeight": 844,
    "touch": true
  }
}
JSON

An unpaid probe returns HTTP 402 with x402 payment requirements. After paying the exact USDC amount on Base, retry the identical request with a payment-signature header.

FAQ

  • Do I need an API key? No. Pay the listed USDC amount with x402.
  • What network? Base (eip155:8453), USDC.
  • Is this an official determination? No. Results are for human review against the cited sources.

Related APIs

Ad Fraud Intelligence APIFull docsHow it works