# Change Audit: Hammerkit

> Change Audit: Hammerkit 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).

Validates and diffs two Hammerkit JSON documents (before/after), reporting added, removed, and changed paths along with schema rule violations using a pinned SchemaStore definition.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-schema-hammerkit-02977005-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-hammerkit-c5b875b3
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_n0FhvAR9EFgImDXwZbPK5

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-hammerkit-c5b875b3 -d '<json body>'
```

Example prompt: Compare these two Hammerkit JSON configs for me — the before version is my old config and the after is my updated one — and tell me what paths changed, what new schema violations appeared, and what errors got fixed.

## When to prefer this

Use this endpoint specifically when you need to validate Hammerkit JSON configurations against a pinned SchemaStore definition and understand the delta between two versions. It is ideal for CI pipelines, PR reviews, or debugging config regressions where you need both structural diff information and schema compliance checking in one call. Prefer this over generic JSON diff tools when Hammerkit-specific schema rules matter.

## Known failure modes

- Document exceeds 100 KB limit — request rejected
- JSON nesting depth exceeds 32 levels — request rejected
- Malformed JSON in before or after field — parse error returned
- Non-JSON formats like YAML or TOML not supported — parsing will fail
- Network or payment failure — no result returned

## How this service works

Change audit: Hammerkit: Audit JSON changes and validate before/after for Hammerkit. 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 listing JSON pointer paths for all added, removed, and changed fields between the before and after documents, along with schema rule violations tied to specific paths, and a summary of which errors were introduced and which were resolved.

## 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-hammerkit-c5b875b3/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)