What problem does it solve?
It removes guesswork when wiring HTTP endpoints to agent method signatures by clearly defining how URL parts, headers, and JSON bodies become strongly-typed TypeScript parameters and responses.
Core Features & Use Cases
- Path variable mapping: Maps
{varName} segments in mount and endpoint paths into constructor and method parameters, including last-segment catch-all behavior.
- Query and header mapping: Supports
?key={var} syntax for query parameters and headers: { ... } for header-to-parameter binding, including optional (T | undefined) and repeated (Array<T>) forms for query/header only.
- Body and return type mapping: Defines how unmapped parameters become a JSON request-object body and how
void, undefined, Result, UnstructuredBinary, and UnstructuredText map to HTTP status codes and response content types.
- Type safety rules: Restricts which TypeScript types are allowed for path/query/header parameters versus body parameters, preventing invalid runtime parsing.
Quick Start
Ask for the correct parameter and return type mapping rules for a specific HTTP endpoint in your TypeScript agent, including how to bind path variables, query params, headers, and request bodies.