# host-meta.json Change Audit

> host-meta.json 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).

Audits before/after JSON changes for host-meta.json files, reporting added/removed/changed paths and schema validation errors using a pinned SchemaStore definition.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-schema-host-meta-json-732cef28-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/host-meta-json-change-audit-787eca44
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_0BxAS-p6ISnQnKWtAI0C6

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 host-meta-json-change-audit-787eca44 -d '<json body>'
```

Example prompt: Can you audit the changes I made to my host-meta.json? Here's the before version: {} and the after version: {"links":[{"rel":"lrdd","template":"https://example.com/.well-known/webfinger?resource={uri}"}]} — tell me what paths changed and if any schema rules were violated.

## When to prefer this

Choose this endpoint when you specifically need to audit changes to host-meta.json files and want schema validation grounded in the SchemaStore definition for that format. It is ideal for CI/CD pre-deploy checks, pull request reviews, or any workflow where you need to understand exactly what JSON paths changed and whether schema compliance improved or degraded. Prefer this over generic JSON diff tools when host-meta.json schema correctness matters.

## Known failure modes

- Document exceeds 100 KB size limit — request rejected
- JSON nesting exceeds 32 levels deep — parsing refused
- Invalid JSON submitted (non-parseable content) — error returned
- Payment of 0.01 USDC not completed — request not processed
- YAML or TOML content submitted instead of JSON — not supported

## How this service works

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

Returns a structured audit report listing JSON pointer paths that were added, removed, or changed between the before and after documents, schema rule violations present in each version, newly introduced errors, and errors that were resolved — all validated against a pinned SchemaStore definition for host-meta.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/host-meta-json-change-audit-787eca44/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)