# Relaystation Data Diff

> Relaystation Data Diff is a paid API for AI agents from api.relaystation.ai, paid per call via x402, $0.01/call, status unknown (last checked 2026-09-14).

Computes a row-level changeset between two tables, returning added, removed, and changed rows

## Facts

- Endpoint: POST https://api.relaystation.ai/v1/data/diff
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/relaystation-data-diff-403824af
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_ARNZ8t6HUlWK1TA7zqr8C

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 relaystation-data-diff-403824af -d '<json body>'
```

Example prompt: Compare these two JSON tables — yesterday's snapshot and today's export — and give me a row-level diff showing which rows were added, removed, or changed between them.

## When to prefer this

Choose this endpoint when you need a precise, row-level diff between two tabular datasets and want a structured changeset (added/removed/changed) rather than a simple hash or summary. It is ideal for ETL incremental loading, data auditing, reconciliation between two system exports, or change-data-capture workflows where you need exact row attribution. Prefer it over manual diffing scripts when operating inside an agentic pipeline that can handle x402 micropayments automatically.

## Known failure modes

- Malformed or incompatible table schemas — rows cannot be matched if primary keys are inconsistent or missing
- Payload too large — very large tables may time out or incur high per-MB costs
- Mismatched column structures between the two tables causing comparison errors
- Invalid JSON or CSV format causing parse failure
- Insufficient x402 payment balance for data volume processed

## How this service works

$0.0002/MB. Row-level changeset between two tables — added, removed, and changed rows. 1¢ x402 min; remainder auto-credits — relaystation.ai/penny

## Output

A structured changeset object containing three collections: added rows (present in table B but not A), removed rows (present in table A but not B), and changed rows (present in both but with differing field values), billed at $0.0002/MB of input data with a 1¢ x402 minimum charge and any remainder auto-credited.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "method",
    "bodyType",
    "body"
   ],
   "properties": {
    "body": {
     "properties": {}
    },
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "POST",
      "PUT",
      "PATCH"
     ],
     "type": "string"
    },
    "bodyType": {
     "enum": [
      "json",
      "form-data",
      "text"
     ],
     "type": "string"
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object"
    }
   }
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/relaystation-data-diff-403824af/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.relaystation.ai](https://www.zero.xyz/host/api.relaystation.ai/llms.txt)