Check output contracts API

Compare caller-supplied success examples with their output schemas for type, enum, required fields, and extra properties. A mismatch is a conflict between those documents, not a confirmed live response.

The Check output contracts operation is part of the Agent Execution Contract Intelligence API on BRAINIAC.software. Compare caller-supplied success examples with their output schemas for type, enum, required fields, and extra properties. A mismatch is a conflict between those documents, not a confirmed live response. It is exposed as POST /api/v1/agent-contracts/output-contract-check and priced at $0.04 USDC on Base. Payment uses the x402 exact scheme: an unpaid call returns HTTP 402 with payment requirements; after paying the exact USDC amount, retry the same request with a payment-signature header and Idempotency-Key. No account and no API key are required. Data sources for this product: Caller-supplied OpenAPI documents, JSON Schema objects, operation definitions, and workflows processed locally Limitations: No URL is fetched and no language model reads the text. A missing sentence is undocumented. It is not a confirmed defect in a running server. The HTTP method is not evidence that a call is safe to retry or idempotent. An operation is not called idempotent unless the supplied contract says so. Outputs are compliance prechecks, drafts, or data lookups for human review. They are not official determinations, legal advice, identity confirmation, or certified filings. Related operations in this group include Check expiry contracts, Check retry safety contracts, Audit idempotency contracts, Check pagination contracts. Open the group documentation for the full request schema, field notes, and response examples before integrating.

POST$0.04 USDC
/api/v1/agent-contracts/output-contract-check

Example request

curl -i -X POST "https://www.brainiac.software/api/v1/agent-contracts/output-contract-check" \
  -H 'content-type: application/json' \
  -H 'Idempotency-Key: <fresh-64-character-random-hex-key>' \
  --data-binary @- <<'JSON'
{
  "operations": [
    {
      "name": "create_order",
      "outputSchema": {
        "type": "object",
        "required": [
          "id",
          "status"
        ],
        "additionalProperties": false,
        "properties": {
          "id": {
            "type": "string"
          },
          "status": {
            "type": "string",
            "enum": [
              "draft",
              "submitted"
            ]
          }
        }
      },
      "examples": [
        {
          "id": 15,
          "status": "shipped",
          "note": "rush"
        },
        {
          "id": "ord_1",
          "status": "draft"
        }
      ]
    }
  ]
}
JSON

An unpaid probe returns HTTP 402 with x402 payment requirements. After paying the exact USDC amount on Base, retry the identical request with a payment-signature header.

FAQ

  • Do I need an API key? No. Pay the listed USDC amount with x402.
  • What network? Base (eip155:8453), USDC.
  • Is this an official determination? No. Results are for human review against the cited sources.

Related APIs

Agent Execution Contract Intelligence APIFull docsHow it works