---
title: "Ask Alma about a contact, choosing the area"
method: POST
path: "/api/v1/advisors/{slug}/ask"
---

# Ask Alma about a contact, choosing the area

`POST /api/v1/advisors/{slug}/ask`

## Request

- Base URL: `https://memchats.com`
- URL: `https://memchats.com/api/v1/advisors/{slug}/ask`
- Auth: HTTP bearer

There is one counsellor, Alma. The slug says which area she answers with: `alma` (and `memchats`) let her detect it from who the contact is and what the exchange is about, while `legal`, `relaciones`, `conocer` and `negocio` set it explicitly. The five retired advisor slugs are kept for backwards compatibility with existing API tokens and the published MCP server, and map onto the areas: `lexiel` to legal, `amoriel` and `pactiel` to relaciones, `cupiel` to conocer, `proxiel` to negocio. No area depends on the plan: all four are available on every plan, Free included. Same pipeline and same quota as POST /api/v1/alma/respond (consumes one LLM query from the plan quota), returned in the flat `{ answer, advisor, contact_id }` shape older clients read.

## Path parameters

- `slug` 'alma' | 'relaciones' | 'conocer' | 'negocio' | 'legal' | 'memchats' | 'lexiel' | 'amoriel' | 'cupiel' | 'proxiel' | 'pactiel', required

## Request body

- object
  - `contact_id` integer, required
  - `question` string, required

## Response `200`

Alma's answer, flattened into a single text

- object
  - `answer` string
  - `advisor` string
  - `contact_id` integer

## Other responses

- `400`: Malformed body, or a question over 2000 characters
- `404`: Contact not found
- `429`: Weekly Alma analysis quota exhausted, with `resetsAt`

---

[API](https://skmtc.dev/memchats/apis/memchats-api.md) · [All operations](https://skmtc.dev/memchats/apis/memchats-api/llms.txt) · [OpenAPI document](https://skmtc.dev/memchats/apis/memchats-api/revisions/e62bca06f785?raw)