# Change Audit: publiccode.yml

> Change Audit: publiccode.yml 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 before/after states of a publiccode.yml file, reporting added/removed/changed paths and schema validation errors introduced or resolved.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-schema-publiccode-yml-c56bf7fb-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-publiccode-yml-2b2bc09e
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_IaCduh7Th1-5IfdUTRs1R

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-publiccode-yml-2b2bc09e -d '<json body>'
```

Example prompt: Can you audit my publiccode.yml change — here's the before state and the after state as JSON — and tell me what paths changed, what schema errors were introduced or resolved, and whether the updated version is valid?

## When to prefer this

Choose this endpoint when you specifically need to audit changes to a publiccode.yml file using the SchemaStore definition, and want a diff-aware report that highlights not just current errors but which errors were introduced or resolved by the change. Prefer over generic JSON diff tools when publiccode.yml schema compliance is the goal, and over generic schema validators when change tracking between two states is needed.

## Known failure modes

- Document exceeds 100 KB size limit — request rejected
- Nesting depth exceeds 32 levels — request rejected
- Input is YAML or TOML instead of JSON — not supported, must convert to JSON first
- Malformed JSON in before or after field — parsing error returned
- Network or payment failure via x402 protocol — no audit performed

## How this service works

Change audit: publiccode.yml: Audit JSON changes and validate before/after for publiccode.yml. 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 pointer paths for all added, removed, and changed fields between the before and after documents, along with any schema rule violations introduced or resolved, based on a pinned SchemaStore definition for publiccode.yml. Does not parse YAML or TOML; input must be JSON. Documents are limited to 100 KB and 32 nesting levels each.

## 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-publiccode-yml-2b2bc09e/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)