PAID APIS · DOCUMENTED JSON · CUSTOMER-AUTHORIZED CHARGES
Validate inbound records before they break downstream workflows
Use deterministic validators between ingestion and storage. Check input JSON against supported contract rules, screen batches for invalid or duplicate records, and find exact field changes before an automated downstream action.
What you can automate
- Gate a scheduled ETL import before writing invalid customer records.
- Verify LLM-generated JSON against an explicit supported schema subset.
- Inspect schema changes during deployment and identify affected keys.
Exact current charges and integration
USDC per-request billing and PayPal prepaid credits are separate payment methods. The catalog is calculated by the production server; quotes are checked before execution. No recurring subscription is selected automatically.
- data-quality-gate: $0.02 via x402 or 2 prepaid credits per call — Input, sample and integration.
- json-contract-check: $0.005 via x402 or 1 prepaid credit per call — Input, sample and integration.
- json-change-set: $0.005 via x402 or 1 prepaid credit per call — Input, sample and integration.
- schema-drift-guard: $0.03 via x402 or 3 prepaid credits per call — Input, sample and integration.
- record-dedupe: $0.003 via x402 or 1 prepaid credit per call — Input, sample and integration.
Integration request examples
Example: json-contract-check
{
"schema": {
"type": "object",
"required": [
"id"
],
"properties": {
"id": {
"type": "string"
}
}
},
"value": {
"id": "row-1"
}
}This is an illustrative request payload, not a live result or a free execution.
Full OpenAPI schema · Idempotent prepaid client and key security · Live catalog
Limitations
- JSON Contract Check supports a documented subset of JSON Schema, not all keywords.
- Data Quality Gate accepts bounded batches of up to 200 records.
- This is validation, not a guarantee that source data is factually correct.
Common integration questions
Can a scheduled application pay per result?
Yes, with an approved payment method and the documented per-call credits or x402 pricing. No schedule or payment is auto-enabled.
Is the API key embedded in templates?
No. Store credentials privately in your workflow tool and use an Idempotency-Key for safe retries.
Try before you integrate
Published input samples, current product prices and system health are publicly accessible. Executing your own data requires an authorized payment; we do not publish paid results as free samples.
Verified operational and payment status · Scheduled workflow templates