Validator directory

Start with the destination, not a generic checklist.

Each validator has a defined input, scope, and credit cost. It checks stated rules. It does not replace destination instructions, professional judgment, or a portal’s final validation.

01/ GRANTS

Funding submissions

1 credit

NIH Common Form / SciENcv

Technical and heuristic PDF preflight for SciENcv-generated NIH Common Forms. Choose Forms-I or NOFO-specific context in the workspace.

PDFForms-INOFO-specific

1 credit

NIH / NSF grant attachment

Agency-specific PDF attachment preflight. Select the NIH or NSF profile in the workspace.

PDFNIHNSF

02/ REGISTRY

ClinicalTrials.gov

3 credits, complex

Protocol record

Technical and content-presence preflight for protocol documents and structured records.

PDFXMLJSON

3 credits, complex

Results record

Technical and content-presence preflight for results documents and structured records.

PDFXMLJSON

03/ COURTS

CM/ECF PDF

1 credit

Federal court filing PDF

Conservative technical PDF preflight. Provide local court policy JSON only when you have current court and size-limit guidance.

PDFtechnical readinesscourt-specific JSON

04/ TECHNICAL

Portable files and packages

1 credit

Generic technical PDF

Checks PDF integrity and technical readability without representing a destination-specific profile.

PDFintegrity

3 credits, complex

Configurable ZIP package

Checks an archive and its declared manifest policy. Optional package policy must be a JSON object.

ZIPmanifestJSON policy

05/ PATENTS

USPTO Patent Center

1 credit

Patent Center upload

Patent Center file type, size, and PDF compatibility checks. Confirm current USPTO filing requirements independently.

PDFDOCXTXTZIP

Launch maximum: 50 MiB. A selected profile may enforce a lower limit. Validator availability and precise source versions are exposed by the running API. Use GET /api/v1/validators to fetch current machine-readable metadata.

06/ NEXT

Select and check

See the input contract before uploading.

Choose a validator in the workspace. It offers only the profile and optional policy fields the validator supports before a file is sent for checking.

Open validation workspace