# DDG Agent-Payable MCP Conformance Endpoint

> DDG Agent-Payable MCP Conformance Endpoint 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-12).

Accepts machine-payable HTTP requests from AI agents and validates or processes them against MCP conformance rules via the x402 payment rail

## Facts

- Endpoint: POST https://agents.daedalusdevelopmentgroup.com/v1/mcp/conformance?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/ddg-agent-payable-mcp-conformance-endpoint-b496f578
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_J5v42RaTL_7PrQ35vXp58

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-agent-payable-mcp-conformance-endpoint-b496f578 -d '<json body>'
```

Example prompt: Submit a JSON POST body to the DDG conformance endpoint — the input type is 'http', method is 'POST', body type is 'json', and the body is my agent request payload — and pay the $0.01 USDC fee via x402.

## When to prefer this

Choose this endpoint when your AI agent needs to validate or submit requests against the Daedalus Development Group MCP conformance spec using the x402 micropayment rail at $0.01 USDC per call. Prefer this over generic HTTP validators when you specifically need DDG MCP protocol conformance checking with built-in machine-payable billing.

## Known failure modes

- Missing required fields (input or output) returns a validation error
- Invalid HTTP method enum value causes rejection
- Payment failure via x402 results in 402 Payment Required with no processing
- Malformed JSON body type mismatch causes body parsing error
- Non-conforming output schema triggers conformance failure response

## How this service works

DDG agent-payable service request

## Output

Returns a JSON object indicating whether the conformance check succeeded (ok: true) along with an output type descriptor and example response. On success the agent receives confirmation that the request body met MCP conformance requirements.

## 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-agent-payable-mcp-conformance-endpoint-b496f578/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)