Authentication

Every call carries an OAuth 2.1 access token from your Lemobb sign-in. Claude and ChatGPT get one for you; scripts get one with the authorization code flow and PKCE.

Your Lemobb sign-in

Your concierge creates your sign-in for the email you used at checkout. You get an email with a temporary password and choose your own the first time you sign in. You can turn on an authenticator app (TOTP) for two-step sign-in.

The sign-in page is hosted by Amazon Cognito for Lemobb. We never see your password.

Clients

Our sign-in service doesn't support automatic client registration, so each platform has a fixed public client ID (no secret; PKCE protects the exchange).

PlatformClient IDRedirect URI
Claude76fl5894clmv5ssmj0r3lqkrm9https://claude.ai/api/mcp/auth_callback
ChatGPT5mkldits49gpk1e5mf1q0rmu9jhttps://chatgpt.com/connector/oauth/… (per app)
Scripts, Claude Code, MCP Inspector40m7get61rp6hi7k8vmos74tm2http://localhost:8765/callback

Scopes

ScopeAllows
project:readSee your app's progress, dates and the materials checklist
materials:writeSend materials (text answers and files) and notes to your concierge
billing:readGet the link to your billing portal

In requests and tokens, each scope carries the address of the resource it is for: https://api.lemobb.com/v1/ for the REST API (for example https://api.lemobb.com/v1/project:read) and https://api.lemobb.com/mcp/ for the MCP endpoint. Claude and ChatGPT request the MCP scopes for you.

Tokens

Access tokens last 1 hour; refresh tokens last 30 days.

Tokens from the Claude and ChatGPT clients only work on the MCP endpoint (https://api.lemobb.com/mcp). Use the scripts client for the REST API.

Get a token for a script

  1. Create a PKCE verifier and challenge:
    VERIFIER=$(openssl rand -base64 48 | tr -d '=+/\n' | cut -c1-64)
    CHALLENGE=$(printf %s "$VERIFIER" | openssl dgst -binary -sha256 | openssl base64 | tr '+/' '-_' | tr -d '=\n')
  2. Open the sign-in page in your browser, sign in and allow. You land on the redirect URI with ?code=… in the address bar (nothing needs to run there; copy the code).
    open "https://lemobb.auth.us-east-1.amazoncognito.com/oauth2/authorize?response_type=code&client_id=40m7get61rp6hi7k8vmos74tm2&redirect_uri=http%3A%2F%2Flocalhost%3A8765%2Fcallback&scope=https%3A%2F%2Fapi.lemobb.com%2Fv1%2Fproject%3Aread%20https%3A%2F%2Fapi.lemobb.com%2Fv1%2Fmaterials%3Awrite%20https%3A%2F%2Fapi.lemobb.com%2Fv1%2Fbilling%3Aread&code_challenge=$CHALLENGE&code_challenge_method=S256"
  3. Exchange the code for tokens:
    curl -X POST https://lemobb.auth.us-east-1.amazoncognito.com/oauth2/token \
      -d grant_type=authorization_code -d client_id=40m7get61rp6hi7k8vmos74tm2 \
      -d redirect_uri=http://localhost:8765/callback -d code="$CODE" -d code_verifier="$VERIFIER"
  4. Call the API with the access_token. When it expires, use the refresh_token:
    curl https://api.lemobb.com/v1/project -H "Authorization: Bearer $LEMOBB_TOKEN"
    
    curl -X POST https://lemobb.auth.us-east-1.amazoncognito.com/oauth2/token \
      -d grant_type=refresh_token -d client_id=40m7get61rp6hi7k8vmos74tm2 -d refresh_token="$REFRESH_TOKEN"

Discovery (for MCP clients)

MCP clients find everything from the protected resource metadata. It points to our authorization server metadata, whose endpoints are on the sign-in domain.

curl -i -X POST https://api.lemobb.com/mcp
HTTP/2 401
www-authenticate: Bearer
EndpointPurpose
https://api.lemobb.com/.well-known/oauth-protected-resource/mcpProtected resource metadata (RFC 9728)
https://api.lemobb.com/.well-known/oauth-authorization-serverAuthorization server metadata (RFC 8414)
https://lemobb.auth.us-east-1.amazoncognito.com/oauth2/authorizeSign-in and consent (authorization code with PKCE)
https://lemobb.auth.us-east-1.amazoncognito.com/oauth2/tokenCode exchange and refresh
https://lemobb.auth.us-east-1.amazoncognito.com/oauth2/revokeRevoke a refresh token (RFC 7009)

Rate limits

Each user can make 120 requests per minute. Above that you get 429 rate_limited with a Retry-After header in seconds.

Upload URLs: 30 per hour per project. Notes: 20 per day per project.

Authentication errors

A missing, invalid or expired token gets 401, and a token without the scope of the route gets 403, both from API Gateway with {"message": "Unauthorized"} or {"message": "Forbidden"}. Other errors come from the API in the documented error shape.

Disconnect

Remove the connector in Claude or ChatGPT to stop using it, and revoke a script's refresh token at the revoke endpoint. To sign out everywhere right away, email support@lemobb.com.