# cosmos.config.json Change Audit & Validator

> cosmos.config.json Change Audit & Validator 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).

Audits JSON changes between before/after versions of a cosmos.config.json file, reporting added/removed/changed paths and schema rule violations using a pinned SchemaStore definition.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-schema-cosmos-config-json-9151c717-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/cosmos-config-json-change-audit-validator-1c1263f2
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_002tQbqOXFVaE_mZ6FrwP

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 cosmos-config-json-change-audit-validator-1c1263f2 -d '<json body>'
```

Example prompt: Can you audit the changes I made to my cosmos.config.json — here's the before version and the after version — and tell me which JSON paths changed, what schema rules were violated, and whether I introduced or resolved any errors?

## When to prefer this

Choose this endpoint when you need to audit a specific before/after change to a cosmos.config.json file against its SchemaStore definition, particularly when you want precise JSON pointer-level diff reporting combined with schema rule violation detection. It is not a general JSON differ or a deployment/security checker.

## Known failure modes

- Document exceeds 100 KB limit — request rejected
- JSON nesting exceeds 32 levels — request rejected
- Invalid JSON submitted (YAML or TOML not supported) — parse error
- Malformed request body — validation error returned
- Payment not received — 402 response with payment instructions

## How this service works

Change audit: cosmos.config.json: Audit JSON changes and validate before/after for cosmos.config.json. 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

A structured report listing JSON pointer paths that were added, removed, or changed between the before and after documents, along with schema rule violations that were introduced or resolved, based on a pinned SchemaStore definition for cosmos.config.json.

## 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/cosmos-config-json-change-audit-validator-1c1263f2/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)