Expose a custom HighByte pipeline as a REST endpoint via an API Trigger and discover its expected parameters programmatically
domain: support.highbyte.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Add an API Trigger to a Pipeline in HighByte Intelligence Hub to expose it as a custom REST Data API endpoint
Define expected parameters on the trigger, optionally with default values, to control what the request body must contain
Call GET /data/v1/pipelines/params to discover parameters across all exposed pipelines, or GET /data/v1/pipelines/{pipelineName}/params for a single pipeline
Invoke the custom endpoint with a JSON body matching the discovered parameter schema
If the pipeline is also exposed on the MCP Server, verify an AI agent can use the same parameter discovery endpoints to build valid calls
Known gotchas
If a parameter has no default value it is required in the request body and the call will error if omitted; if a default is defined, a missing value is silently substituted
When parameters are defined at all, any additional properties in the request body beyond those parameters are ignored rather than rejected — don't assume validation catches typos
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?