# GitHub Discussion JSON Schema Change Audit

> GitHub Discussion JSON Schema 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-23).

Audits JSON changes between before/after documents against the pinned GitHub Discussion SchemaStore definition, reporting added/removed/changed paths and introduced/resolved validation errors.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-schema-github-discussion-dbf3c6c6-changes?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-23
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/github-discussion-json-schema-change-audit-3b675556
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_9FGU5Qn_19cy3CxxsGhvL

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 github-discussion-json-schema-change-audit-3b675556 -d '<json body>'
```

Example prompt: Can you audit my GitHub Discussion JSON change — here's the before version and the after version — and tell me which paths changed, which schema rules were violated, and whether any new errors were introduced or old ones resolved?

## When to prefer this

Choose this endpoint when you need to validate a specific GitHub Discussion JSON document change against the SchemaStore-pinned schema, particularly when you want to see both a structural diff (added/removed/changed paths) and a validation diff (introduced/resolved errors) in a single audited response. Best for CI/CD pipelines, code review tooling, or migration scripts dealing specifically with GitHub Discussion JSON payloads under 100 KB.

## Known failure modes

- Document exceeds 100 KB limit — request rejected
- JSON nesting depth exceeds 32 levels — parsing fails
- Malformed JSON in before or after field — validation cannot proceed
- YAML or TOML input not supported — must be valid JSON
- Payment of 0.01 USDC not fulfilled — request blocked

## How this service works

Change audit: GitHub Discussion: Audit JSON changes and validate before/after for GitHub Discussion. 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

A structured audit report listing JSON pointer paths that were added, removed, or changed between the before and after documents, along with schema rule violations that were introduced or resolved, based on the pinned GitHub Discussion 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/github-discussion-json-schema-change-audit-3b675556/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)