API Routes
Brix uses one typed contract for server handlers, imperative clients, component hooks, caching, retries, and failures. Choose the workflow that owns the code you are changing.
Define and implement an endpoint
#Call an endpoint
#Return a custom HTTP response
#Use a response contract and route for redirects, downloads, streams, or application-owned request processing. Schema-owned JSON or flat URL-encoded input with JSON output uses API contracts. Response routes share managed registration and typed URL generation, not the API client or response-validation contract.