CoreModelsGuides
LinkML
Let the pipeline read the model that is already right.
- LinkML to Postgres in One Call: A CoreModels QuickstartQuickstart · Ten minutes, one YAML file, one HTTP call. By the end of this you will have converted a LinkML schema into Postgres DDL through CoreModels, read the machine-readable ledger of everything the conversion could not carry exactly, and sent the same schema back out as LinkML unchanged.
- The LinkML HTTP Surface: Import, Export, Map, ReplayAPI · There are ten routes on the CoreModels transform API. Five of them matter if LinkML is your source or your target, and the first thing to settle is which one you actually want — because the difference between them is not the format, it is whether anything gets written and who decides what passes through.
- Give an Agent a LinkML Schema: `transform_schema` over MCPMCP · > Analyst: Here's our product catalog in LinkML. The warehouse team needs a Postgres table for it. What do we lose?
- Plans, Not Scripts: Repeatable LinkML Conversion PipelinesAutomation · A conversion you cannot reproduce is not a pipeline; it is a favor someone did once. The interesting question for automation is not "can this tool turn LinkML into Postgres DDL" — it is "will the run in six months, on a build agent, with a token nobody remembers issuing, produce the same bytes and tell me if it did not."
- Inside the LinkML Coder: Every Construct, Every LossDeep dive · Start with one line of YAML:
Start building
14-day free trial. Builder $49/mo after the trial. Cancel any time.