# Aurora Agile Meta-Framework JSON Change Auditor

> Aurora Agile Meta-Framework JSON Change Auditor 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-18).

Audits JSON document changes by comparing before/after states against the Aurora Agile Meta-Framework schema, reporting added/removed/changed paths and validation errors introduced or resolved.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-schema-aurora-agile-meta-framewor-3246ed41-changes?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-18
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/aurora-agile-meta-framework-json-change-auditor-87011571
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_7_REdxt0tYxHMCMd2R_vM

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 aurora-agile-meta-framework-json-change-auditor-87011571 -d '<json body>'
```

Example prompt: Can you audit this change to our Aurora Agile Meta-Framework JSON config — here's the before document and the after document — and tell me which paths changed, which were added or removed, and whether any new schema violations were introduced or old ones got fixed?

## When to prefer this

Use this endpoint when you need to audit a specific before/after JSON change against the Aurora Agile Meta-Framework schema definition, especially to detect newly introduced violations or confirm that errors were resolved. Prefer it over generic JSON diff tools when Aurora Agile Meta-Framework schema compliance is the concern, not just structural difference.

## Known failure modes

- Document exceeds 100 KB limit — request rejected
- Nesting depth exceeds 32 levels — parsing fails
- Input is YAML or TOML instead of JSON — not supported
- Malformed JSON in before or after field — parse error returned
- Network or payment failure — no audit result returned

## How this service works

Change audit: Aurora Agile Meta-Framework: Audit JSON changes and validate before/after for Aurora Agile Meta-Framework. 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 including JSON pointers to changed locations, a list of added/removed/changed paths between the two documents, rule violations found in each version, and a summary of errors introduced or resolved by the change. Covers documents up to 100 KB with up to 32 nesting levels.

## 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/aurora-agile-meta-framework-json-change-auditor-87011571/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)