Service details
Response Check
Check a response against your schema, timestamp age and selected claim evidence before using it. Your assistant calls the service and brings the result back into your task.
Check a supplied response against a declared schema, freshness rule and optional supplied evidence
0.05 USDC per completed diagnostic
Paid only. No free trial for this operation.
This operation needs paid setup. New to Mekler? Start with a free sample task →
Know its boundaries.
- Independent fact verification, source authenticity, unspecified claims, arbitrary JSON Schema keywords or references, regex patterns, URL retrieval, or guaranteed hallucination detection.
- Arbitrary-precision fractional JSON numbers that fail the declared lossless serialization profile.
Data handling
Response, schema, supplied evidence and payment proofs are excluded from telemetry. Optional semantic assessment sends only selected claims and evidence to AWS Bedrock in us-east-1. No URLs are fetched. Completed results stay encrypted for 30-day original-proof recovery; payment retention follows the published payment policy.
Input example and exact contract
{
"request_id": "response-check-example-001",
"response": {
"value": 12,
"updated_at": "2026-10-21T12:00:00Z"
},
"schema": {
"type": "object",
"required": [
"value",
"updated_at"
],
"properties": {
"value": {
"type": "integer",
"minimum": 0
},
"updated_at": {
"type": "string",
"format": "date-time"
}
},
"additionalProperties": false
},
"freshness": {
"pointer": "/updated_at",
"reference_time": "2026-10-21T12:01:00Z",
"max_age_seconds": 300
}
}Example output
{
"status": "ok",
"verdict": "pass",
"schema": {
"status": "pass",
"errors": [],
"error_limit_reached": false,
"draft": "2020-12",
"format_assertions": [
"date-time",
"ipv4",
"ipv6",
"uuid"
]
},
"freshness": {
"status": "pass",
"pointer": "/updated_at",
"reason": "within_declared_age",
"age_seconds": 60.0
},
"semantic": {
"status": "not_requested",
"claims": [],
"method": null
},
"observed_at": "2026-10-21T12:01:00Z",
"limitations": [
"Only the requested contract is checked; pass is not proof of truth, source authenticity or suitability for a consequential decision.",
"Freshness uses caller-supplied timestamps and reference time; a recent timestamp does not authenticate recent source data.",
"Semantic assessment is advisory, uses supplied evidence only and can be wrong. Only caller-selected claims are assessed; other content remains unchecked.",
"No URLs are fetched, instructions executed or external facts independently verified."
]
}Calling, result interpretation and recovery
Calling
- Endpoint
POST /v1/data/responses/check-response-contract
- Content type
application/json
- Input
Send request_id and response, plus at least one check. Exact bounds and optional check semantics are in requestBody.
Interpret the result
- Status
ok means a completed charged diagnostic, including fail or review. It does not mean the response is true.
- Result
Inspect each check and every limitation. Evidence spans are verbatim but model entailment can be wrong.
- Recovery
Resend identical JSON and original proof after pending, timeout or expiry; do not buy again. A semantic supplier attempt is durably reserved once per payment authorization. Retries reuse a saved encrypted result or hold an uncertain/failed attempt without another model call. A held uncharged attempt needs a new explicitly authorized request_id to start again; never automatically pay again.
Limits
- Request bytes
20000
- Semantics
No work occurs on unsigned quotes. Complete normalized input is bound before payment.
Completed pass/fail/review diagnostics are charged; supplier/storage failures are uncharged.
Exact encrypted results recover for 30 days using the original body and proof.
Omitted checks are not_requested; pass applies only to requested checks, and semantic assessment can be wrong.
Semantic generation is attempted at most once per authorization; uncertain supplier attempts remain held and uncharged. Ready semantic results are encrypted before settlement and reused across retries.
Reject unsupported numeric precision before payment; integral values are exact up to 1000 digits. Nonintegral values must round-trip through finite binary64 decimal serialization. No arbitrary-precision fractional arithmetic is promised.
Payment and recovery
- Price
0.05 native USDC per completed operation
- Network
Solana mainnet or Base mainnet
- Protocol
x402 v2 exact
- Quote
POST the intended JSON unsigned for one input-bound 402; no work/source retrieval occurs. Sign one offer and resend identical JSON. Work and encrypted storage complete before settlement.
- Authorization
Choose one accepts entry with a standard x402 v2 client. Check native USDC, network, recipient, amount and intended input before signing. Solana uses an SVM transaction; Base uses an EOA EIP-3009 authorization (USD Coin version 2). Send the proof with identical JSON input. No API key, token approval, bridge or Solana wallet is needed for Base. Never automatically fall back to another network.
- Retry
Preserve identical JSON and original proof for 30 day result recovery; do not buy again after a timeout or pending result. Fresh request_id creates a new paid operation. A semantic supplier attempt is durably reserved once per payment authorization. Retries reuse a saved encrypted result or hold an uncertain/failed attempt without another model call. A held uncharged attempt needs a new explicitly authorized request_id to start again; never automatically pay again.
- Finality
A 202 is pending. Finalized delivery carries PAYMENT-RESPONSE; provisional delivery is separately labeled and does not establish finality. Preserve the original proof instead of buying again.
- Expiry
Ongoing service under recurring monthly authority. Budget warnings do not stop service. Short-lived quotes and recovery retention still expire.
- Networks
solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdp
eip155:8453
- Assets
- Solana:5eykt4usfv8p8njdtrepy1vzqkqzkvdp
EPjFWdd5AufqSSqeM2qN1xzybapC8G4wEGGkZwyTDt1v
- Eip155:8453
0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913
- Fees
CDP sponsors the payment transaction gas on both networks. The service price is the same on either network; wallet funding or exchange fees are separate.
- Request binding
The server authenticates the complete quote and input and atomically binds the first accepted authorization to them. Standard Base EIP-3009 signs the money terms and nonce, not HTTP content. Keep signatures private; do not reuse an authorization for another quote, operation or body.