# Change Audit: .nodehawkrc

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

Validates and audits JSON changes between before/after versions of a .nodehawkrc configuration file, reporting added/removed/changed paths and introduced/resolved schema errors.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-schema-nodehawkrc-f0f26002-changes?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/change-audit-nodehawkrc-4a5f94f7
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_7WnXJw2j6r1WHOSYu_JCx

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-nodehawkrc-4a5f94f7 -d '<json body>'
```

Example prompt: Can you audit the changes I made to my .nodehawkrc — here's the before and after JSON — and tell me which paths changed and whether I introduced any new schema violations?

## When to prefer this

Use this endpoint when you need precise, schema-backed diffing of .nodehawkrc configuration files specifically, with violation tracking tied to SchemaStore rules. Prefer it over generic JSON diff tools when you need to know not just what changed but whether those changes introduced or resolved schema errors in the nodehawk configuration context.

## Known failure modes

- Document exceeds 100 KB limit — request rejected
- Nesting depth exceeds 32 levels — parsing refused
- Input is not valid JSON (YAML/TOML not supported) — parse error returned
- Missing 'after' field — validation cannot proceed
- Network or payment failure — no result returned

## How this service works

Change audit: .nodehawkrc: Audit JSON changes and validate before/after for .nodehawkrc. 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 pointers for all added, removed, and changed paths between the before and after .nodehawkrc documents, along with any schema rule violations introduced or resolved, based on a pinned SchemaStore definition.

## 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-nodehawkrc-4a5f94f7/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)