API and MCP
Everything the interface can do is also possible via the API: chats, messages, projects, assistants, files, memory, tasks, credit and team.
REST API
Everything the interface can do is also possible via the API: chats, messages, projects, assistants, files, memory, tasks, credit and team.
- Settings → Developer → API keys → New key. Select only the permissions you need.
- You will only see the key once. Keep it somewhere safe.
- Documentation: chat.agiledeveloper.de/docs, OpenAPI at
/api/openapi.json.
The quickest way to an answer:
curl https://chat.agiledeveloper.de/api/v1/antworten \
-H "Authorization: Bearer agile_chat_…" \
-H "Content-Type: application/json" \
-d '{"nachricht": "Summarise the advantages of prepaid billing in three sentences.", "modus": "sparsam"}'API calls cost the same as answers in the interface and appear in your usage. Connector credentials can never be read via the API.
Webhooks
Under Settings → Developer → Webhooks you can be notified when an answer or task is finished or when your credit is low. Every request is signed.
MCP for other AI assistants
Via MCP, other AI assistants can use Agile Chat as a tool: search and read chats, ask Agile Chat questions, list projects and assistants, check credit. The setup is described at chat.agiledeveloper.de/docs/mcp.