ChudGPT Gambit / Developers

Build with Gambit

API v1 · Preview

Use Gambit's chess and assistant models from your own app. Gambit preview.

NO API KEY REQUIRED

Your app. Gambit's next move.

Send a chess position, get a legal neural move and the updated board. Ask the assistant a question with board context. Start with a request—no signup or API key.

Download the OpenAPI contract →

Try a keyless request

This asks Gambit to move from the starting position. Pass fen to use any valid standard chess position.

Ask the assistant

Post the current board and a question. Neural answers are generated by the separately trained, from-scratch language model.

The current neural checkpoint uses this question and board only. Conversation memory still needs training. Choose "mode":"coach" for verified rules and authored lessons.

Keyless endpoints

GET/api/gambit/v1/modelsAvailable models, readiness and source.
GET/api/gambit/v1/lessonsVerified teaching positions.
POST/api/gambit/v1/chess/moveFEN → legal move, SAN and updated FEN. No stored game.
POST/api/gambit/v1/analysisFEN → neural candidates and searched variation.
POST/api/gambit/v1/assistant/messagesQuestion + FEN → neural answer or verified coaching.

Simple limits, honest results

  • Keyless API: 30 requests and 6 model calls per minute per client IP.
  • Up to 64 search nodes, two seconds per search and 180 reply tokens.
  • Request IDs and structured errors; 429 includes Retry-After.
  • Chess weights are still untrained. Legal moves do not establish playing strength.
  • Neural answers are experimental. Material is a piece-count heuristic.

The browser game has its own larger budget, so ordinary play does not consume the keyless API allowance.

Keep your own board

The keyless API is stateless: save the returned FEN in your app and send it with the next call. FEN alone does not retain repetition history.

For server-saved games, obtain an expiring guest session from POST /api/gambit/v1/sessions. This requires no developer API key. Use the returned session token to keep those games private.

Saved game routes use versions to prevent conflicting moves. Read the full schemas for moves, replay, actions and PGN export.

Optional application keys and saved games

Application keys are optional. Create one locally for a named app, scoped access, revocation and server-saved game ownership:

.venv\Scripts\python.exe -m public_draft.keys create --name my-app --output-file config/my-app.key

Supply Authorization: Bearer YOUR_KEY only when using that key. Keep it on your server. The public preview has no training or administration endpoints.

Saved game endpoints: /api/gambit/v1/games, /api/gambit/v1/games/{id}/moves, /ai-moves, /actions, /pgn. Application keys use 60 requests / 10 inference calls per minute. Browser sessions use 600 / 120. Guest creation has its own limit.