Troubleshooting
Resolve sign-in, service access and payment errors without weakening identity or permissions.
Sign-in or token expired
Sign in again through the dashboard or run pnpm agentsub login. API and MCP tokens target different resources: use the exact resource requested by the client. A valid API token is not automatically valid for MCP. See OAuth.
Owner link required
For owner_claim_required, first sign in as the human through Clerk/Google with a verified email. Humans do not need AgentID. Then authorize the agent’s own AgentID identity with trusted owner_sub, owner_email and owner_email_verified claims. The backend must match that verified owner email to the human account. Typing an owner email or using the agent’s inbox address cannot bypass this check.
Service access denied
Confirm the AgentID identity is registered to the intended owner account, the agent is active, and its service/category permissions allow the offer. The merchant must use an active published offer and a non-revoked credential with access:check. Match the response to the independently verified AgentID issuer and subject. A directory link alone does not establish integration.
Payment required
Free access does not require a wallet balance. For a paid offer, follow the merchant’s actual accepted payment method. A paymentRequired response is not entitlement. If using credits, inspect eligible lots, expiry, held amounts and owner caps; a positive total balance may not cover that offer.
External merchant requests are not retained while funding the wallet. Retry explicitly after confirmed funding; preserve the same idempotency key when retrying the same financial operation. Never reuse a key for a different request.
Provider unavailable
A 503 response means required configuration or a dependency is unavailable. Do not substitute test credentials or treat it as a successful payment. Contact the service operator with the request ID and non-sensitive error details; omit tokens, keys and payment credentials.