Agents
Configure responsibilities and tools, run sessions, and serve users through an API or a web interface.
Use agents to answer product questions, retrieve business data, or carry out tool tasks. You configure the model, instructions, and tools. Praxis manages session execution and event history; your application decides who can use the agent and which business operations they may perform.
Who this is for
Add a ready-made conversation interface to an existing product and pass in the signed-in user and current page. For custom interfaces, background tasks, or non-web clients, create sessions and read events through the API. Agents retrieve business data through authorized tools; your business server still enforces order ownership.
If you need a single model call or want to write the model and tool loop yourself, start with Models. Agents suit applications that need reusable configurations, ongoing conversations, and a record of task execution.
How the objects relate
| Object | Responsibility | Relationship |
|---|---|---|
| Agent | Name, instructions, model, and tools | Saving configuration creates a version; one agent can have many sessions |
| Session | A separate conversation and execution state | Pins an agent version at creation; later configuration edits do not replace that snapshot |
| Environment | Machine configuration for a session | API sessions can omit the environment for a light machine, or select a sandbox environment |
| Event | User messages, agent replies, tool calls, and status changes | Belongs to a session; accepting input is separate from producing a reply |
| End user | A person using your product | An embed token binds session access to that user and agent |
Service agents serve your customers with a separate environment per session. Personal agents bind to a persistent computer. The integration guides focus on service agents. See Agents and sessions for details. Public agent IDs have the form agent_…; use the value returned by creation or retrieval.
Choose a delivery format
| Format | You provide | Start here |
|---|---|---|
| API | Server authentication, message and event handling, your own UI | Run your first agent |
| PraxisKit | A component in your website, identity, and business interactions | Embed in a web page |
| iframe | A token endpoint and a loader for the hosted UI | Embed with a script |
| Hosted | User authentication and a redirect to a short-lived link | Open hosted chat |
React is one way to use Kit. Public documentation Q&A can use anonymous visitors. For account data, your backend must verify the signed-in user before issuing a token. See Choose an integration for the full comparison.
Continue by task
- Change instructions, models, or versions: Configure an agent.
- Supply page information and business capabilities: Pass context and Configure tool authorization.
- Investigate customer issues: Inspect sessions and usage and Manage end users.
- Prepare to launch: Test your integration and Go-live checklist.
Next: API reference · Documentation Q&A recipe · Limits and errors