Glotto documentation
Everything you need to turn an API spec into SDKs, docs, and an MCP server. Get started with your first glotto generate.
Every SDK, same error model
import { ApiError } from 'glotto-sdk';
try {
// any client call
} catch (err) {
if (err instanceof ApiError) {
console.error(err.status, err.toString());
console.error(err.error); // undefined when the documented model cannot be decoded
console.error(err.rawBody); // original response text
}
}regenerated + byte-diffed in CI d05b0dfc8e97
Get started
Concepts
- The Glotto IR
- The pipeline
- Drift detection
- Breaking-change detection
- Idempotency keys
- The verification report
- Endpoint migration
Guides
- The MCP server
- The generated docs site
- Deployment & single-tenant
- Multi-VCS release flow
- Custom code
- Migrate from Stainless
- How Glotto compares
- Connect a VCS provider
- The generated CLI
- Migrate from Fern
- The API-surface graph
- Migrate from Speakeasy
- The generated Terraform provider
- The published spec repo
Using the SDKs
- Authentication
- Retries & timeouts
- Pagination
- Errors
- Idempotency
- Streaming
- Webhooks
- Polling
- Telemetry hooks
- Agent primitives
- Forward compatibility
- File uploads & downloads
Languages
Reference
- CLI reference
- glotto.yml reference
- glotto.yml client behavior
- glotto.yml model shaping
- glotto.yml API surface
- glotto.yml project settings
- Diagnostics reference
- Diagnostics configuration
- Migration diagnostics
- Fatal diagnostics
- SDK generation diagnostics
- Reserved model names
- Runtime diagnostics
- Transforms reference