SDKs & Tools
Build with Gemini using official SDKs and developer tools. The Gemini Developer Platform repository also brings together an MCP server, API samples, and agent skills.
TypeScript SDK
The official TypeScript SDK for the Gemini API is published as
@gemini-markets/sdk. It has two entry points — /server for Node.js, Bun, and
Deno, and /browser for frontend apps and edge runtimes.
Code
- Quickstart — install, create a client, make your first request
- Authentication — HMAC, OAuth, and browser PKCE
- WebSocket — real-time streams and live order books
- Error handling — error classes, diagnostics, and safe logging
- Patterns & recipes — pagination, timeouts, heartbeat, and advanced configuration
- API Reference — all 106 operations across 10 REST namespaces, with code examples
- WebSocket Reference — streams, methods, and wire format
- Deep dives — order book reconstruction, RFQ, data types, request validation, sessions, transport
Developer Platform Tools
These tools are open source and work with the APIs documented here. Follow the setup instructions in the linked repository before using them with production credentials.
| Tool | What it will help you do |
|---|---|
| MCP server | Connect Claude, ChatGPT, and other MCP clients to Gemini API tools. It includes public market-data tools and authenticated tools for orders, funds, accounts, margin, and staking. |
| API samples | Run REST and WebSocket examples in TypeScript, Python, and Go. The samples include public and authenticated API usage. |
| Agent skills | Add Gemini-focused skills to Claude Code, including an integration guide and terminal candlestick charts. |
See the developer-platform README for installation instructions, configuration, and examples. Use demo environment credentials when testing.
API specifications
Inspect machine-readable contracts and generate data models or client scaffolding through the canonical API Specifications catalog. Generic generated clients do not implement Gemini's authenticated signing transport: private Prediction Markets requests encode the logical request payload in X-GEMINI-PAYLOAD and send an empty HTTP body. Use generated code alongside the API Reference for authentication, permissions, and product-specific behavior that schemas cannot fully express.