# BRAINIAC Device Consistency Check

> BRAINIAC Device Consistency Check is a paid API for AI agents from www.brainiac.software, paid per call via x402, $0.03/call, status unknown (last checked 2026-11-12).

Analyzes device fingerprint fields for internal contradictions that indicate ad fraud, emulators, or spoofed device signals

## Facts

- Endpoint: POST https://www.brainiac.software/api/v1/ad-fraud/device-consistency-check?utm_source=zero.xyz
- Price: $0.03/call
- Payment: x402
- Status: unknown
- Last checked: 2026-11-12
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/brainiac-device-consistency-check-e3742541
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_IFPqHuYxVl7UJ7cG4Vno2

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability brainiac-device-consistency-check-e3742541 -d '<json body>'
```

Example prompt: Check whether this device fingerprint is internally consistent and flag any contradictions that might indicate fraud: OS is Android, model is iPhone 14 Pro, device type is phone, screen is 1170x2532, pixel ratio 3, touch enabled, architecture arm64.

## When to prefer this

Use this endpoint when you have device fingerprint metadata from a mobile ad install, impression, or click event and want to detect internal contradictions before attributing conversions or approving payouts. It is ideal for lightweight, per-event fraud pre-screening at $0.03/call with no account required, paying via USDC on Base. Prefer this over full device identity lookup services when you only need to validate internal field consistency rather than confirm physical device identity.

## Known failure modes

- Missing fields lower confidence but do not trigger fraud signals — partial payloads are accepted
- Contradictions only reflect internal inconsistency, not confirmed identity of the physical device
- Simulator flag presence can legitimately explain OS/architecture mismatches, reducing false positives
- Unusual but valid device configurations may surface as signals requiring human review
- No network-side verification is performed — only the supplied fields are compared against each other

## How this service works

Pay-per-call APIs for AI agents: OFAC sanctions screening, compliance checks, token security, and Base chain data via x402. No account. Fixed USDC price. MCP-ready.

## Output

Returns a JSON object with a verdict (e.g. 'review', 'pass', 'fail'), a confidence level, a list of detected signals with type, severity, explanation, and basis, a human-readable analysis summary, evidence array, and a limitations list explaining what the check can and cannot determine about the physical device.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "device": {
   "type": "object",
   "properties": {
    "os": {
     "type": "string",
     "maxLength": 40
    },
    "model": {
     "type": "string",
     "maxLength": 80
    },
    "touch": {
     "type": "boolean"
    },
    "osVersion": {
     "type": "string",
     "maxLength": 40
    },
    "simulator": {
     "type": "boolean"
    },
    "deviceType": {
     "enum": [
      "phone",
      "tablet",
      "desktop",
      "tv",
      "other"
     ],
     "type": "string"
    },
    "pixelRatio": {
     "type": "number",
     "maximum": 10,
     "minimum": 0
    },
    "screenWidth": {
     "type": "integer",
     "maximum": 20000,
     "minimum": 0
    },
    "architecture": {
     "type": "string",
     "maxLength": 40
    },
    "screenHeight": {
     "type": "integer",
     "maximum": 20000,
     "minimum": 0
    }
   },
   "additionalProperties": false
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "signals": [
   {
    "type": "android_apple_model",
    "basis": "fact",
    "fields": [
     "device.os",
     "device.model"
    ],
    "severity": "high",
    "explanation": "The OS reads as Android and the model name reads as an Apple phone or tablet."
   }
  ],
  "success": true,
  "verdict": "review",
  "analysis": "Some supplied device fields contradict each other. That does not identify the physical device.",
  "evidence": [],
  "confidence": "high",
  "limitations": [
   "Device fields are compared only with each other. No device identity is looked up or confirmed.",
   "A simulator flag, when supplied, explains an OS and architecture mismatch.",
   "Screen size and touch support do not prove which physical device was used.",
   "Missing fields lower confidence. They do not add fraud risk."
  ]
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/brainiac-device-consistency-check-e3742541/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from www.brainiac.software](https://www.zero.xyz/host/www.brainiac.software/llms.txt)
