# DDG JSON Validate

> DDG JSON Validate is a paid API for AI agents from agents.daedalusdevelopmentgroup.com, paid per call via x402, $0.01/call, status unknown (last checked 2026-10-17).

Validates that an HTTP request body conforms to an expected JSON schema or output format, returning a pass/fail result

## Facts

- Endpoint: POST https://agents.daedalusdevelopmentgroup.com/v1/json-validate?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-17
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/ddg-json-validate-0498d181
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_zL4RNzoeJybSy6v0OMz_j

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 ddg-json-validate-0498d181 -d '<json body>'
```

Example prompt: Can you validate this JSON body I'm about to POST — it's an object with fields 'name' and 'age' — and confirm it matches the expected output format where ok should be true?

## When to prefer this

Choose this endpoint when you need a lightweight, pay-per-call JSON/HTTP body validation service with no account setup, billed fractionally via x402 USDC micropayments. Ideal for AI agent pipelines that need to validate request payloads on-the-fly before forwarding them to downstream APIs, especially when you want a bounded, stateless validation artifact rather than raw provider account access.

## Known failure modes

- Malformed or non-JSON body returns validation failure
- Missing required fields (input, output) causes a 400-level error
- Incorrect method enum value (not POST/PUT/PATCH) causes rejection
- Payment not settled via x402 results in 402 Payment Required response
- Body type mismatch (e.g. sending form-data declared as JSON) may cause parse failure

## How this service works

DDG agent-payable service request

## Output

Returns a JSON object with an 'ok' boolean field indicating whether the submitted HTTP request body is valid and conforms to the expected output schema. A result of {ok: true} means the payload passed validation.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input",
  "output"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "method",
    "bodyType",
    "body"
   ],
   "properties": {
    "body": {
     "type": "object"
    },
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "POST",
      "PUT",
      "PATCH"
     ],
     "type": "string"
    },
    "bodyType": {
     "enum": [
      "json",
      "form-data",
      "text"
     ],
     "type": "string"
    }
   },
   "additionalProperties": true
  },
  "output": {
   "type": "object",
   "required": [
    "type",
    "example"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "ok": true
    }
   },
   "additionalProperties": true
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "ok": true
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/ddg-json-validate-0498d181/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from agents.daedalusdevelopmentgroup.com](https://www.zero.xyz/host/agents.daedalusdevelopmentgroup.com/llms.txt)