# Change Audit: Pulumi

> Change Audit: Pulumi 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 Pulumi JSON documents (before/after), reporting added/removed/changed paths and any schema rule violations using a pinned SchemaStore definition.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-schema-pulumi-96824235-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-pulumi-eb2783f3
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_UCzi0ZHPkLRo18_7sd6G3

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-pulumi-eb2783f3 -d '<json body>'
```

Example prompt: Can you audit the changes between my old and new Pulumi JSON configs — compare the before and after documents and tell me which paths were added, removed, or changed, and whether any new schema violations were introduced or old ones resolved?

## When to prefer this

Choose this endpoint when you specifically need to diff and validate Pulumi JSON configuration files against a pinned SchemaStore definition, particularly when you want to understand which schema rules changed state (introduced vs. resolved) between two versions. It is preferable over generic JSON diff tools because it combines structural diffing with Pulumi-specific schema validation in a single call. Not suitable for YAML/TOML Pulumi files or documents over 100 KB.

## Known failure modes

- Document exceeds 100 KB limit — request rejected
- JSON nesting depth exceeds 32 levels — request rejected
- Non-JSON input (YAML, TOML) passed — not parsed, may error
- Malformed JSON in before or after field — parse error
- Empty or missing both documents — may return no diff results

## How this service works

Change audit: Pulumi: Audit JSON changes and validate before/after for Pulumi. 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 containing JSON pointer paths for all added, removed, and changed properties between the before and after documents, along with any schema rule violations flagged by the pinned SchemaStore definition for Pulumi, including which errors were newly 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-pulumi-eb2783f3/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)