# Cloud Foundry Application Manifest JSON Change Audit

> Cloud Foundry Application Manifest 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-24).

Audits JSON changes between two Cloud Foundry Application Manifest documents, reporting added/removed/changed paths, rule violations, and introduced or resolved validation errors.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-schema-cloud-foundry-application--2b4169ff-changes?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-24
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/cloud-foundry-application-manifest-json-change-audit-8e2fb2ee
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_xmRhR4NPUa7sHp0TDaiCu

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 cloud-foundry-application-manifest-json-change-audit-8e2fb2ee -d '<json body>'
```

Example prompt: I just updated my Cloud Foundry Application Manifest JSON — can you audit the change and tell me what paths were added, removed, or changed, and whether any new schema violations were introduced or existing ones resolved?

## When to prefer this

Choose this endpoint when you need a precise, schema-aware diff of two Cloud Foundry Application Manifest JSON documents — especially when you want to know not just what changed structurally but whether the change introduced or resolved SchemaStore-validated rule violations. It is purpose-built for Cloud Foundry manifests and uses a pinned SchemaStore definition, making it more reliable for CF-specific validation than a generic JSON differ or schema validator.

## Known failure modes

- Document exceeds 100 KB size limit — request rejected
- Nesting depth exceeds 32 levels — parsing refused
- Non-JSON input (YAML or TOML) submitted — not parsed or converted
- Payment not included or insufficient — x402 payment required
- Malformed JSON in before or after fields — validation error returned

## How this service works

Change audit: Cloud Foundry Application Manifest: Audit JSON changes and validate before/after for Cloud Foundry Application Manifest. 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 with JSON pointers identifying added, removed, and changed paths between the two manifest documents, along with any schema rule violations present in each version, highlighting errors that were introduced or resolved by the change. Limited to documents up to 100 KB each and 32 nesting levels.

## 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/cloud-foundry-application-manifest-json-change-audit-8e2fb2ee/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)