Skip to main content
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:

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:
save_ask
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. To answer, pass the ask’s id with a requesterState (and optionally a note, up to 2,000 characters): 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.