Troubleshooting
Most problems here are one click from fixed. Find the message you're seeing, or the thing that isn't happening, and follow the line. If nothing fits, the bottom of the page has a person.
Connecting
"This request expired" on the sign-in page. Connection links live fifteen minutes. Go back to your AI client and start the connection again; the new link is fresh.
"This link is no longer valid." The link was already used, or it never existed. Same fix: start the connection again from your client.
You signed up by email and the connection didn't complete. Email accounts need to open the verification link we send first. Open it, then start the connection again from your client. Google, GitHub and Discord sign-ins skip this step.
The consent page says the client runs on your own machine. That's expected for Claude Code and other local tools. Approve it only if you just started the connection from an app on that computer.
Hiasynth isn't in the directory yet. In Claude, choose Add custom connector and paste https://mcp.hiasynth.co. In ChatGPT the directory listing is the only route; if it isn't there, it's still under review.
Asking
"Your Hiasynth account is connected, but population queries need an active subscription." The connection is fine. Subscribe on your Hiasynth account, see Pricing, and ask again.
The assistant answers without using Hiasynth. It didn't reach for the tool. In Claude, open the + menu in the chat and check that the connector is switched on for that conversation. In any client, naming Hiasynth in the question helps: "use Hiasynth to count...".
The answer says a country isn't in the build. Coverage is Europe, and a few countries are still being added. The tool says so rather than guessing. What's inside lists what's covered.
A whole-continent question is slow. A question with no place in it scans everything. Name a country, region or city and it comes back in seconds.
The answer looks wrong. Every answer carries a confidence tier and the baseline it was compared against. If a number still looks off, send us the question and the answer: that's the fastest way to make it better.
Credits and billing
Out of credits mid-month. Add a pack from your home page. Packs sit behind the monthly allowance and never expire.
You want a warning before it happens. Under Settings on your account page, switch on the low-credit email and set the balance it fires at.
A payment failed. Queries pause until it clears. Update your card from the billing portal on your account page and everything picks up where it left off; your balance is untouched.
You cancelled and want back in. Resubscribe from your home page. The credits you had are spendable again the moment you do. If you were on the launch price, note that coming back is at the standard price.
Keys and clients
You lost an API key. We can't show it again. Revoke it under API keys on your connector page and create a new one.
You want to disconnect a client. Same page, under Connected clients. Disconnecting a client does not sign you out of hiasynth.co, and signing out of hiasynth.co does not disconnect clients.
You connected in the beta with a config-file entry. Early testers used a block in Claude Desktop's config file with a personal key. Replace it with the connector: quit Claude Desktop, delete the hiasynth entry from claude_desktop_config.json (in the Claude folder under Application Support on macOS, under AppData on Windows), reopen, and follow Start in Claude. Then revoke the old key on your connector page. Your complimentary credits stay on the account.