# Change Audit: appsscript.json

> Change Audit: appsscript.json 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 between a before and after version of appsscript.json, validating both against a pinned SchemaStore definition and reporting added/removed/changed paths and introduced/resolved errors.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-schema-appsscript-json-874e3211-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-appsscript-json-dc7eba62
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_hdpNGqa59oGPWSiut6SCy

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-appsscript-json-dc7eba62 -d '<json body>'
```

Example prompt: Can you audit the changes I made to my appsscript.json — here's the before version and the after version — and tell me which JSON paths changed and whether I introduced any new schema errors?

## When to prefer this

Choose this endpoint when you specifically need to audit changes to a Google Apps Script manifest file (appsscript.json) against its canonical SchemaStore schema. It is purpose-built for appsscript.json and uses a pinned schema definition, making it more reliable for that specific file type than a generic JSON diff or schema validator. Prefer it when you need both a structural diff (added/removed/changed paths) and schema compliance validation in a single call.

## Known failure modes

- Document exceeds 100 KB limit — request rejected
- JSON nesting exceeds 32 levels — parsing fails
- Malformed JSON in before or after field — validation cannot proceed
- Non-JSON format (YAML, TOML) supplied — not supported
- Network or payment failure — no result returned

## How this service works

Change audit: appsscript.json: Audit JSON changes and validate before/after for appsscript.json. 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 of JSON pointer-level differences between the before and after appsscript.json documents, including added, removed, and changed paths, schema rule violations present in each version, newly introduced errors, and errors resolved by the change. Validated against a pinned SchemaStore definition for appsscript.json.

## 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-appsscript-json-dc7eba62/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)