Endpoints & Knowledge
Endpoints the agent can call, the knowledge base it retrieves from, and extensions.
The two capabilities that make an agent useful: Endpoints (tools it can call) and the Knowledge base (content it can retrieve from). See also the consumer Tools & Knowledge guide.
Endpoints
The external endpoints a project's agent is allowed to call — tools it uses to fetch data or take actions while answering.
- Endpoints list — all of the project's tools as a grid or list, with search, filter by source (added manually vs. via a connected MCP client), and sort. Each tool previews its request details, usage stats and success rate, and payloads. Tools with active health alerts are flagged.
- New endpoint — a guided flow: describe the request, describe the inputs, then review and create. Work is validated step-by-step and drafts are preserved.
- Edit endpoint — adjust a tool's definition, request and input schema, authentication and headers, and execution limits; enable or disable it; and see its health.
A tool defined by path only inherits the project's default tool base URL, and must be enabled to be callable by the agent.
Knowledge base
The documents a project's agent can draw on when answering (retrieval-augmented generation). Curate this content so answers are grounded in your own material.
- View all knowledge documents as a grid or list; search and filter by source type (files, URLs, or pasted text).
- Upload a document — provide a title, content, and optional tags.
- Preview a document's details and provenance (added manually vs. via a connected MCP client), and delete documents.
Content added here becomes retrievable context for the agent when knowledge-base retrieval is enabled.
Extensions
Installable add-on capabilities that extend what a project's agent can do. Operators browse the available catalogue, enable the ones they want for the project, configure each extension with its own settings, and monitor its performance metrics. Enabling an extension checks for conflicts with (and dependents among) other enabled extensions first. Extensions are configured per project — the same extension can be set up differently across projects.