What problem does it solve?
When exposing Golem agents over HTTP, developers need to know exactly how path variables, query parameters, headers, and request bodies map to Rust method parameters, and which types are allowed in each position. This Skill provides the complete mapping rules so endpoints parse requests correctly the first time.
Core Features & Use Cases
- Request Element Mapping: Covers path variables (including catch-all segments), query parameters, header binding via the headers(...) block, and JSON body mapping for POST/PUT/DELETE endpoints.
- Type Support Reference: Documents which Rust types work for path/query/header parameters (String, integers, floats, bool, char, unit enums, plus Option and Vec for query/headers) and how return types map to HTTP status codes and bodies.
- Binary and Text Payloads: Explains UnstructuredBinary and UnstructuredText for raw payloads, including MIME type and language restrictions.
- Use Case: You are building a Rust agent with an endpoint like #[endpoint(get = "/search?q={query}&limit={max}")] and need to confirm that u64 is a valid query parameter type and that the POST body must always be a JSON object keyed by parameter names.
Quick Start
Ask how to map path variables, query parameters, headers, and a JSON body to the parameters of a Rust agent endpoint in Golem.