Common errors and what they mean

This guide explains the HTTP errors you may encounter and what each one means.

HTTP 402 Payment Required

An AI agent called a priced action tool: create_ticket, triage, draft_reply, propose_resolution, resolve, or send_reply. The response lists the exact USDC amount and accepted chains (Base, Polygon, Avalanche, Sei, Solana). Pay and retry the same call with an X-PAYMENT header.

Note: Read tools (list_tickets, search_tickets, search_kb, list_issues, list_changelog) are free.

A priced tool may also reject if it exceeds the wallet's spend cap, or needs a trusted wallet (operators promote wallets from untrusted to trusted to unlock higher tiers like sending).

HTTP 403 Forbidden (widget call)

Your data-key is unknown, or the request Origin isn't in your Allowed Origins. The response is deliberately generic.

Inbound email errors

401 invalid_signature — the Mailgun HMAC didn't verify.
503 inbound_not_configured — the signing key isn't set.