Waterfalls
Waterfall builder catalog
Every capability with its inputs, normalized output fields, and the endpoints a waterfall can use: price, quality, fill, p50 and rate limits.
Authorization
bearer AuthorizationBearer <token>
In: header
Response Body
application/json
application/json
curl -X GET "https://example.com/v1/waterfalls/catalog"{ "items": [ { "id": "string", "name": "string", "category": "string", "summary": "string", "inputs": [ { "name": "string", "description": "string", "required": true } ], "outputs": [ "string" ], "endpoints": [ { "id": "string", "provider": "string", "provider_name": "string", "name": "string", "mode": "string", "pricing_model": "string", "quote_micro": 0, "sandbox": true, "verified": true, "supported": true, "p50_ms": 0, "fill": 0, "score": 0, "samples": 0, "rps": 0, "burst": 0 } ] } ]}Cancel a waterfall run POST
Stop a queued or running run. In-flight attempts are aborted and released; the partial result is kept.
Create a waterfall from a template POST
Copy a template into your workspace in one call, optionally pinning vendors per stage, overriding speed or capping cost, and publish it (default) so waterfall_run works right away. Returns the waterfall (id, name, endpoint). Templates with status needs_integration are rejected with validation_failed. Next: waterfall_run with {id, input}.