{
"jsonrpc": "2.0",
"id": "request-123",
"result": {
"task": {
"id": "task-456",
"context_id": "context-789",
"status": "completed",
"history": [
{
"message_id": "msg-1",
"role": "agent",
"parts": [
{
"kind": "text",
"text": "Response from agent"
}
]
}
]
}
}
}Send a message to an Agno Agent, Team, or Workflow. The Agent, Team or Workflow is identified via the ‘agentId’ field in params.message or X-Agent-ID header. Optional: Pass user ID via X-User-ID header (recommended) or ‘userId’ in params.message.metadata.
{
"jsonrpc": "2.0",
"id": "request-123",
"result": {
"task": {
"id": "task-456",
"context_id": "context-789",
"status": "completed",
"history": [
{
"message_id": "msg-1",
"role": "agent",
"parts": [
{
"kind": "text",
"text": "Response from agent"
}
]
}
]
}
}
}Message sent successfully
Represents a successful JSON-RPC response for the message/send method.
Represents a single, stateful operation or conversation between a client and an agent.
Show child attributes
Represents the status of a task at a specific point in time.
Show child attributes
Defines the lifecycle states of a Task.
submitted, working, input-required, completed, canceled, failed, rejected, auth-required, unknown Represents a single message in the conversation between a user and an agent.
Show child attributes
Identifies the sender of the message. user for the client, agent for the service.
agent, user "message""2023-10-27T10:00:00Z"
Show child attributes
Show child attributes
Identifies the sender of the message. user for the client, agent for the service.
agent, user "message""task""2.0"Was this page helpful?