Get started

Describe a pipeline.
Get a Job that validates.

Every Job below is checked with the same validator the API runs on submit — the same rules, not an imitation of them. If the model wires something illegally, it is told why and fixes it before you see it.

Try

Usually a few seconds. The Job is validated and repaired if needed. Limited to 5 requests per minute.

You will get three things

  1. The Job JSON, ready to submit.
  2. What the validator said about it, including anything it rejected first.
  3. A curl command to run it.

What this does and does not guarantee

Structurally valid

The topology is checked properly: node and sink types exist, inputs resolve, fan-in and fan-out limits hold, the graph is acyclic, and every sink has a reachable source. A Job shown as validated will be accepted on submit.

Not a guarantee it does what you meant

Field values inside config are not covered by the validator, and neither is intent. Credentials are placeholders. Read the Job before you run it, and check the reference for the components it picked.