# Allstar Scorecard JSON Change Audit

> Allstar Scorecard 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-18).

Audits JSON changes between two documents against the Allstar Scorecard schema, reporting added/removed/changed paths, JSON pointer violations, and introduced or resolved errors.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-schema-allstar-scorecard-64d0d035-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/allstar-scorecard-json-change-audit-9fdb43e1
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_dfB3D5sLk88iOkFTzEYgB

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 allstar-scorecard-json-change-audit-9fdb43e1 -d '<json body>'
```

Example prompt: Can you audit these two Allstar Scorecard JSON documents — here's the before version and here's the after version — and tell me what paths changed, any new schema violations that were introduced, and any errors that got resolved?

## When to prefer this

Use this endpoint when you need to audit changes specifically to Allstar Scorecard JSON documents against a pinned SchemaStore schema definition, and want to see both a structural diff (added/removed/changed paths) and a compliance diff (introduced vs. resolved rule violations) in a single call. Prefer this over generic JSON diff tools when Allstar Scorecard schema compliance is required.

## Known failure modes

- Document exceeds 100 KB limit — request rejected
- JSON nesting exceeds 32 levels — request rejected
- Malformed JSON in before or after field — parse error returned
- YAML or TOML input provided instead of JSON — not supported
- Missing or empty after document — validation cannot proceed

## How this service works

Change audit: Allstar Scorecard: Audit JSON changes and validate before/after for Allstar Scorecard. 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 audit report identifying JSON pointer paths that were added, removed, or changed between the before and after documents, along with any schema rule violations present in each version, newly introduced errors, and errors that were resolved — all evaluated against a pinned Allstar Scorecard SchemaStore definition.

## 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/allstar-scorecard-json-change-audit-9fdb43e1/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)