# Change Audit: Codex Skill Metadata

> Change Audit: Codex Skill Metadata 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-19).

Audits JSON before/after changes for Codex Skill Metadata schema compliance, reporting added/removed/changed paths and introduced/resolved validation errors.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-schema-codex-skill-metadata-35c89150-changes?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-19
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/change-audit-codex-skill-metadata-0b56ba62
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_BF1OjFM4hsW8W5WBYHOPv

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-codex-skill-metadata-0b56ba62 -d '<json body>'
```

Example prompt: Can you audit the changes I made to my Codex Skill Metadata JSON — here's the before version and the after version — and tell me which paths changed, what was added or removed, and whether any new schema violations were introduced?

## When to prefer this

Use this endpoint when you specifically need to validate changes to Codex Skill Metadata JSON against its pinned SchemaStore definition and want a structured diff of added/removed/changed paths alongside introduced or resolved schema errors. Prefer this over generic JSON diff tools when Codex Skill Metadata schema compliance is required.

## Known failure modes

- Document exceeds 100 KB limit — request rejected
- Nesting depth exceeds 32 levels — request rejected
- Input is not valid JSON (YAML/TOML not supported) — parse error returned
- Both before and after are identical — empty diff report
- Schema definition unavailable or pinned version mismatch — validation may be incomplete

## How this service works

Change audit: Codex Skill Metadata: Audit JSON changes and validate before/after for Codex Skill Metadata. 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 report listing JSON pointer paths that were added, removed, or changed between the before and after documents, along with any schema rule violations that were introduced or resolved, based on a pinned Codex Skill Metadata 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/change-audit-codex-skill-metadata-0b56ba62/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)