Nested JSON Contract Check
Pricing
from $20.00 / 1,000 completed validation reports
Nested JSON Contract Check
Validate up to 1,000 JSON records against a finite nested typed contract. Get strict structural checks and precise field paths before the next workflow step. Not full JSON Schema, factual verification, coercion or repair. $0.02 per completed report plus the listed Actor start fee.
Pricing
from $20.00 / 1,000 completed validation reports
Rating
0.0
(0)
Developer
Godmind
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
8 days ago
Last modified
Categories
Security
Limited permissionsShare
Check a batch of JSON records against a small, explicit typed contract. Useful for an agent checking structured output before passing it to another step.
This is a finite contract checker, not a complete JSON Schema validator. It does not repair records or convert types. No LLM or external lookup is used by the validation engine.
Input
Supply the complete request as a string in request_json. Keeping the JSON as text allows duplicate object keys and non-finite number literals to be refused.
The example produces FAIL with a TYPE_MISMATCH at /id in record 1 (zero-based). It is a fictional example.
Contract profile
Each contract node must name one type: object, array, string, integer, number, boolean or null. The supported keywords are type, properties, required, additionalProperties and items. No enum, bounds, patterns, references, unions or custom code. Unsupported syntax is refused.
Limits: 1 MiB request text; 1000 records; 2000 contract nodes; 50000 total record nodes; depth 20. At most 50 issue details are returned, with exact issue totals and a truncation indicator.
Output
The report is available as one item in the run's default dataset and through the OUTPUT key. PASS means all supplied records conform. FAIL is a completed check with violations. INVALID_REQUEST means the request was refused, not that the records failed validation. Issues use zero-based record indexes, JSON Pointer paths and codes.
The billing output links to BILLING. Engine completed_report_event metadata is synthetic; it is not a payment receipt. The adapter persists the report before a completion-charge attempt. Ambiguous charge outcomes are marked UNKNOWN_NEEDS_RECONCILIATION and are not blindly retried.
Pricing and availability
A completed PASS or FAIL validation report costs USD0.02 for up to 1000 records. The separately listed Actor start fee also applies; its event count depends on allocated memory (minimum one event). Platform usage is included in the listed pricing. No automatic per-record fee is configured. An INVALID_REQUEST has no completed-report event, but may still incur the Actor start fee. Use the platform run-charge limit to control your maximum charge.
The package passed local SDK/container checks and one private hosted synthetic sample. Paid collection, paid-run idempotency, customer results, payout and high-volume economics have not been demonstrated. This is a finite-profile structural checker, not a complete JSON Schema validator or factual verifier.
Data handling
Do not submit credentials or sensitive personal data. The engine does not put record values in issue diagnostics, but the hosting platform receives your request and may retain run input and storage under its own policies. This tool does not establish correctness of the real-world facts in your records.
