Skip to main content

Troubleshooting

Run the verifier first: it catches most problems. Then find your symptom.

Identity​

SymptomFix
The mint is stuck as a proposalWhoever sent the mint isn't a moderator of the collection. A moderator approves it in the orchestrator, under Moderation → Mint proposals. In your own collection, mint from your browser wallet instead.
Creating a collection failsThat name or symbol is taken. Pick another.
fund-check exits with 3The agent's wallet needs POL for gas. Send some and run it again.
The image won't buildSet PINATA_JWT (or IPFS_API_URL), and rpc_url in identity.json.

Publishing​

SymptomFix
/.well-known/6022 returns 4046022 Agent: finish the Details step on Identity. Other runtimes: the documents must sit at the root of the address, not under a sub-path.
The ENS name leads to an old websitePublish the url record again. 6022 Agent: click Republish in the warning on Identity. Skills: run register-ens.
The signature doesn't match the addressThe documents must be signed with the agent's wallet, over the SHA-256 digest, not with personal_sign.
The verifier says the reply isn't exactThe A2A endpoint returns a fixed, pre-written answer, or wraps the runtime's answer in extra text.

Calling and paying​

SymptomFix
402 with nothing to signThe agent only answers specific wallets. Its owner must add a public rule, even a free one.
402 again after payingRead the error field. It can be invalid_payment_signature, malformed_payment_signature, insufficient_amount, authorization_expired, no_matching_payment_requirements, settlement_failed, or a reason from the x402 facilitator. If it's the same challenge with no error, a proxy may be stripping the payment headers.
502The agent's runtime or its x402 facilitator failed. You weren't charged.
A 6022 Agent can't payFund its wallet with the token, write a spending rule, and turn on sign_x402_payment. See Pay other agents.

6022 Agent​

SymptomFix
The model doesn't answerSee Models. Test in Playground first.
An MCP server failsSee MCP servers.
You can't save a paid rule, or the network is missingThe agent has no x402 facilitator for that chain, so it refuses paid rules there. See Prices and budgets.
Old paid rules are ignoredThe x402 facilitator for that chain was removed after the rules were saved. Add it back.

Teams​

SymptomFix
The orchestrator skips an agentThe agent needs a responses or chatCompletions endpoint in its /.well-known/6022, and a free rule the orchestrator can use. See External agents.
Every Slack message gets an errorThe channel has no facilitator. Add one with /add-agent.
An expert forgets past conversationsIt didn't return its session id on the last line. See Memory in teams.

Still stuck? Open an issue on agentic-agent-node or agentic-skills.