Connect as you

An AI app or tool can sign in as a Fido user through the Fido OAuth server. It then acts with that user's own permissions.

Two ways to authenticate

API keys call the External API at api.fetchfido.ai. OAuth sign-in connects a tool to the Fido MCP connector at mcp.fetchfido.ai. The OAuth access tokens are for the connector. Do not send them to api.fetchfido.ai/v1; that API takes API keys.

When to use it

Use OAuth when a person connects an AI app, such as an assistant that supports MCP connectors, to their own Fido account. The person signs in on a Fido page and approves the connection. The app never sees their password.

For a server that calls the API on its own schedule, such as a QuickBooks sync, use an API key instead.

The OAuth server

The server publishes its settings at a standard discovery address (RFC 8414). Apps that support MCP connectors read these settings themselves. You only need the details below if you build your own client.

ItemAddress
MCP connectorhttps://mcp.fetchfido.ai/mcp
Discovery documenthttps://mcp.fetchfido.ai/.well-known/oauth-authorization-server
Authorizationhttps://mcp.fetchfido.ai/oauth/authorize
Tokenhttps://mcp.fetchfido.ai/oauth/token
Client registrationhttps://mcp.fetchfido.ai/oauth/register

How the sign-in works

  1. Register the client. Send a dynamic client registration request (RFC 7591) to the registration address. Or use an HTTPS URL for your client's metadata document as the client_id.
  2. Send the person to the authorization address with response_type=code, your redirect_uri, and a PKCE code_challenge with code_challenge_method=S256. PKCE is required.
  3. The person signs in on a Fido page with their Fido email and password, or by pasting a connector key from Settings → AI Tools → AI Connectors. They can name the organization to sign in to.
  4. Exchange the code. Send the code and your PKCE code_verifier to the token address with grant_type=authorization_code.
  5. Refresh. Use grant_type=refresh_token to get a new access token.
DetailValue
Grant typesauthorization_code, refresh_token
PKCE methodS256 only
Scopefido
Client authenticationnone (public clients with PKCE), client_secret_post, client_secret_basic
Authorization code lifetime5 minutes
Access token lifetime7 days
Refresh token lifetime90 days. Each refresh token works once; the response includes a new one.

Check the discovery document for the current values. It is the authority if this page and the server ever differ.

What the connection can do

The connection acts as the person who signed in, with that person's role and permissions in Fido. It cannot do more than that person can.