NoClickError

One way past a refusal for money: a link a person opens to pay, no sign-in needed. Hand them url.

The request is malformed or a value is out of range; field names the argument when there is one.

No key was sent, or the key or session token isn't valid (revoked, expired, or not a platform key).

Your account can't pay for this: balanceUsd is what's left and requiredUsd what the call needs, in US dollars. offers are links a person opens to add funds or change plan; retry once one is paid. A model provider's account out of funds (your own key) throws it too, with details.reason "provider_out_of_funds". A deployed app's paid call names the app in details.project and details.project_id (invite-only beta).

if (err instanceof PaymentRequired) for (const offer of err.offers) console.log(offer.label, offer.url);

The account's plan doesn't allow this: plans cap some resources. offers are links to the plans that do.

It would cost more than the ceiling you set (max_monthly_usd on PhoneNumber.buy).

A policy wants a person to approve this call first. The approval request is already out; wait on it, then retry with approvalId:

if (err instanceof ApprovalRequired && (await err.operation?.wait()))
  await gmail.run("send_email_message", args, { approvalId: err.approvalId });

A monthly spend cap (scope: key, user, agent, ...) is used up. A deployed app's paid call names the app in project and project_id, with scope project when it's the app's own budget_usd_per_month (invite-only beta).

You paused this user's spending (user.pauseSpending()), so nothing that costs money runs for them until user.resumeSpending(). message and nextStep are for you; userMessage and action are what you asked NoClick to tell the user, to show them as they are; since is when you paused them.

The key or session lacks the scope, or the user it acts for can't do this (another user's object, a suspended user).

Your policy (noclick.Policy) forbids this tool.

Nothing by that id or name in this account, or owned by the user the call acts for.

It already exists (existing_id names it), or another call holds it, like a conversation mid-turn.

Not available here: a feature the account doesn't have yet (phone numbers), or a sandbox that has stopped.

Something has to be set up first, such as an agent answering a number before it can place calls.

The connection has no account connected yet; send the person connectUrl.

The connection's account was revoked or stopped working; send the person connectUrl to reconnect it.

A spent quota: never retried automatically.

Too many requests, or a send cap reached (emails, inbox replies); retry_after says when to try again.

A service NoClick relays to refused the call or failed. A refusal, such as an integration's service answering a run with an error, comes in its own words, its HTTP status in details.upstream_status, and answers 424: it isn't retried, since sending the same call again won't help. A failure (a model's provider down, a service that didn't answer) answers 502 and is retried; once retries run out, retrying in a moment usually works.

The work outlasted what one request may wait (about 90 seconds). Never retried automatically, since the work may still be going on: an agent's turn goes on and lands in its conversation (details.operation_id and details.conversation say where).

A 5xx the server could not describe as a platform error.

The API could not be reached, even after retries.

An operation finished failed without a more specific error type.

The operation was canceled before it finished.

A request, link or operation expired before anyone acted on it.

operation.wait({ timeoutS }) ran out before the operation finished.

A webhook delivery's NoClick-Signature doesn't match its body, or its timestamp is too old. Thrown by Webhook.verify in your receiver; answer it with a 400 and drop the delivery.