ARD Catalog Validator
Pricing
$0.01 / catalog validation
ARD Catalog Validator
Validate an inline or public HTTPS ARD catalog and return stable repair-grade JSON diagnostics for coding agents.
Pricing
$0.01 / catalog validation
Rating
0.0
(0)
Developer
VinceSoft
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
25 days ago
Last modified
Categories
Share
What does ARD Catalog Validator do?
ARD Catalog Validator determines whether an Agentic Resource Discovery catalog conforms and returns exactly what a coding agent must fix. Supply either a raw JSON object for fully offline validation or a public HTTPS URL. The Actor returns stable rule codes, JSON Pointer paths, expected and actual values, severities, and deterministic repair suggestions through Apify API, schedules, integrations, or hosted MCP tooling.
It uses the same pinned schema and semantic engine as ARD Catalog Resolver, with no LLM, browser, paid API, or automatic mutation of your document.
Why use ARD Catalog Validator?
The official ARD project provides a free conformance CLI. This paid primitive is for workflows that need an independently deployable Apify/MCP contract, one versioned JSON result, stable diagnostics rather than Ajv-specific prose, remote URL safety, and parity with the Resolver’s production interpretation. Typical agent queries include “Is this ARD catalog valid?”, “Why does this ai-catalog.json fail?”, and “Return machine-readable repairs for this ARD manifest.”
How to use ARD Catalog Validator
- Open the Input tab.
- Paste a
catalogJSON object or provide one public HTTPSurl, never both. - Select strict mode for conformance or permissive mode while investigating extensions.
- Run and consume the single dataset envelope.
Input
{"catalog": {"specVersion": "1.0","entries": []},"validationMode": "strict"}
Raw input causes no network request. Strict mode rejects fields that the pinned upstream schema forbids. Permissive mode demotes only those additionalProperties failures to warnings; entry extension fields that the ARD schema explicitly permits remain valid in both modes. An unsupported catalog version remains invalid.
Output
{"contractVersion": "1.0","ok": true,"valid": false,"ardSpecVersion": "0.9","catalogSpecVersion": "1.0","schemaRevision": "5fa2f5aef790b478319f6a3b43adf4661b0ed0e0","errorCount": 1,"errors": [{"code": "INVALID_IDENTIFIER","path": "/entries/0/identifier","severity": "error","suggestion": "Use a valid ARD identifier beginning with urn:air:."}]}
You can download the dataset in formats such as JSON, HTML, CSV, or Excel; JSON is recommended for repair automation.
Data table
| Field | Meaning |
|---|---|
valid | Conformance in the selected mode. |
ardSpecVersion | Pinned ARD prose draft version. |
catalogSpecVersion | Manifest version declared by the input. |
schemaRevision | Exact upstream Git revision. |
errors | Repair-grade blocking issues. |
validationWarnings | Non-blocking issues. |
Pricing / Cost estimation
The provisional price is $0.01 for one catalog-validation event. Valid and invalid completed determinations are billable. Input rejection and URL network/resource/internal failures are free. Check the live Actor details for current pricing.
Tips and limits
Prefer inline input in CI and code-generation workflows: it is faster, deterministic, and removes network uncertainty. The Actor never emits a patched catalog, so downstream automation must apply and review its own changes. Remote URL responses are limited to public HTTPS, bounded redirects, and 1 MiB decoded content. DNS is resolved and pinned per request, private/local/link-local targets are blocked again after redirects, and URL query values are redacted from result provenance and logs.
Invalid JSON and schema-invalid catalogs are completed validation determinations (ok: true, valid: false). Invalid Actor input and URL retrieval failures return ok: false with a stable machine error and are not charged.
FAQ, disclaimers, and support
The supported baseline is ARD draft 0.9 and catalog manifest 1.0 at schema revision 5fa2f5aef790b478319f6a3b43adf4661b0ed0e0. This is not a replacement for reviewing the official specification or free conformance tooling. Use the Actor’s Issues tab for a diagnostic that differs from the pinned upstream behavior, including a minimal anonymized catalog.