> ## Documentation Index
> Fetch the complete documentation index at: https://docs.famulor.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Ask Milian

> Ask Milian from your API client with explicit approval of additional credits.

Milian can answer questions, analyse permitted workspace data, and recommend next steps through **POST /api/v1/milian/ask** or the **ask\_milian** MCP tool. It does not change workspace resources.

## Approval and credits

Before **every** question, tell the user that Milian uses **additional workspace credits** and ask for explicit approval. Set `confirmed` to `true` only after that approval. Connecting a client or granting access does not approve future paid questions.

Usage is charged to the active workspace at the **same rates as Milian in the dashboard**. Available credits are checked before generation. The response reports the credits actually charged; completed work may still be charged if a later step fails. Each follow-up or retry is a new paid question: do not retry automatically.

## Access

Use a workspace API key or OAuth token with `milian:write`. Data access also requires the relevant read scopes, such as `calls:read`. For OAuth, select **Milian** and the data groups you want it to analyse. Milian is optional and is not included in the default seven groups or the public assistant-history profile. Viewer and billing roles cannot start paid questions.

Questions are standalone. Include the context Milian needs; these questions are not added to dashboard chat history.

## Request

```bash theme={null}
curl -X POST https://app.famulor.io/api/v1/milian/ask \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"question":"Analyse my recent calls and suggest improvements.","confirmed":true,"locale":"en"}'
```

Only run this example after the user has approved the additional credits. On your own branded domain, use that domain in place of `app.famulor.io`.

## Response

```json theme={null}
{"data":{"id":"00000000-0000-4000-8000-000000000001","status":"completed","answer":"Your analysis…","credits":2.35,"billing_complete":true}}
```

The credit amount above is illustrative, not a fixed price. Check `status` and `billing_complete` before treating the request as complete. Insufficient credits before generation return HTTP 402. A missing approval returns HTTP 400. Unauthorized scopes or roles return HTTP 403.

See [MCP tools and scopes](/mcp/tools-and-scopes) for connection setup.