Endpoint
POST /v4/profile
Retrieves a user’s profile, optionally combined with search results.
Request
Headers
| Header | Required | Description |
|---|---|---|
Authorization | Yes | Bearer token with your API key |
Content-Type | Yes | application/json |
Body Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
containerTag | string | Yes | The container tag (usually user ID) to get profiles for |
threshold | float | No | Threshold for filtering search results. Only results with a score above this threshold will be included. |
q | string | No | Optional search query to include search results with the profile |
Response
Response Fields
| Field | Type | Description |
|---|---|---|
profile.static | string[] | Long-term, stable facts about the user |
profile.dynamic | string[] | Recent context and temporary information |
searchResults | object | Only present if q parameter was provided |
searchResults.results | array | Matching memory results |
searchResults.total | number | Total number of matches |
searchResults.timing | number | Query execution time in milliseconds |
Basic Request
Profile with Search
Include a search query to get both profile data and relevant memories in one call:Profile with Threshold
Use the optionalthreshold parameter to filter search results by relevance score:
Error Responses
| Status | Description |
|---|---|
400 | Missing or invalid containerTag or threshold |
401 | Invalid or missing API key |
404 | Container not found |
500 | Internal server error |
Rate Limits
Profile requests count toward your standard API rate limits. Since profiles are cached, repeated requests for the same user are efficient.See Examples
View complete integration examples for chat apps, support systems, and more