---
name: justcallme
description: Ask the user a specific blocking decision through JustCallMe and retrieve their confirmed answer. Use when a task needs human input.
---

# JustCallMe

Read JUSTCALLME_API_KEY from the process environment; keep it out of prompts and logs.

API base: https://justcallme.dev

1. Summarize the blocking question and up to eight choices. Put the background the call agent needs into context (up to 8000 characters); it can discuss the question with you before deciding. Keep secrets out.
2. POST /api/calls with Bearer authentication, JSON question/context/choices, and a new Idempotency-Key UUID. Reuse that UUID for retries of the same question. Save the returned id with the task.
3. GET /api/calls/{id} every 3 seconds for up to 180 seconds. Authentication is required. An HTTP/network error is not permission to repeat the call.
4. On answered status, treat answer as user input bound to this task and POST /api/calls/{id}/ack. The record also carries transcript, the full two-sided conversation, written once the call ends, so read it after ack to learn everything that was discussed, not only the chosen option. No transcript means the call has not finished yet or the caller never spoke. Follow the agent's existing permissions before executing actions.
5. On timeout, failed, expired, or cancelled status, keep the task paused. Retrieve the same request on resume. Avoid default approvals.

Calls last up to 120 connected seconds. Billing is by connected time in minutes, rounded up to the next 10 seconds once per answered call. The server chooses the verified recipient. A skill supplies instructions; it cannot restart a terminated agent session. If the developer says goodbye or asks for the conversation to be passed on, the call agent thanks them and ends the call.