The Mind-e API lets you send chat messages, manage web sources, check credits, and more — all programmatically.Documentation Index
Fetch the complete documentation index at: https://mind-e.co/docs/llms.txt
Use this file to discover all available pages before exploring further.
Base URL
Authentication
Most API endpoints require authentication using a Bearer token. Pass your API key in theAuthorization header:
Some endpoints are public (no authentication required) — these are used by the embeddable chat widget. They are marked as “Public” in the documentation.
Request format
- Send JSON in the request body with
Content-Type: application/json - File uploads use
multipart/form-data - Query parameters are passed in the URL
Response format
All responses return JSON with asuccess field:
HTTP status codes
| Code | Description |
|---|---|
| 200 | Success |
| 400 | Bad request — invalid parameters or validation error |
| 401 | Unauthorized — missing or invalid API key |
| 402 | Payment required — insufficient credits |
| 404 | Not found — resource doesn’t exist |
| 429 | Rate limited — too many requests |
| 500 | Server error |
Rate limiting
API requests are rate limited. When rate limited, the response includes these headers:| Header | Description |
|---|---|
X-RateLimit-Limit | Maximum requests allowed in the window |
X-RateLimit-Remaining | Remaining requests in the current window |
X-RateLimit-Reset | Unix timestamp when the window resets |
429 response, wait until the reset time before retrying.
Credits
API chat requests consume credits just like widget conversations. The response includes acredits object showing how many credits were used and your remaining balance.