# Change Audit: ODGS Standard Metrics

> Change Audit: ODGS Standard Metrics 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 changes by comparing before/after documents for ODGS Standard Metrics schema compliance, reporting added/removed/changed paths and introduced/resolved validation errors.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-schema-odgs-standard-metrics-7248d271-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-odgs-standard-metrics-c7e57584
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_6mVGYEjJ41WmaKYNnbl2C

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-odgs-standard-metrics-c7e57584 -d '<json body>'
```

Example prompt: Audit these two ODGS Standard Metrics JSON documents for me — compare the before and after versions and tell me what paths were added, removed, or changed, and whether any new schema violations were introduced or old ones resolved.

## When to prefer this

Choose this endpoint when you specifically need to validate JSON changes against the ODGS Standard Metrics schema definition. It is ideal for CI/CD pipelines, code review workflows, or configuration management scenarios where you need to catch schema regressions, document exactly what changed between two JSON documents, and identify whether errors were introduced or resolved. Not suitable for YAML/TOML, documents over 100 KB, or schemas other than ODGS Standard Metrics.

## Known failure modes

- Document exceeds 100 KB limit — request rejected
- JSON nesting exceeds 32 levels — request rejected
- Malformed JSON in before or after fields — parse error returned
- YAML or TOML input provided instead of JSON — not supported
- Network or payment failure — no audit result returned

## How this service works

Change audit: ODGS Standard Metrics: Audit JSON changes and validate before/after for ODGS Standard Metrics. 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 diff of the two JSON documents against the pinned ODGS Standard Metrics schema, including JSON pointers for all added, removed, and changed paths, a list of validation rule violations, and which errors were introduced or resolved between the before and after documents.

## 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-odgs-standard-metrics-c7e57584/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)