Guides

Header Cheat Sheet

A helpful reference for all of the custom headers that Pay-i supports.

Headers which accept multiple objects require a comma separated list.

HeaderDescriptionMultiple Objects?Section
xProxy-Limit-IDsUsed to declare the limits which should be charged for the request.YesLimits (Continued)
xProxy-Request-TagsFree form, custom strings used for later reference and data correlation.YesRequest Tags
xProxy-User-IDA free form, custom string used to identify the user the request is associated with.NoUserIDs
xProxy-Experience-IDA unique identifier associated with an instance of an Experience Type.NoExperiences (Continued)
xProxy-Experience-NameThe name of an Experience Type, used when making the initial request of a new Experience to automatically create it and return a new experience_id.NoExperiences (Continued)
xProxy-Logging-DisableWhen set to True Pay-i will not log the request or response details, but will still account for costs, errors, latency, and other metadata. Use this when a request contains sensitive information that your developers will not need to see in order to debug issues.No
xProxy-Provider-BaseURIWhen using Pay-i as a proxy for a Provider, it will default to that Provider's SaaS endpoint. Use this header to change the Provider URI so Pay-i can proxy to a custom/hosted endpoint.

Note that Azure, Bedrock, and Google Vertex require the use of this header as they do not have generic API endpoints.
No
xProxy-RouteAs-ResourceFor Azure OpenAI only. Azure OpenAI obfuscates the model that is deployed in your Azure resource. This header is used to tell Pay-i which resource is deployed so that the costs can be tabulated correctly.No
xProxy-Forward-*Used to forward custom headers to the Provider.-Header Forwarding