# Change Audit: Catalog Info Backstage

> Change Audit: Catalog Info Backstage 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).

Validates and audits JSON changes (before/after) for Backstage catalog-info files using a pinned SchemaStore definition, reporting added/removed/changed paths and introduced/resolved schema errors.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-schema-catalog-info-backstage-eb7ea41a-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-catalog-info-backstage-6a9d3024
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_p6unRCoKhgEdpFmcY05yK

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-catalog-info-backstage-6a9d3024 -d '<json body>'
```

Example prompt: Can you audit the change to our Backstage catalog-info entity — here's the before JSON and the after JSON — and tell me what paths changed and whether any new schema violations were introduced?

## When to prefer this

Choose this endpoint when you specifically need to validate Backstage catalog-info JSON documents against a pinned SchemaStore schema and get a structured diff of what changed between two versions. It is purpose-built for Backstage catalog entities, unlike generic JSON diff tools that have no schema awareness, and unlike general-purpose schema validators that don't produce before/after change reports.

## 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
- Payment not provided or insufficient — 402 response
- SchemaStore definition unavailable or pinned version mismatch — validation may be incomplete

## How this service works

Change audit: Catalog Info Backstage: Audit JSON changes and validate before/after for Catalog Info Backstage. 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 audit report including JSON pointers for all added, removed, and changed paths between the before and after documents, a list of schema rule violations introduced or resolved by the change, and any other validation errors — scoped to the Backstage catalog-info 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-catalog-info-backstage-6a9d3024/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)