# Change Audit: Pull Request Labeler

> Change Audit: Pull Request Labeler 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-15).

Audits JSON before/after changes for Pull Request Labeler configuration files, reporting validation errors, added/removed/changed paths, and resolved/introduced rule violations using a pinned SchemaStore definition.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-schema-pull-request-labeler-5e97a0fe-changes?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/change-audit-pull-request-labeler-dd05371e
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_ZzRBgI2QWZTMverM9V1PN

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-pull-request-labeler-dd05371e -d '<json body>'
```

Example prompt: Can you audit my Pull Request Labeler config change — here's the before JSON and the after JSON — and tell me what paths were added or removed, and whether any new schema violations were introduced or old ones got fixed?

## When to prefer this

Choose this endpoint when you specifically need to validate Pull Request Labeler configuration JSON against its pinned SchemaStore schema and want a structured diff of what changed between two versions, including which errors were introduced or resolved. It is purpose-built for this schema rather than being a generic JSON differ or schema validator, making it more precise for PR labeler configs than general-purpose tools.

## Known failure modes

- Document exceeds 100 KB limit — request rejected
- Nesting depth exceeds 32 levels — parsing refused
- Non-JSON input (YAML, TOML) submitted — not parsed or converted
- Malformed JSON in before or after field — parse error returned
- Payment of 0.01 USDC not fulfilled — x402 payment required error

## How this service works

Change audit: Pull Request Labeler: Audit JSON changes and validate before/after for Pull Request Labeler. 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 pointers with rule violations, paths that were added, removed, or changed between the before and after documents, and a breakdown of validation errors that were introduced or resolved by the change. Covers documents up to 100 KB each with up to 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-pull-request-labeler-dd05371e/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)