# Change Audit: GitHub Action Schema Validator

> Change Audit: GitHub Action Schema Validator 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).

Audits JSON changes for GitHub Action configurations by validating before/after documents against a pinned SchemaStore definition, reporting added/removed/changed paths and introduced/resolved errors.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-schema-github-action-fb63685d-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/change-audit-github-action-schema-validator-9f9975cc
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_y_okjW6M8FzgwbNA_NC7A

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 change-audit-github-action-schema-validator-9f9975cc -d '<json body>'
```

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

## When to prefer this

Choose this endpoint when you need to validate specifically GitHub Action configuration JSON changes against a pinned SchemaStore definition, with a structured diff of added/removed/changed paths and a clear report of introduced vs. resolved schema errors. Prefer it over generic JSON diff tools when schema compliance and rule violation reporting matters, and over generic schema validators when you need change-level comparison rather than single-document validation.

## Known failure modes

- Document exceeds 100 KB limit — request rejected
- Nesting depth exceeds 32 levels — validation may fail
- YAML or TOML input format not supported — must convert to JSON first
- Malformed JSON in before or after field — parse error returned
- Non-GitHub-Action schema content validated against wrong definition — incorrect results

## How this service works

Change audit: GitHub Action: Audit JSON changes and validate before/after for GitHub Action. 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 pointers and rule violations, paths that were added, removed, or changed between the before and after documents, and which errors were introduced or resolved by the change. Covers documents up to 100 KB each 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/change-audit-github-action-schema-validator-9f9975cc/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)