Skip to main content
Confirm that the URL is exactly https://api-dispatcher.bily.ai/mcp. The client must support remote Streamable HTTP MCP servers.Do not use https://app.bily.ai/mcp, llms.txt, or llms-full.txt as the endpoint. Reload the client after you update its configuration.
Confirm that the client supports MCP OAuth discovery, Authorization Code with PKCE S256, refresh tokens, and the mcp_access scope.The MCP endpoint answers an unauthenticated request with the discovery challenge. Compatible clients follow that challenge automatically.If the client cannot complete the flow, use an access key fallback.
A 401 means the credential is missing, invalid, expired, or revoked. Reconnect through Bily Connect or replace the fallback key.Do not send a Bily Connect credential and x-api-key together.
Reconnect through Bily Connect. Bily rotates refresh credentials for security.Reusing an older refresh credential or losing the latest refresh response can invalidate the connection.Do not paste credentials into the client or keep retrying an older credential.
A 403 means the connection is authenticated, but the requested organization, store, permission, or action is outside its allowed scope.With Bily Connect, confirm that the signed-in user still belongs to the organization that owns the store.With a fallback key, use only the default store and organization recorded when the key was created.If the response requires store scope, select the intended store and create a replacement key under Settings > MCP.
Describe the outcome, resource, and intended read or write. Add an accessible storeUrl when the request depends on connected store operations.Set limit from 1 to 20.Do not guess a helper name when search does not return it.
Pass a string that contains an async arrow function:
async () => {
  return bily.context();
}
Keep the code at or below 20,000 characters. Return JSON-serializable data.
One execution can run for at most 20 seconds. Split broad work into smaller calls. Reduce query ranges or result limits, and return only the fields needed for the next decision.
Approval is expected for write, spend-affecting, and destructive operations. Review the function, store, proposed changes, planning metadata, and verification step in the client.Bily’s planning metadata does not replace the client approval prompt.
Use search again. Review the operation’s preconditions, input schema, verification guidance, and connected-store requirements.Confirm that dates are real calendar dates and the requested store is correct.

Send safe diagnostic details to support

Record the client name and version, safe error message, timestamp, tool name, and store URL. Remove credentials and customer payloads before you contact Bily support.