# Change Audit for Gitea Issue Template Forms

> Change Audit for Gitea Issue Template Forms 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 before/after versions of Gitea Issue Template form documents, reporting added/removed/changed paths and introduced/resolved schema validation errors.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-schema-gitea-issue-template-forms-237d607f-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-for-gitea-issue-template-forms-aa28e783
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_X4UCJtLI7eoxdbWbakohs

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-for-gitea-issue-template-forms-aa28e783 -d '<json body>'
```

Example prompt: Can you audit the changes I made to my Gitea issue template form — here's the before JSON and the after JSON — and tell me which paths changed and whether any new schema validation errors were introduced or old ones resolved?

## When to prefer this

Use this endpoint when you specifically need to audit changes to Gitea Issue Template form JSON documents against the SchemaStore definition, especially when you want to understand what paths changed and whether edits introduced or resolved schema violations. It is purpose-built for Gitea Issue Template forms and uses a pinned local schema definition, making it more precise than a generic JSON diff or schema validator for this file type.

## Known failure modes

- Document exceeds 100 KB limit — request rejected
- JSON nesting depth exceeds 32 levels — request rejected
- Malformed JSON in before or after field — parse error returned
- YAML or TOML input provided instead of JSON — not supported, error returned
- Network or payment failure — no audit result returned

## How this service works

Change audit: Gitea Issue Template forms: Audit JSON changes and validate before/after for Gitea Issue Template forms. 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-level differences between the before and after documents, including added, removed, and changed paths, as well as any validation rule violations introduced or resolved relative to the pinned SchemaStore definition for Gitea Issue Template forms.

## 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-for-gitea-issue-template-forms-aa28e783/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)