Custom Properties
Add custom metadata to LLM requests for advanced segmentation and analysis. Tag requests with session IDs, conversation context, or application data to gain deeper insights into your AI application performance.
Who can use this feature: Anyone on any plan.
Introduction
Custom Properties allow you to add any additional information to your requests, such as:
- The
session,conversation, orappid - The
prompt chainby adding a common value to group of requests Applicationorusermetadata making the request
Custom Properties appear as headers in the `Request` table.
Why Custom Properties
- Get the total cost or latency for a group of requests in a prompt chain
- Get the “unit economics” of your application. For example, the average cost of a conversation.
- Slice and dice your requests and metrics by any custom property.
Quick Start
Adding Custom Properties at Request Time
Use headers to add Custom Properties to your LLM requests.
Define the Header
Name your header in the format Helicone-Property-[Name] where Name is the name of your custom property.
Define the Value
The value is a string that labels your request for this custom property. Here are some examples:
Updating Custom Properties After Request
You can also update Custom Properties post-request submission by making a PUT request to a designated API endpoint.
Obtain the Request ID
Make a PUT Request
Here are the code snippets on how to make a PUT request:
PUT Request API
Check out the detailed documentation.
Was this page helpful?