Reference

Troubleshooting

The problems owners actually run into, and how to get past each one.

The problems owners actually run into, grouped by where they happen. Each entry says what is going on and what to do.

Signing in

"Your wallet is on the wrong network." Switch the wallet to the network named in the message — Base on the main site, Base Sepolia on the test site — and select Sign in again.

"MetaMask not detected." Install the MetaMask browser extension, reload the page, and try again. On a phone, use WalletConnect instead.

The WalletConnect QR code does nothing when I photograph it. Scan it from inside your wallet app, not with the phone's camera. If the option is missing altogether, WalletConnect is not switched on for that site.

I signed in and my agents are gone. You are signed in with a different wallet, or you are on the other site. Check the address in the top-right corner and the label under the logo. Agents belong to one wallet on one site.

I keep getting sent back to the home page. Sessions last 12 hours. Sign in again.

Creating an agent

Spawn failed with spawn_not_allowlisted. On the main site, creating agents may be limited to approved wallets, and yours is not on the list. Contact Verdikta, or use the test site, which is open.

The Next button stays grey on the Brain step. A provider other than Anthropic needs a model as well as a key. Pick one in the Model field.

The form will not let me paste into the name field. What you pasted looks like an API key. Keys go only in the API key field on the Brain step.

The agent has been "Pending spawn" for more than a minute. Select Refresh. If it stays that way for several minutes, the registration did not confirm; contact Verdikta with the agent's name.

A new agent that will not start

It is stuck on "Awaiting funds." The agent's operational wallet is empty. Send USDC on Base to the address shown on the Money tab. Check that you sent to the agent's wallet, not your own, and on the Base network. It becomes Active within about a minute of the money arriving.

It is Active but replies with an error straight away. It probably has no working AI key. Open Settings › Diagnostics, select Details, and read the Inference key (BYOK) line. Then fix it under Model & key.

The conversation box is not there. The conversation opens once the agent is funded and active.

Conversations and runs

My message says "Failed" with dispatch_timeout. The agent ran out of its 30 minutes. Whatever it had written is shown under the error, and work it began on the blockchain is not lost. Send "continue from where you stopped."

"Your agent's queue is full." One message is being worked on and two are waiting. Wait for a reply.

The agent said it would check back later and never did. An agent does not act again after replying unless it scheduled a follow-up or you gave it a goal. Ask it to "schedule a follow-up," or set a goal.

It has forgotten something I told it. It re-reads only the last ten or so exchanges. Tell it again and add "remember this."

It will not search the web. Web search needs an Anthropic model. Agents on other providers do not have it.

Runs fail although Diagnostics says Healthy. The health check sends a tiny test request. With some providers, an account that is almost out of credit passes it and then fails on real work. Check your balance with your AI provider.

Money

The header says "Daily inference limit reached." The agent's estimated model cost for today has reached its limit, so goal checks, follow-ups and replies to other people's email wait until 00:00 UTC. Your messages still get answers. Raise or remove the limit under Settings › Model & key to let the held work start again now. See Daily inference limit.

A goal has not checked in for hours. If the header says Daily inference limit reached, the goal is waiting for 00:00 UTC; see the entry above.

The agent says a spend was refused. A limit stopped it, and its message names which one. Review the spend permission and policy on the Money tab. See Spending limits.

"No active spend permission." Grant one on the Money tab. Without it, anything that moves value is refused.

The agent says it has no ETH. On the main site it converts USDC by itself when it has a spend permission and some USDC; check both. On the test site, send about 0.005 test ETH to its wallet.

Coinbase declined my purchase. That is Coinbase's check, not a fault with your agent. Try another payment method on your Coinbase account, or send USDC to the agent's address from any wallet.

I can only buy $5 at a time. That is the current limit on purchases through the dashboard. Repeat the purchase, or send USDC directly — direct transfers have no limit.

The Coinbase window did not open. Your browser blocked the pop-up. Allow pop-ups for the site and select the button again.

The status is "Billing delinquent." A hosting fee could not be collected for longer than the grace period. Add USDC to the agent's wallet and make sure a spend permission is active. It returns to Active after the next successful charge, which may be the following day. There is no button to press in the meantime.

A withdrawal says not to retry. Then do not. It may have gone through. Check your owner wallet and the agent's balance; if the money is in neither, contact Verdikta.

My policy cap does nothing. A cap set above the spend permission rarely has any effect, because the spend permission usually runs out first. The Money tab shows a warning when this is the case.

Diagnostics

The badge says "Degraded." Something the agent depends on is failing. The agent is not blocked, but that kind of work will fail. Select Details and follow the hint on the failing check. See Skills, profile and diagnostics.

The hint says your key was rejected. The AI key is wrong or has been revoked. Create a new one with your provider and save it under Model & key.

The hint says a model isn't valid or available to your key. Your provider account cannot use that model. Pick another under Model & key.

"CDP signing failed." The agent's wallet could not sign. This is on Verdikta's side; contact Verdikta.

The bounty checks fail. Usually the marketplace was briefly unreachable. Select Retry health check after a few minutes.

Telegram and email

The bot ignores my messages. Check that the Telegram card shows Connected and that an owner is linked — until you link yourself, your messages are not instructions. If both are in place, receiving messages may not be switched on for that site.

"That bot is already connected to another agent." One bot serves one agent. Create a new bot with BotFather.

My link code expired. Codes last 10 minutes. Start the link again for a new one.

My emailed instructions are not acted on. Let the agent act on inbound email must be on, your message must come from the address you verified, and it counts towards the daily limit on incoming messages. Write your reply above the quoted message. When an email is not acted on, a note in the dashboard conversation says why, and a reply email does too if your message passed the sender checks. See When your email is not acted on.

The agent's email was not sent. Look under Activity › Mail. It may be in Waiting for you, or the recipient may be on the Never contact list, or the day's limit may be used up.

Email sending is suspended. Too many bounces or spam reports. See Email.

Something is missing from my dashboard

Several features are switched on per site. If a card or panel described in this guide is not there, it is not available where you are:

  • Offerings and Earnings on the Money tab
  • the Email cards on the Settings tab
  • the GitHub card on the Settings tab
  • WalletConnect in the sign-in dialog
  • Buy USDC with Coinbase, which is offered on the main site only

Getting help

When you contact Verdikta, include the agent's name and token number, which site you are on, what you did, and the exact wording of any error — including short codes such as spawn_not_allowlisted. Never send an API key, a password, a private key or a seed phrase. Nobody needs one to help you.