Skip to main content

Core Exports

AgentInput.request

When an agent is invoked via the direct HTTP Agent API, the platform auto-injects the raw HTTP request context on input.request: method, sub-path, path segments, body, headers, query and cookies. Use it to read custom headers or query params, or to expose several endpoints from one agent (see HTTP Routing). Header names arrive in canonical form, and header and query values are arrays:
input.request is not populated for webhook-triggered invocations (the payload lives in metadata instead), scheduled jobs, or direct SDK calls. Always guard access with optional chaining. See Core Types → AgentInput for the full field list.

Next Steps

Tools & Connectors

View tools exports

Workflows

View workflow exports