# Weverlabs Data Evidence Check

> Weverlabs Data Evidence Check is a paid API for AI agents from weverlabs.com, paid per call via x402, $0.1/call, status unknown (last checked 2026-11-02).

Analyzes a submitted JSON sample for field presence, empty values, types, timestamps, source attribution, and duplicate keys, returning a signed evidence report with receipt.

## Facts

- Endpoint: POST https://weverlabs.com/api/data-evidence-check?utm_source=zero.xyz
- Price: $0.1/call
- Payment: x402
- Status: unknown
- Last checked: 2026-11-02
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/weverlabs-data-evidence-check-143ab580
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_LEJOwyjOWCUyteyDzigCy

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 weverlabs-data-evidence-check-143ab580 -d '<json body>'
```

Example prompt: Run a data evidence check on this JSON sample from our earnings data feed — check for field presence, empty values, type consistency, timestamps, and duplicate keys, and give me back a signed report.

## When to prefer this

Use this endpoint when you need a verifiable, signed audit trail of JSON data quality — especially for financial datasets (earnings, fundamentals, market data, macro, ownership) where field completeness, type correctness, and duplicate key detection must be documented. Prefer this over generic JSON validators when you need a signed receipt for compliance or when source attribution tracking matters.

## Known failure modes

- Payload exceeds 256 KB limit — request rejected
- Invalid JSON submitted — parse error returned
- required_fields contains more than 256 entries — validation error
- endpoint URL does not match ^https?:// pattern — schema validation failure
- dataset_type enum value not recognized — rejected
- Network timeout on large payloads

## How this service works

Data evidence report for a submitted JSON sample: field presence, empty values, types, timestamps, source attribution and duplicate keys, with a signed receipt.

## Output

A structured evidence report covering: which required fields are present or missing, which fields contain empty or null values, detected data types per field, timestamp field analysis, source attribution metadata, any duplicate keys found, and a cryptographically signed receipt confirming the check was performed.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "payload": {
   "anyOf": [
    {
     "type": "object"
    },
    {
     "type": "string"
    }
   ],
   "description": "Sample JSON object or serialized JSON. Maximum 262144 UTF-8 bytes (256 KB). A serialized sample may contain an object or array of records."
  },
  "endpoint": {
   "type": "string",
   "pattern": "^https?://",
   "maxLength": 8192,
   "description": "Original URL, recorded exactly as supplied. Processing uses the submitted sample."
  },
  "dataset_type": {
   "enum": [
    "earnings",
    "fundamentals",
    "market_data",
    "macro",
    "ownership",
    "other"
   ],
   "description": "Selects default field expectations only when required_fields is absent."
  },
  "required_fields": {
   "type": "array",
   "items": {
    "type": "string",
    "maxLength": 1024,
    "minLength": 1
   },
   "maxItems": 256,
   "description": "Absolute JSON pointers, or dot paths with [index] and [*]. Simple paths are relative to each detected record. An explicit empty array selects no default expectations.",
   "uniqueItems": true
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/weverlabs-data-evidence-check-143ab580/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from weverlabs.com](https://www.zero.xyz/host/weverlabs.com/llms.txt)