# pnpm Workspace Config Change Audit

> pnpm Workspace Config Change Audit 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).

Validates and audits JSON changes to pnpm-workspace.yaml configuration files, reporting schema violations, added/removed/changed paths, and introduced or resolved errors between before and after states.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-schema-pnpm-workspace-pnpm-worksp-717625b2-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/pnpm-workspace-config-change-audit-03e45166
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_P8iHWb5RPJBej3mkKE-Ls

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 pnpm-workspace-config-change-audit-03e45166 -d '<json body>'
```

Example prompt: Can you audit the changes I made to my pnpm-workspace.yaml — here's the before version and the after version — and tell me if any schema rules were violated, what fields were added or removed, and whether any new errors were introduced?

## When to prefer this

Choose this endpoint when you need schema-level diff auditing specifically for pnpm-workspace.yaml files, particularly when you want to catch schema violations against a pinned SchemaStore definition and get structured JSON pointer reports on what changed. Prefer it over generic JSON diff tools when pnpm workspace schema compliance matters, or when you need introduced/resolved error tracking rather than a plain structural diff.

## Known failure modes

- Document exceeds 100 KB limit — request rejected
- JSON nesting deeper than 32 levels — parsing refused
- Invalid JSON submitted (YAML/TOML not parsed) — parse error returned
- Network or service unavailability — HTTP 5xx error
- Payment failure via x402 protocol — transaction rejected

## How this service works

Change audit: pnpm Workspace (pnpm-workspace.yaml): Audit JSON changes and validate before/after for pnpm Workspace (pnpm-workspace.yaml). 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 to violations, schema rule infractions, lists of added/removed/changed paths between the before and after documents, and a summary of newly introduced versus resolved errors — all based on a pinned SchemaStore definition for pnpm-workspace.yaml.

## 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/pnpm-workspace-config-change-audit-03e45166/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)