| Test sign-in fails |
See the fixes in Test sign-in. |
| An action fails with “blocked URL” |
Gephyr only calls HTTPS addresses on the hosts you’ve listed. Add your API host, and make sure it isn’t an IP address or an internal hostname. |
| An action times out |
Each call has 15 seconds. Speed up the endpoint, or use one that returns less. |
| “Response too large” |
Responses over 1 MB are refused. Use paging or a narrower endpoint, and hide fields assistants don’t need. |
| Assistants pick the wrong action, or none |
Improve the action’s description: what it does, when to use it, what the inputs mean. Fewer, task-shaped actions work better. |
| Agents fill inputs wrongly, or get empty answers |
Describe each input with an example, and put any rule (“at least one of”, date limits) in the endpoint’s description. See Make your API agent-ready. |
| Users get “connection has expired” often |
Make sure refresh tokens are enabled and long-lived in your auth provider, and that offline access is allowed (in Auth0, Allow Offline Access on your API). |
| Users or agents say they hit a limit |
Gephyr’s protection limits how often each user’s agent can use each action. If real users reach a limit, raise it for that action on the Protection tab and publish. |
| Paying customers are told it’s not part of their plan |
Check who can use it on the Login step: the claim or address Gephyr reads, the path to the plan, and the values that mean paying (spelled as your app stores them). With a token claim, a new plan shows once the user’s token refreshes, within the hour. |
| A confirmed action says the result is uncertain |
Your API timed out or errored after the request was sent, so Gephyr can’t tell whether it happened. It won’t run it again automatically. Each one is listed under Check these at the top of Overview, with its time, action, AI app and Open receipt: look it up in your system by the receipt id (your API got it in the Gephyr-Receipt header) or by time before the user asks again. See Receipts. |
| The CLI says “Not signed in” or “isn’t signed in any more” |
Run gephyr login again. A computer is signed out after 90 days without use, a year after it signed in, or when someone signs it out on the console’s Gephyr CLI page. |
| “That code isn’t waiting for approval” |
Codes work once, for 10 minutes. Run gephyr login again and type the new code. |
gephyr logout says it couldn’t sign out |
Gephyr couldn’t be reached, so the computer is still signed in. Try again, or sign it out on the console’s Gephyr CLI page. |
| Publish & share says it couldn’t list your app in the MCP Registry |
The message gives the registry’s reason. Your app is live either way, and Gephyr tries again the next time you publish. If it says your connector address is already used by another server, email hello@gephyr.ai. |
| “Gephyr can’t find your DNS record” |
Add the TXT record shown under List it under your own domain instead exactly as shown, on the domain itself (often written @), then choose Check the record and publish again. New records can take a few minutes to show. Until then, your current listing stays up. |
| The CLI can’t change an app’s API address or limits |
Once an app has been published, its API address, hosts, who can use it and its limits change only in the console. |