# Zinin M2M Hub – US Brand Evidence Snapshot Diff

> Zinin M2M Hub – US Brand Evidence Snapshot Diff is a paid API for AI agents from api.timzinin.com, paid per call via x402, $0.05/call, status unknown (last checked 2026-10-13).

Computes a structured diff between two US brand evidence snapshots, identifying what changed between a 'before' and 'after' state

## Facts

- Endpoint: POST https://api.timzinin.com/api/us-brand-evidence-snapshot-diff?utm_source=zero.xyz
- Price: $0.05/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-13
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/zinin-m2m-hub-us-brand-evidence-snapshot-diff-f0b5509a
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_ormed_6NU9CVE_wOYtyik

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 zinin-m2m-hub-us-brand-evidence-snapshot-diff-f0b5509a -d '<json body>'
```

Example prompt: Compare these two US brand evidence snapshots and tell me what changed — the first one is the 'before' state and the second is 'after', using schema version 1.0.

## When to prefer this

Choose this endpoint when you need to programmatically compute a structured diff between two US brand evidence snapshots — especially when you have a clear before/after pair and need to identify precisely what changed in brand evidence data. Prefer this over manual comparison or generic JSON diff tools when the domain is US brand presence and evidence-level granularity is required.

## Known failure modes

- Invalid or missing primarySide enum value (must be 'before' or 'after') causes request rejection
- Unsupported schemaVersion (must be '1.0') returns a validation error
- Malformed or incomplete snapshot objects in primary or counterpart fields cause parsing errors
- Payment failure via x402 results in 402 response before processing
- Mismatched schema versions between primary and counterpart snapshots may produce unreliable diffs

## How this service works

Pay-per-call data & tool APIs

## Output

A structured diff object detailing the changes between the two brand evidence snapshots, including added, removed, and modified evidence fields — allowing the caller to understand exactly what shifted between the primary (before or after) and counterpart states.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "primary": {
   "$ref": "#/definitions/bazaarShared0"
  },
  "counterpart": {
   "$ref": "#/definitions/bazaarShared0"
  },
  "primarySide": {
   "enum": [
    "before",
    "after"
   ],
   "type": "string"
  },
  "schemaVersion": {
   "enum": [
    "1.0"
   ],
   "type": "string"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/zinin-m2m-hub-us-brand-evidence-snapshot-diff-f0b5509a/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.timzinin.com](https://www.zero.xyz/host/api.timzinin.com/llms.txt)