Skip to content

Pipe Builder (/v1/build/*) — REMOVED

The five build routes are gone from this server: POST /v1/build/inputs, POST /v1/build/output, POST /v1/build/runner, POST /v1/build/concept and POST /v1/build/pipe-spec now answer 404. The runtime code that only these routes and their local twins used went after them: the concept and pipe specs, pipelex-agent concept, pipelex-agent pipe and pipelex build runner.

What replaces each one

  • An inputs template (/v1/build/inputs) is projected by the client from the input form that POST /v1/pipe-io returns, with the mthds packages' projection: renderInputsTemplate from mthds/protocol, which @pipelex/sdk re-exports, or mthds.protocol.inputs_template in Python. mthds-agent inputs does exactly that. pipelex build inputs still writes the engine's own rendering locally, the template the removed route returned, which differs from the client projection where the projection fixture corpus records.
  • A pipe's declared output (/v1/build/output) is described by the output_form and the pipe I/O contract that POST /v1/pipe-io returns. The rendered output example has no HTTP replacement; pipelex build output renders it locally.
  • The typed structures a runner script imported (/v1/build/runner) are the python-structures target of POST /v1/codegen. The runner script itself has no replacement: Build Runner says how to write one.
  • The concept and pipe spec conversions (/v1/build/concept, /v1/build/pipe-spec) have no replacement: a method is written as MTHDS directly and checked with POST /v1/validate.