# dtool Dataset Metadata Change Audit

> dtool Dataset Metadata 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-18).

Validates and diffs two JSON documents representing dtool dataset metadata, reporting added/removed/changed paths and schema rule violations using a pinned SchemaStore definition.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-schema-dtool-dataset-metadata-b0d4dcc6-changes?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-18
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/dtool-dataset-metadata-change-audit-cad35902
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_PKsg7Wv1PB4-BsOpuMnQh

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 dtool-dataset-metadata-change-audit-cad35902 -d '<json body>'
```

Example prompt: Can you audit the changes I made to my dtool dataset metadata? Here's the before version and the after version — tell me what paths changed, what schema rules were violated, and whether I introduced any new errors.

## When to prefer this

Choose this endpoint when you specifically need to audit changes to dtool dataset metadata JSON against a pinned SchemaStore definition. It is purpose-built for the dtool ecosystem and provides both a structural diff and schema-compliance report in a single call, making it ideal for CI pipelines, data stewardship workflows, or pre-publish validation steps where dtool metadata correctness is critical.

## Known failure modes

- Document exceeds 100 KB limit — request rejected
- Nesting depth exceeds 32 levels — parsing fails
- Invalid JSON submitted (YAML or TOML not supported) — parse error returned
- Malformed request body — validation error
- Payment not included or insufficient — 402 response

## How this service works

Change audit: dtool dataset metadata: Audit JSON changes and validate before/after for dtool dataset 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

Returns a structured report containing JSON pointers for all added, removed, and changed paths between the before and after documents, a list of schema rule violations for each document, and a summary of errors introduced or resolved by the change. Limited to documents up 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/dtool-dataset-metadata-change-audit-cad35902/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)