Skip to main content
The Chat Agent is a conversational AI with full awareness of your product context. It knows your research, your build plans, and your connected integrations. In a single conversation you can ask it to look up existing research, run new market analysis, expand a build tree node, kick off a Forge coding run, create a Linear issue, or post to Slack — all through natural language. Each action it takes is reflected back to you in the stream as it happens.

What the agent can do

The agent has access to a core set of ManticScore tools, plus any integration you’ve connected via Composio: ManticScore tools: Composio tools (discovered at runtime): The agent can discover and use any tool from your connected integrations — GitHub, Linear, Jira, Slack, Notion, Gmail, and 1,000+ more. It searches for the right tool, retrieves its schema, and calls it without you needing to configure anything beyond the initial connection.

Sending a message

Chat uses streaming NDJSON. Your client sends the conversation history and receives a stream of events back.
array
required
Conversation history. Each message: {"role": "user" | "assistant", "content": "string"}. Content limit: 50,000 characters per message.
string
required
Your product idea. This gives the agent context throughout the conversation. Up to 50,000 characters.
string
UUID of your project. When provided, the agent has access to all research and build graphs in that project.
string
Resume a previous conversation. The agent uses this to maintain memory across messages. Omit to start a new session.
boolean
default:"false"
Set to true if you have completed research the agent should be aware of.
boolean
default:"false"
Set to true if you have a build graph the agent should be aware of.
string
Serialized research context to inject directly into the agent’s context window. Up to 100,000 characters.

Stream events

The response is a stream of NDJSON events. Parse each line as a JSON object and handle events by the event field.
First event on every connection. Save the session_id to resume this conversation later.
The agent is starting a new reasoning turn. stop_reason tells you whether the turn ended by calling a tool or by producing a response.
The agent is calling a tool. tool_name identifies which ManticScore or Composio tool is being invoked.
Live status updates from within a running tool. When the agent calls run_research or start_implementation, pipeline stage events are forwarded here.
A chunk of the agent’s text response. Append each text value to build the full message.
Emitted at the end of the response. Contains a summary of the conversation, the tools used, and the session_id for resuming.
Final event. The stream is closed.

Managing sessions

The agent maintains memory within a session and can reference earlier messages. Each session is tied to a session_id returned in stream_start.

List sessions

curl

Get a session with full event history

curl

Delete a session

curl

Cross-session memory

The agent builds memory across sessions within a project. You can inspect or clear this memory: Fetch memories for a project:
curl
Clear memories:
curl
Omit project_id to clear all memories across all projects.

Limits and credits

Pass session_id on follow-up messages within the same conversation. The agent uses session context to avoid repeating tool calls and to give more relevant answers based on what it already retrieved.