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

# Asks

> File and track anything you are waiting on Semicola for.

An **ask** is anything you're waiting on Semicola for: help with something broken, a capability that
doesn't exist yet, supply you want to buy, an integration, or a commercial question.

Every ask has one type:

| Type          | Use it when                                                          |
| ------------- | -------------------------------------------------------------------- |
| `support`     | Something is broken or blocking you, or you need a person.           |
| `product`     | The capability doesn't exist yet.                                    |
| `supply`      | You're a buyer looking for inventory Semicola doesn't carry.         |
| `integration` | Semicola doesn't connect to the system you need.                     |
| `commercial`  | You need help with pricing, terms, billing or a rate-card exception. |

## File an ask

In chat, tell Semi what you need; it files the ask after you confirm. Agents on `/mcp/v3` use
`save_ask` for every type:

```json save_ask theme={null}
{
  "type": "integration",
  "title": "Connect our CRM for conversion uploads",
  "subject": "CRM"
}
```

| Field      | Notes                                                                                     |
| ---------- | ----------------------------------------------------------------------------------------- |
| `title`    | Required for a new ask, up to 200 characters.                                             |
| `type`     | Optional. If it's unclear, leave it out rather than delay: the ask is filed as `support`. |
| `detail`   | Support: what is broken or blocking (up to 4,000 characters).                             |
| `subject`  | Supply and integration: the inventory or system you need.                                 |
| `channel`  | Supply: the channel you want to buy.                                                      |
| `severity` | `low`, `medium` or `high`.                                                                |

`save_ask` returns an `askId`, the `type`, `title`, `status` and your `requesterState`.

Secrets are removed before anything is stored: API keys, tokens and passwords pasted into a title,
detail or note are scrubbed from the ask, the transcript and the call logs.

## Status and your answer

Semicola's status and your own answer are kept side by side, so "we marked it done" and "you're still
blocked" can both be true.

| `status`      | Shown as    | Meaning                                                                           |
| ------------- | ----------- | --------------------------------------------------------------------------------- |
| `received`    | Received    | Semicola recorded the ask.                                                        |
| `accepted`    | Accepted    | Acknowledged or planned, without a promised delivery date.                        |
| `in_progress` | In progress | Someone is actively working on it.                                                |
| `done`        | Done        | The change is verified live and waits for your confirmation.                      |
| `closed`      | Closed      | An explicit no-change or cancellation outcome; you can acknowledge or dispute it. |

To answer, pass the ask's `id` with a `requesterState` (and optionally a `note`, up to 2,000
characters):

| `requesterState`     | Meaning                                                    |
| -------------------- | ---------------------------------------------------------- |
| `confirmed_resolved` | The outcome you asked for happened.                        |
| `accepted`           | You acknowledge an answer that closed it without a change. |
| `still_blocked`      | The release or answer didn't unblock you.                  |
| `withdrawn`          | You no longer want it pursued.                             |

Title, type and severity are fixed after filing. Only the person who filed an ask or an account admin
can withdraw it.

## Read your asks

* In the app: **Your requests** (ask Semi "what am I waiting on?" or call `open_customer_requests`).
* MCP: `search` with `kind: "ask"`, then `get` with `kind: "ask"` and the id.
* REST: `GET /api/v2/asks` (`limit`, `cursor`), newest customer-visible update first.

All reads are scoped to your account; another account's ask id looks the same as a missing one.
Finished asks stay in your recent history for 90 days.

## Not available yet

* Release details on a finished ask (version, date, what changed) and a notification when it's
  delivered.
* The older supply-request endpoints (`/api/v2/supply-requests`); file supply asks with `save_ask`.

## Related

* [Ask Semi](/sell/ask-semi)
* [Semi confirmations](/setup/semi-confirmations)