Flaim

Support

Flaim is built and maintained by one person. If something is broken or confusing, tell me and I will fix it.

Before You Email

Most problems clear up with one of these. Try them in this order.

  1. Check Your Leagues. Open Your Leagues and make sure the league is listed. If it isn't, choose Sync all. Your AI can only see leagues that show up there.
  2. Use the same Flaim account. Your AI app has to be signed in to the same Flaim account you use on flaim.app. If you made two accounts with different email addresses, your leagues are only in the one where you connected them.
  3. Try again or refresh. ESPN, Yahoo, and Sleeper sometimes respond slowly. Wait a minute and ask again, or ask your AI to refresh your leagues.
  4. Reconnect your AI app. Disconnect Flaim Fantasy in your AI app, connect it again, and approve access. Steps for each app are on the AI apps page.
  5. Start a new chat. An older chat can keep using league details from before your change.

Platform Fixes

  • ESPN: open ESPN Fantasy in Chrome on your computer and make sure you're signed in, then open the Flaim extension and sync again. If it still fails, open the info panel in the extension, choose Copy support info, and paste it into your email. More help is on the ESPN page.
  • Yahoo: on Your Leagues, choose Reconnect Yahoo and sign in on Yahoo's page again, then choose Sync leagues. More help is on the Yahoo page.
  • Sleeper: make sure you entered your Sleeper username, not your display name. They can be different. Then choose Refresh under Sleeper on Your Leagues. More help is on the Sleeper page.
  • A league you hid or archived: it moves to Hidden or Inactive at the bottom of Your Leagues. Open that list and use the restore button on the league to show it to your AI again.

Get in Touch

Email support@flaim.app. Include which platform you use (ESPN, Yahoo, or Sleeper), which AI app you use, what you were trying to do, and the exact error message if there was one. Screenshots help. Never send a password.

For privacy questions or a request about your data, email privacy@flaim.app.

Connecting Your Own App (Unofficial)

This route is unsupported. There's no client program and no support promise, and it can change. If you're writing your own app or script to read your own Flaim account, here is how it works today. Most people should use the custom connector setup instead.

  • Endpoints: the MCP server is https://api.flaim.app/mcp, and the OAuth metadata is at https://api.flaim.app/.well-known/oauth-authorization-server.
  • Register: use dynamic client registration at the registration_endpoint listed there. Register as a public client with token_endpoint_auth_method set to none.
  • Sign in: use the authorization code flow with PKCE. A code challenge is required, and only S256 is accepted. Scopes are mcp:read (the default) and mcp:write, which you only need for refresh_leagues and which includes read access. To ask for both, send one space-separated scope value, not two scope parameters.
  • Redirect URI: use plain http:// on 127.0.0.1, localhost, or [::1], with any port and any path and no query string or fragment. For example, http://127.0.0.1:7778/callback. https:// loopback callbacks are rejected. Other callbacks work only for a short list of AI apps Flaim already supports (ChatGPT, Claude, Perplexity, Gemini, Grok, Muse, Cursor, VS Code for the web, and Littlebird). There's no way to register your own hosted callback or custom URL scheme, and no wildcard rule.
  • Tokens: access tokens last one hour. Each refresh returns a new refresh token and the old one stops working right away, so save the new one every time. A refresh token expires if it goes unused for a year.
  • A hosted app: if your app runs on a server and only reads your own account, sign in once from your own computer with a loopback redirect, save the refresh token in storage your server can write to, and exchange it for access tokens from there. Replace the stored token with the new one after every refresh. A fixed environment variable stops working after the first refresh.
  • Rate limit: 60 requests per minute per Flaim account. Over that, Flaim returns HTTP 429 with Retry-After: 60. Setup requests such as initialize and tools/list don't count.