# Change Audit: Adobe UXP Manifest

> Change Audit: Adobe UXP Manifest 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).

Validates and audits JSON changes (before/after) for Adobe UXP Manifest files, reporting added/removed/changed paths and schema violations using a pinned SchemaStore definition.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-schema-adobe-uxp-manifest-defd5d21-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/change-audit-adobe-uxp-manifest-16f32be5
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_cKXLc9ksugVVWf_-IhCA5

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-adobe-uxp-manifest-16f32be5 -d '<json body>'
```

Example prompt: Can you audit the changes I made to my Adobe UXP plugin manifest? Here's the before JSON: {} and here's the after JSON: {"manifestVersion":5,"id":"com.example.plugin","name":"My Plugin","version":"1.0.0"} — tell me what paths changed and whether the new version has any schema violations.

## When to prefer this

Choose this endpoint when you specifically need to audit changes to an Adobe UXP plugin manifest JSON file and validate it against the official SchemaStore schema definition. It is purpose-built for UXP manifest change tracking, making it more targeted than a generic JSON diff or schema validator. Best for plugin developers working with Adobe UXP who want to catch schema regressions between manifest versions before submission or deployment.

## Known failure modes

- Document exceeds 100 KB limit — request rejected
- JSON nesting exceeds 32 levels — request rejected
- Invalid JSON provided (non-parseable) — parsing error returned
- YAML or TOML input not supported — must be valid JSON
- Network or payment failure — no result returned

## How this service works

Change audit: Adobe UXP Manifest: Audit JSON changes and validate before/after for Adobe UXP 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 report of JSON pointer differences between the before and after documents, including added, removed, and changed paths, plus schema rule violations present in each document, newly introduced errors, and resolved errors — all validated against the pinned Adobe UXP Manifest 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-adobe-uxp-manifest-16f32be5/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)