# Change Audit: GitHub Secret Scanning

> Change Audit: GitHub Secret Scanning 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-12).

Validates and diffs two JSON documents (before/after) against the GitHub Secret Scanning schema, reporting added/removed/changed paths and introduced/resolved validation errors.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-schema-github-secret-scanning-ee0b158b-changes?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-12
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/change-audit-github-secret-scanning-8b891909
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_xgTU6bagdLhaGNTuaxIq5

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-github-secret-scanning-8b891909 -d '<json body>'
```

Example prompt: I just updated my GitHub Secret Scanning config file — can you audit the before and after JSON to show me what changed and whether the new version has any schema violations?

## When to prefer this

Use this endpoint when you specifically need to validate and diff JSON configurations against the GitHub Secret Scanning schema. Prefer it over generic JSON diff tools when schema-aware validation and violation reporting against the SchemaStore definition is required, and when the payload fits within 100 KB.

## Known failure modes

- Document exceeds 100 KB limit — request rejected
- JSON nesting exceeds 32 levels — request rejected
- Invalid JSON submitted (YAML/TOML not supported) — parse error
- Schema definition unavailable or pinned version mismatch — validation may be incomplete
- Payment of 0.01 USDC not completed — endpoint returns 402

## How this service works

Change audit: GitHub Secret Scanning: Audit JSON changes and validate before/after for GitHub Secret Scanning. 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 detailing JSON pointer diffs (added, removed, changed paths) between the before and after documents, along with introduced and resolved schema validation errors according to the pinned GitHub Secret Scanning 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-github-secret-scanning-8b891909/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)