# Change Audit: AWS CDK cdk.json

> Change Audit: AWS CDK cdk.json 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-23).

Validates and audits JSON changes between a before and after snapshot of an AWS CDK cdk.json configuration file, reporting added/removed/changed paths and schema rule violations.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-schema-aws-cdk-cdk-json-813530f3-changes?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-23
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/change-audit-aws-cdk-cdk-json-2873b358
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Ye9dWKqPtPwSWUkJI-82B

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-aws-cdk-cdk-json-2873b358 -d '<json body>'
```

Example prompt: Can you audit my AWS CDK cdk.json change — here's the before version and the after version — and tell me which paths changed, whether any schema rule violations were introduced or resolved, and if there are any errors I should know about?

## When to prefer this

Use this endpoint when you specifically need schema-aware change auditing for AWS CDK cdk.json files, particularly when you want JSON pointer-level diff reporting combined with SchemaStore rule violation detection. Prefer this over generic JSON diff tools when CDK-specific schema validation matters, and over full CDK deployment tooling when you only need lightweight pre-flight configuration checks without deployment or security guarantees.

## Known failure modes

- Document exceeds 100 KB limit — request rejected
- JSON nesting deeper than 32 levels — validation may be incomplete
- Invalid JSON submitted (non-parseable) — error returned
- YAML or TOML input instead of JSON — not supported
- Network or payment authorization failure — no audit returned

## How this service works

Change audit: AWS CDK cdk.json: Audit JSON changes and validate before/after for AWS CDK cdk.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 pointers for all added, removed, and changed paths between the before and after documents, any schema rule violations introduced or resolved, and a summary of errors found — validated against a pinned SchemaStore definition for AWS CDK cdk.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/change-audit-aws-cdk-cdk-json-2873b358/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)