Digital Vending Machine

Ship valid JSON.Pay for a signed decision.

Built for AI application engineers and automation teams, Schema Gate verifies model-generated JSON before it triggers a tool, updates a record, or enters another production workflow. Accepted output is canonicalized and delivered with a signed receipt. No signup, API key, or subscription is required. The SDK is free; each completed ACCEPT or REJECT decision costs 0.010 USDC.

Try one real paymentOpen advanced console
Public Python clientBring Python 3.10+ and a local Solana-mainnet keypair holding at least 0.010 USDC. Your wallet key stays local; the SDK verifies the exact terms before signing.
Inspect the live contractService health · OpenAPI specification. Malformed requests do not settle.
Published receipt keyVerify every ES256 delivery receipt. Exact retry and token recovery do not create a second charge.
01

A gate between AI output and production.

Send JSON, a target schema, and the checks that protect your workflow. Schema Gate verifies the contract, canonicalizes accepted output, and returns a signed ACCEPT or REJECT decision before another system acts.

Buyer contractInput + rules
{
  "order_id": "order_8472",
  "input": { "customer": "Ada", "items": 3 },
  "target_schema": { "required": ["customer", "items"] },
  "acceptance_criteria": {
    "canonical_json": true,
    "required_fields": ["/customer", "/items"],
    "forbidden_patterns": [],
    "max_output_bytes": 16384,
    "normalizer_version": "schema-gate-c14n-v1"
  }
}
passes
Accepted deliveryCanonical JSON + receipt
{
  "verdict": "ACCEPT",
  "output": { "customer": "Ada", "items": 3 },
  "receipt": {
    "order_id": "order_8472",
    "acceptance_commitment": "sha256:…",
    "signature": "signed-receipt…"
  }
}
02

Commit the rules before payment.

Your downstream system gets a result it can verify against the same contract the buyer approved.

  1. 1

    Name the order

    Use an order ID and idempotency key so the purchase can be recovered safely.

  2. 2

    Define the shape

    Send the source JSON and the schema the final result must satisfy.

  3. 3

    Commit the checks

    Lock the pass conditions into the payment request before authorizing it.

  4. 4

    Enforce the receipt

    Accept the result only when its signed receipt matches your committed contract.

03

A small contract with a strong guarantee.

The SDK is free to use. One POST carries the order identity, source JSON, target schema, and acceptance contract; each completed signed evaluation is billed as one task.

Schema Gate contract

Production
Method
POST
Endpoint
https://www.x402digitalvendingmachine.store/v1/schema-gate
Evaluation
0.010 USDC
Paid verdicts
ACCEPT + REJECT
SDK
Free to use
Retry / recovery
Free with exact identity
Production requestRequest committed x402 terms
curl -i -X POST https://www.x402digitalvendingmachine.store/v1/schema-gate \
  -H "Content-Type: application/json" \
  -d '{"order_id":"order_8472","idempotency_key":"gate_8472_v1","input":{"customer":"Ada","priority":"urgent","items":3},"target_schema":{"type":"object","required":["customer","priority","items"],"properties":{"customer":{"type":"string"},"priority":{"enum":["standard","urgent"]},"items":{"type":"integer","minimum":1}},"additionalProperties":false},"acceptance_criteria":{"canonical_json":true,"required_fields":["/customer","/priority","/items"],"forbidden_patterns":[],"max_output_bytes":16384,"normalizer_version":"schema-gate-c14n-v1"},"acceptance_commitment":"sha256:fd6eac5b641344bc8d236102863c4a7fac1c476b98f8b88da47324a92d119823"}'

Retry the identical request with the canonical PAYMENT-SIGNATURE payload returned by your wallet-enabled client.

Receipt enforcementFor the next workflow step
if delivery["verdict"] == "ACCEPT" and verify_receipt(delivery["receipt"]):
    continue_workflow(delivery["output"])
Static delivery previewInterface example only · not a live purchase or settlement
{
  "preview_only": true,
  "verdict": "ACCEPT",
  "output": {
    "customer": "Ada",
    "items": 3,
    "priority": "urgent"
  },
  "receipt": {
    "type": "schema-gate-receipt",
    "order_id": "order_8472",
    "acceptance_commitment": "sha256:fd6eac5…",
    "signature": "<ES256 compact JWS>"
  }
}
EXECUTION GATE · PRIVATE PARTNER PILOT

Target-side permit enforcement for registered partners.

A privately deployed receiver has completed qualification. For a registered partner-owned receiver, the target can fail closed on a fresh, issuer-specific, one-use permit for each covered action, alongside the target's ordinary authorization.

The working price hypothesis is 0.010 USDC per covered action. No real funded external partner pilot has run yet, so Execution Gate is not offered here as a publicly purchasable service and the hypothesis is not a live price.

Prospective partners can review the public Python SDK and integration guide, then open a private-pilot discussion. Registration, action scoping, and readiness review come before any funded pilot.

This pilot does not promise customers, revenue, profit, universal security, or non-bypassability. A partner remains responsible for its own target, authorization, and enforcement.

Review Python SDK and guideContact us about the pilot
04

Advanced purchase console.

This console is for buyers whose wallet-enabled x402 client already creates canonical payment payloads. It never connects to a wallet and never accepts a private key or seed phrase. New buyers should follow the one-payment SDK guide. No signup, API key, or subscription is required. Valid signed payments are automatically verified and settled without manual approval; invalid, expired, mismatched, or replayed authorizations are rejected. A completed signed ACCEPT or REJECT evaluation costs 0.010 USDC; malformed requests and exact retry or recovery calls are free.

61 characters
JSON Schema
Committed before payment
Your downstream workflow can require this same commitment in the signed delivery receipt.
Never paste a wallet address, private key, or seed phrase.
Schema Gate response
{
  "ready": true,
  "next": "Commit an acceptance contract and request live terms."
}
05

A result your workflow can enforce.

The receipt binds the delivered JSON to the order and acceptance contract, so the next system can decide with evidence instead of trust.

Acceptance commitment
The checks are fixed before authorization and echoed in the receipt.
Canonical result
Accepted output conforms to the supplied target schema.
Signed receipt
Downstream code can require receipt verification before continuing.
Durable recovery
The same order and idempotency key recover the accepted delivery without buying it twice.