# Change Audit: GAMA

> Change Audit: GAMA 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-20).

Validates and audits JSON changes between a before and after document for the GAMA schema, reporting added/removed/changed paths and introduced/resolved validation errors.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-schema-gama-9f475a49-changes?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-20
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/change-audit-gama-efb3752c
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_dcTVL1OO6FtbUCVRm3e0G

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-gama-efb3752c -d '<json body>'
```

Example prompt: Can you audit the changes I made to this GAMA JSON config? Here's the before document and the after document — tell me what paths changed, what schema rules were violated, and whether I introduced or resolved any errors.

## When to prefer this

Use this endpoint when you need to audit changes between two versions of a GAMA-format JSON document and want both a structural diff (added/removed/changed paths) and a schema validation diff (introduced/resolved errors) in a single call. Prefer this over generic JSON diff tools when GAMA-specific schema rules matter, and over full deployment pipelines when you only need a lightweight pre-flight check without deployment or security guarantees.

## Known failure modes

- Document exceeds 100 KB limit — request rejected
- Nesting depth exceeds 32 levels — parsing error
- Invalid JSON submitted (YAML/TOML not supported) — parse failure
- Payment not included or insufficient — 402 response
- Schema definition unavailable or mismatched — validation may be incomplete

## How this service works

Change audit: GAMA: Audit JSON changes and validate before/after for GAMA. 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 diff of the two JSON documents scoped to the GAMA schema: JSON pointers to added, removed, and changed paths; validation rule violations present in each version; and a list of errors that were introduced or resolved by the change. Up to 100 KB per document, max 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-gama-efb3752c/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)