Add a content source

A task needs data to run over. In Speedtrain that data lives in an index — a collection of documents ingested from an external system.

Create an index

Open Content sources

Go to Content sources. The Indices tab lists the indexes in the current environment; Stage outputs lists content generated by tasks.

Add an index

Click Add index and give it a name and an alias. The alias is the stable handle you use when pushing documents and when referencing the index elsewhere.

Push your documents

Send your records to the index through the ingestion API using a management client key. Management clients

Document shape

A document is a JSON object. Speedtrain reads whatever fields you send, so the shape is yours to decide — use the field names your source system already uses rather than inventing new ones.

{
  "id": "SKU-40128",
  "title": "Merino base layer",
  "category": "Base layers",
  "material": "100% merino wool",
  "weight_gsm": 180,
  "colour": "Charcoal"
}

Send the raw attributes, not a pre-written summary. The model does better work from structured fields than from prose someone else already condensed.

Images

If you want a vision model to see the product photos, add a top-level $images array:

{
  "id": "SKU-40128",
  "title": "Merino base layer",
  "$images": [
    { "url": "https://cdn.example.com/40128-front.jpg", "text": "Front view, charcoal" },
    { "url": "https://cdn.example.com/40128-detail.jpg" }
  ]
}

Field	Rules
`url`	Required. Absolute `http(s)` and publicly fetchable — the model provider fetches it directly, so private or authenticated CDNs will not work.
`text`	Optional caption. It reaches the model as information about the image, never as an instruction.

$images must be at the top level and spelled exactly that way. A nested or differently-cased key is treated as ordinary data and ignored. A malformed $images array rejects the whole document at ingest, naming the offending element.

An empty $images: [] is valid — “this document has no pictures” is a legitimate fact, and what happens next is decided by the task configuration. Capabilities

Using another task’s output instead

An index is not the only possible input. A task can also run over the accepted output of another task, which is how you chain jobs. You choose between the two when you start a session, not when you build the configuration. Content sources

Overview

Authoring guide

Settings

MCP server

Create an index

Document shape

Images

Using another task’s output instead

​Create an index

​Document shape

​Images

​Using another task’s output instead

Create an index

Document shape

Images

Using another task’s output instead