Ready Agents
Ready-to-use OpenAI-compatible agents with scoped access to knowledge bases, skills, and connected apps.
Ready-to-use OpenAI-compatible agents with scoped access to knowledge bases, skills, and connected apps.
The ready-to-use RAG agent follows the OpenAI Chat Completions format and adds multiple knowledge-base IDs plus optional skill IDs.
/api/v1/agents/rag/chat/completionsExplicit asset access
Common sampling and output parameters are supported. The agent owns tool orchestration: tools, tool_choice, functions, and function_call are not accepted, and n is limited to 1. Asset fields enforce the agent scope on the server.
| Parameter | Type | Description |
|---|---|---|
modelrequired | string | A model from the anymize model catalog. |
messagesrequired | array | OpenAI-compatible messages in conversation order. |
knowledge_base_idsrequired | uuid[] | One to eight accessible knowledge-base IDs whose processing is complete. |
skill_ids | uuid[] | Optionally, up to eight accessible skill IDs. No skill tool is exposed without IDs. |
stream | boolean | Returns an OpenAI-compatible SSE response when true. |
Existing OpenAI clients need only a different base URL and extra_body for the asset IDs.
1from openai import OpenAI23client = OpenAI(4 api_key="YOUR_API_KEY" ,5 base_url="https://app.anymize.ai/api/v1/agents/rag" ,6)78response = client.chat.completions.create(9 model="auto" ,10 messages=[11 {"role" : "user" , "content" : "Summarize the termination rules." }12 ],13 extra_body={14 "knowledge_base_ids" : ["aaaaaaaa-aaaa-4aaa-8aaa-aaaaaaaaaaaa" ],15 "skill_ids" : ["bbbbbbbb-bbbb-4bbb-8bbb-bbbbbbbbbbbb" ],16 },17)1819print (response.choices[0 ].message.content)20print (response.citations)01
It searches only the selected knowledge bases and retrieves exact passages.
02
It loads only explicitly selected skills and their bundle files when needed.
03
It writes the answer and adds protected, clickable links to every passage it uses.
Internal tool calls stay hidden. Streaming returns normal OpenAI SSE chunks followed by the deduplicated citations list.
The ready Connected Research Agent reads only from the connected apps selected through connector_ids. It discovers their tools progressively and keeps the model context small.
/api/v1/agents/connected-research/chat/completionsIntentionally read-only
The paginated asset catalog returns the exact knowledge bases, skills, and connector references the authenticated user may select. Use offset and limit until has_more is false for every asset family. Built-ins use values such as provider:microsoft; custom MCPs use custom:UUID.
/api/v1/agents/assets1curl "https://app.anymize.ai/api/v1/agents/assets?offset=0 &limit=100 " \2 -H "Authorization: Bearer YOUR_API_KEY" Common sampling and output parameters are supported. The agent owns tool orchestration: tools, tool_choice, functions, and function_call are not accepted, and n is limited to 1. Asset fields enforce the agent scope on the server.
| Parameter | Type | Description |
|---|---|---|
modelrequired | string | Connector access requires waterfall-2.0 so private app data stays inside the protected anymize environment. |
messagesrequired | array | OpenAI-compatible messages in conversation order. |
connector_idsrequired | string[] | One to eight connector references from GET /api/v1/agents/assets. |
skill_ids | uuid[] | Optionally, up to eight accessible skill IDs. No skill tool is exposed without IDs. |
knowledge_base_ids | uuid[] | Optionally, up to eight processed knowledge bases for internal evidence and clickable citations. |
stream | boolean | Returns an OpenAI-compatible SSE response when true. |
The agent sees only Microsoft 365 and HubSpot from this request. Other connected apps remain invisible.
1from openai import OpenAI23client = OpenAI(4 api_key="YOUR_API_KEY" ,5 base_url="https://app.anymize.ai/api/v1/agents/connected-research" ,6)78response = client.chat.completions.create(9 model="waterfall-2 .0 " ,10 messages=[11 {"role" : "user" , "content" : "Summarize today's customer meetings and the latest CRM activity." }12 ],13 extra_body={14 "connector_ids" : [15 "provider:microsoft" ,16 "provider:hubspot" ,17 ]18 },19)2021print (response.choices[0 ].message.content)01
The server verifies every connector ID, compliance rule, and enabled capability before the first model call.
02
The model initially sees one dispatcher and loads only the apps and tools needed for the task.
03
Authorization and connection state are checked again before every call. Unknown or mutating tools remain removed.
Clickable anymize chunk citations are produced for knowledge-base results. Connector results may provide native source links, but they are not emitted as internal chunk citations.
The Workspace Agent combines knowledge bases, skills, and connected apps in one OpenAI-compatible request. Each asset family is attached only when its IDs are provided.
/api/v1/agents/workspace/chat/completionsOne agent, explicit capabilities
Common sampling and output parameters are supported. The agent owns tool orchestration: tools, tool_choice, functions, and function_call are not accepted, and n is limited to 1. Asset fields enforce the agent scope on the server.
| Parameter | Type | Description |
|---|---|---|
modelrequired | string | Any supported model without connectors. With connector_ids, waterfall-2.0 is required. |
messagesrequired | array | OpenAI-compatible messages in conversation order. |
knowledge_base_ids | uuid[] | Optionally, up to eight processed knowledge bases for internal evidence and clickable citations. |
skill_ids | uuid[] | Optionally, up to eight accessible skill IDs. No skill tool is exposed without IDs. |
connector_ids | string[] | Optionally, up to eight namespaced connector references. No connector tool is attached without IDs. |
stream | boolean | Returns an OpenAI-compatible SSE response when true. |
The same secure building blocks create several specialized agents. Change only the IDs and task.
01
Combines calendar, CRM, internal policies, and a relevant skill into an evidence-backed customer briefing.
02
Combines Elicit research with internal knowledge bases and clickable evidence.
03
Analyzes PostgreSQL or MySQL through strictly read-only tools without changing data.
1from openai import OpenAI23client = OpenAI(4 api_key="YOUR_API_KEY" ,5 base_url="https://app.anymize.ai/api/v1/agents/workspace" ,6)78response = client.chat.completions.create(9 model="waterfall-2 .0 " ,10 messages=[{"role" : "user" , "content" : "Prepare a briefing for my next customer meeting and cite internal claims." }],11 extra_body={12 "knowledge_base_ids" : ["aaaaaaaa-aaaa-4aaa-8aaa-aaaaaaaaaaaa" ],13 "skill_ids" : ["bbbbbbbb-bbbb-4bbb-8bbb-bbbbbbbbbbbb" ],14 "connector_ids" : ["provider:microsoft" , "provider:hubspot" ],15 },16)1718print (response.choices[0 ].message.content)19print (response.citations)The hosted Skills MCP lets external MCP clients read accessible anymize skills. Together with the Knowledge MCP, an agent can use both asset types.
/api/mcp/skillsAPI key required
Configure knowledge bases and skills as separate MCP servers so the client can distinguish their permissions and tool calls.
1{2 "mcpServers" : {3 "anymize-knowledge" : {4 "url" : "https://app.anymize.ai/api/mcp" ,5 "headers" : { "Authorization" : "Bearer YOUR_API_KEY" }6 },7 "anymize-skills" : {8 "url" : "https://app.anymize.ai/api/mcp/skills" ,9 "headers" : { "Authorization" : "Bearer YOUR_API_KEY" }10 }11 }12}| Parameter | Type | Description |
|---|---|---|
list_skills | tool | Lists the skills the API-key owner is allowed to access. |
get_skill | tool | Loads metadata, instructions, and the file list for one skill by UUID. |
read_skill_file | tool | Reads one bundle file from an accessible skill through a safe relative path. |
Inside the ready RAG agent, these tools are further restricted to skill_ids from that request. Automatically active project or team skills are not added silently.
Every RAG result contains chunk_id and citation_url. The link opens the source in anymize and highlights the exact cited passage.
/api/v1/chunks/{chunk_id}The chunk UUID identifies a passage in the current index. Reindexing can assign a new UUID. citation_id and job_id remain available for existing integrations.
{
"chunk": {
"id": "cccccccc-cccc-4ccc-8ccc-cccccccccccc",
"job_id": "dddddddd-dddd-4ddd-8ddd-dddddddddddd",
"knowledge_base_id": "aaaaaaaa-aaaa-4aaa-8aaa-aaaaaaaaaaaa",
"content": "The notice period is three months to the end of a quarter.",
"chunk_index": 7,
"source": "vertrag.pdf",
"page": 4,
"section": "Laufzeit",
"citation_url": "https://app.anymize.ai/chunk/cccccccc-cccc-4ccc-8ccc-cccccccccccc"
}
}Open citation_url directly from a Markdown answer. After sign-in, anymize loads the document, moves to the passage, and highlights it.
Access stays protected