Skip to main content
The /store_knowledge endpoint allows you to store agent interactions and experiences for future task enhancement. This endpoint should be used whenever an agent is complete with a task. If your agent spawns sub sub agents, each sub task agent should also call this endpoint once it’s complete.

Base URL

Authentication

Request Body

Root Level Parameters

string
required
Unique identifier that corresponds to a dedicated recommendation collection, enabling sub-tenancy isolation for different agentic workflows
string
required
The original user query or instruction that initiated the interaction
array
required
Array of interaction turns between the agent and the environment/user
boolean
Indicates whether the agent completed its task successfully
string
Specifies the type of agent (e.g., ‘browser’, ‘voice’)
string
required
When the interaction occurred (ISO format)
object
Additional metadata about the interaction

Turn Object Structure

Each turn in the turns array represents a single interaction step and contains the following fields:
number
required
The turn number in the interaction sequence. Must start at 1 and be sequential without gaps. For single-turn agents, this should be 1.
string
required
The flattened input the agent sees at this turn. Should include:
  • Available tools and options
  • Current observations
  • Each tool/option should be listed on a new line
string
required
The output or action taken by the agent during this turn
string
What the agent remembers from this turn, such as:
  • Values returned from a RAG store
  • User intent understanding
  • Key context or decisions made
string
The outcome of the agent’s action, including:
  • User interruptions
  • Action success/failure
  • Any deterministic results

Example Requests

Response

Success Response

string
required
Status of the request (will be “accepted”)
string
required
Human-readable status message
string
required
The tenant ID that was used for the request
Example success response:

Error Response

string
required
Error code identifying the type of error
number
required
HTTP status code
string
required
Human-readable error message
object
Additional error details when available
Example error response:

Status Codes

Error Codes

Best Practices

  1. Turn Numbers
    • Ensure turn numbers are sequential
    • Always start from 1
    • Avoid gaps in the sequence
    • For single-turn agents, use turn number 1
  2. Input Documentation
    • Document all available tools and options in the inputs field
    • List each tool/option on a new line
    • Include relevant observations and context
  3. Memory Management
    • Use the memory field to track important context
    • Include relevant RAG results
    • Document key decisions and user intent