# Expo SDK JSON Change Audit

> Expo SDK JSON Change Audit is a paid API for AI agents from market.datapackvibe.com, paid per call via x402, $0.01/call, status unknown (last checked 2026-10-24).

Validates and compares before/after JSON documents against the pinned Expo SDK schema, reporting added/removed/changed paths and introduced/resolved validation errors.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-schema-expo-sdk-9062b966-changes?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-24
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/expo-sdk-json-change-audit-367f4795
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_bGo6640Cy4d6LWbhMd5Ks

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 expo-sdk-json-change-audit-367f4795 -d '<json body>'
```

Example prompt: Can you audit my Expo SDK app.json change and tell me what paths were added, removed, or changed, and whether any new schema errors were introduced? Here's the before: {} and the after: {"name":"MyApp","version":"1.0.0","sdkVersion":"50.0.0"}.

## When to prefer this

Choose this endpoint when you need a schema-aware diff of two Expo SDK JSON configuration documents, specifically to identify which changes introduced or resolved schema violations. It is distinct from generic JSON diff tools because it applies the pinned Expo SDK SchemaStore definition to flag rule violations, not just structural differences. Use it when validating Expo app config migrations, CI change audits, or pre-deployment configuration reviews within the Expo ecosystem.

## Known failure modes

- Document exceeds 100 KB limit — request rejected
- JSON nesting depth exceeds 32 levels — rejected
- Invalid JSON submitted (non-parseable) — parsing error returned
- YAML or TOML input provided instead of JSON — not supported
- Network or payment failure — no audit result returned
- Schema definition unavailable or pinned version mismatch — may produce incomplete results

## How this service works

Change audit: Expo SDK: Audit JSON changes and validate before/after for Expo SDK. Uses a pinned SchemaStore definition on this PC. Reports JSON pointers and rule violations, added/removed/changed paths and introduced/resolved errors. Up to 100 KB per document; no YAML/TOML parsing or deployment/security guarantee. 0.01 USDC includes one two-document change audit.

## Output

Returns a structured report listing JSON pointer paths that were added, removed, or changed between the before and after documents, along with any schema rule violations introduced or resolved by the change, based on the pinned Expo SDK SchemaStore definition. Each document may be up to 100 KB and 32 levels deep.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "after": {
   "default": {
    "agent_market_example": true
   },
   "description": "JSON value to validate; maximum 100 KB, 32 levels."
  },
  "before": {
   "default": {},
   "description": "JSON value to validate; maximum 100 KB, 32 levels."
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/expo-sdk-json-change-audit-367f4795/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from market.datapackvibe.com](https://www.zero.xyz/host/market.datapackvibe.com/llms.txt)