Use your AI Pass account from any OpenAI or Anthropic client.

thaipass is a proxy with OpenAI-compatible and Anthropic-compatible endpoints in front of AI Pass. The models your account sees in the web UI then work in Claude Code, Codex, T3 Code, Cursor, and the software development kits (SDKs). Each request sends your own session cookie, and the proxy stores no credential.

• Three protocols: /v1/chat/completions, /v1/responses, and /v1/messages
• Live catalog: every model your account can reach, checked on each request
• Credits in every reply: the balance before and after, plus a dollar estimate
• Media: image, video, and music generation
• Learning points: earns the monthly learning management system (LMS) points from the dashboard, a command, or a scheduler
• AI SDK provider: the thaipass package calls AI Pass with no HTTP hop

Clone the repo and start the proxy on http://127.0.0.1:3001:

bun install
bun run start

Log in to AI Pass and copy the Cookie header from any request to de.aipass.net. It must contain __Secure-ai_passport_auth.session_token. The dashboard shows each click and accepts the header, the token alone, or a Copy as cURL.

Send the cookie as the API key:

curl -sN localhost:3001/v1/chat/completions \
  -H 'content-type: application/json' \
  -H "authorization: Bearer $AIPASS_COOKIE" \
  -d '{"model":"claude-sonnet-5@azure",
       "messages":[{"role":"user","content":"hi"}]}'

gemini-3.5-flash-lite is free. GET /v1/models lists the rest.

Every client takes a base URL, the cookie as its key, and a model ID. The dashboard’s Integrations page writes each setup out with your values filled in:

T3 Code needs a Codex home of its own and can show your credits in its Limits view. See T3 Code.

A deployment with THAIPASS_TOKEN_KEY also issues scoped tp_v1_… tokens, so an app never holds the raw cookie. Run bun run login to get one.

The guide covers each client, login with thaipass, attachments, media, tool calling, credits, the LMS learner, deployment to Vercel, and troubleshooting by status code. A running proxy serves its OpenAPI reference at /.

The repo is a Bun workspace run by Turborepo:

• apps/proxy: the server and the LMS command
• apps/dashboard: the Next.js dashboard
• packages/core: the AI Pass protocol shared by the server and the provider
• packages/thaipass: the AI SDK provider published to npm

Run bun run dev for watch mode, bun run test for the suites, and bun run check before you commit.

thaipass is a reverse-engineered adapter over an undocumented private API. Keep it to one account you own, and don’t run it as a service for other people. That’s a request, not a licence term.

MIT