Skip to main content
AgentPass offers an easy way to map and build properly formatted HTTP requests.
Request transformation flow from AI parameters to HTTP request

​
What an HTTP Request Includes

​
Method

Specifies the action (such as GET, POST, PUT, DELETE) the client wants to perform.

​
URL

The full URL of the request, including the protocol, domain, and path.

​
Path Parameters

Path parameters are embedded directly into the URL path.

​
Query Parameters

Query parameters are added to the URL query string with proper encoding and array handling.

​
Header Parameters

Header parameters are added to the HTTP request headers.

​
Body Parameters

Body parameters form the request payload with automatic content type detection.

​
Using Variables

In certain cases, you need to use tool or authorization parameters that should not be hardcoded in the HTTP request. AgentPass uses Handlebars templating for dynamic variable replacement. Variables are replaced with the actual parameter values when the request is made. In order to use variables, you need to use the following patterns: Query and Path Parameters
  • {{toolParams.parameterName}}
Body Parameters
  • {{toolParams.parameterName.propertyName}}
Header Parameters
  • {{headers.authorization}} : Full Authorization header (e.g., “Bearer token123”)
  • {{headers.originalToken}} : JWT token without “Bearer” prefix
  • {{headers.contentType}} : Request Content-Type header
  • {{headers.xApiKey}} : Custom header x-api-key → xApiKey
JWT Claims
  • {{auth.jwt.sub}} : JWT subject (user ID)
  • {{auth.jwt.scope}} : JWT scope claim
  • {{auth.customClaim}} : Any JWT claim property
⌘I