# Change Audit: Amazon S3 Bucket CORS

> Change Audit: Amazon S3 Bucket CORS 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-22).

Audits JSON changes between before/after documents for Amazon S3 bucket CORS configuration, reporting added/removed/changed paths and schema validation violations.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-schema-amazon-s3-bucket-cors-f9c204bc-changes?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-22
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/change-audit-amazon-s3-bucket-cors-6577dd62
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_uO_zHAs2w4mvMGrgU2oHl

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-amazon-s3-bucket-cors-6577dd62 -d '<json body>'
```

Example prompt: Can you audit the changes I made to my Amazon S3 bucket CORS configuration? Here's the before JSON and the after JSON — tell me what paths changed, what was added or removed, and whether any schema violations were introduced or resolved.

## When to prefer this

Choose this endpoint when you specifically need to audit JSON configuration changes for Amazon S3 bucket CORS settings and want schema-validated diff reporting using a pinned SchemaStore definition. Best suited for structured change tracking in CI/CD workflows, compliance audits, or manual review of CORS config edits, where you need precise JSON pointer-level reporting of what changed and whether violations were introduced or resolved.

## Known failure modes

- Document exceeds 100 KB limit — request rejected
- JSON nesting exceeds 32 levels — parsing fails
- Invalid JSON submitted (non-parseable) — error returned
- YAML or TOML format submitted — not supported, error returned
- Payment not included or insufficient — x402 payment required error

## How this service works

Change audit: Amazon S3 bucket CORS: Audit JSON changes and validate before/after for Amazon S3 bucket CORS. 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 including JSON pointers for all added, removed, and changed paths between the before and after documents, along with any schema rule violations that were introduced or resolved, validated against a pinned SchemaStore definition for Amazon S3 bucket CORS.

## 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-amazon-s3-bucket-cors-6577dd62/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)