# Latitude 10 docs > Latitude 10 turns one OpenAPI document into a versioned registry, a hosted reference with an API client, docs, TypeScript and Python SDKs, and an MCP server for AI agents. ## Get started - [Overview](https://docs.latitude10.tech/index.md): How one OpenAPI document becomes a registry, a hosted reference, an API client, docs, SDKs and an MCP server on Latitude 10. - [Quickstart](https://docs.latitude10.tech/quickstart.md): Sign in, create a project, push an OpenAPI document with curl, read its score and publish its reference. - [Concepts](https://docs.latitude10.tech/get-started/concepts.md): Accounts, workspaces and their slugs, members, seats and invitations, projects, versions and the sample document. - [Keys and tokens](https://docs.latitude10.tech/get-started/keys-and-tokens.md): Every Latitude 10 key and token prefix, who makes each one, where it goes, how it's stored and how to revoke it. - [Plans and limits](https://docs.latitude10.tech/get-started/plans-and-limits.md): What each plan costs, and every limit of the workspace, registry, reference, API client, docs, SDKs, MCP servers and enterprise features. ## Registry - [Registry](https://docs.latitude10.tech/registry.md): The registry keeps every version of your OpenAPI document, scores each one for AI agents and lists what changed since the last. - [Push a version](https://docs.latitude10.tech/registry/push.md): Push your OpenAPI document to the registry with POST /versions, with its label and Git commit, and what each error means. - [The GitHub Action](https://docs.latitude10.tech/registry/github-action.md): Score your OpenAPI document, fail on breaking changes and push versions from GitHub Actions, or push with one curl step instead. - [Readiness rules](https://docs.latitude10.tech/registry/readiness-rules.md): The rules that score every pushed OpenAPI document from 0 to 100 for AI agents, with what each checks, its weight and how to fix it. - [Breaking changes](https://docs.latitude10.tech/registry/breaking-changes.md): Every kind of change the registry finds between two versions of your OpenAPI document, marked breaking, warning or information. - [Fixes](https://docs.latitude10.tech/registry/fixes.md): Rules-only fixes for your OpenAPI document as JSON Patch, from POST /fixes or the GitHub Action, on the paid plans. - [Versions](https://docs.latitude10.tech/registry/versions.md): How many versions the registry keeps, what happens after a downgrade, and how to read a version's source, report and diff. ## Reference - [Hosted API reference](https://docs.latitude10.tech/api-reference.md): An interactive API reference made from a registry version, served by Latitude 10 or embedded on your own site. - [Publishing the reference](https://docs.latitude10.tech/api-reference/publishing.md): Publish and unpublish a hosted API reference, let readers download the OpenAPI file, hide it from search engines, and read older versions. - [Embedding the reference](https://docs.latitude10.tech/api-reference/embed.md): Put your hosted API reference inside your own site with an iframe, choose its theme, and what the embed allows. - [Markdown in descriptions](https://docs.latitude10.tech/api-reference/markdown.md): What the descriptions in your OpenAPI document may use on the hosted reference, and what's shown as plain text instead. - [Caching and security](https://docs.latitude10.tech/api-reference/caching-and-security.md): How hosted reference pages are cached and keyed by version, the daily cap on uncached renders, and the security headers each page sends. ## API client - [API client](https://docs.latitude10.tech/api-client.md): Try it, the API client in every hosted reference, sends real requests to your API from the reader's browser or through a proxy. - [Direct and proxy](https://docs.latitude10.tech/api-client/direct-and-proxy.md): What Try it sends directly from the reader's browser, what the Pro proxy sends for APIs without CORS, and the limits and errors of each. - [CORS for Try it](https://docs.latitude10.tech/api-client/cors.md): The CORS headers your API sends so Try it can call it straight from the reader's browser, and why each one is needed. - [Verified hosts](https://docs.latitude10.tech/api-client/verified-hosts.md): Prove you control your API's host so the Try it proxy may call it, with a file or a DNS TXT record, and how often it's checked again. - [Shared collections](https://docs.latitude10.tech/api-client/collections.md): Save Try it requests in collections your team shares, publish them to readers as Examples, and what happens past your plan's limits. - [Import and export](https://docs.latitude10.tech/api-client/import-export.md): Export a shared collection as latitude10.collection.json or for Postman, and import our own format back, with what an import refuses. - [Secrets](https://docs.latitude10.tech/api-client/secrets.md): Why a saved Try it request never holds a credential, what the secret check refuses, and the error it answers with. ## MCP - [Hosted MCP](https://docs.latitude10.tech/hosted-mcp.md): A registry version served as an MCP server at a URL, where each tool call is one request to your API with your sealed credential. - [Set up hosted MCP](https://docs.latitude10.tech/hosted-mcp/setup.md): Set up a project's hosted MCP server, from its base URL and host proof to its credential, tools, keys, version and switch. - [Refused hosts](https://docs.latitude10.tech/hosted-mcp/refused-hosts.md): The base URLs a hosted MCP server refuses to call, the rule behind each one, and the exact message the setup page shows. - [Tool calls](https://docs.latitude10.tech/hosted-mcp/tool-calls.md): How a hosted MCP tool is named, how its arguments are checked, and exactly what the one request to your API sends and gets back. - [Hosted MCP errors](https://docs.latitude10.tech/hosted-mcp/errors.md): Every message an agent can get from a hosted MCP server, with its HTTP status and JSON-RPC code, and what each one means. - [Keys and allow lists](https://docs.latitude10.tech/hosted-mcp/keys-and-allow-lists.md): MCP keys for agents, which tools are on, the cap on tools, and allow lists that give a key fewer tools, on Pro and up. - [Agent analytics](https://docs.latitude10.tech/hosted-mcp/analytics.md): Daily totals of a hosted MCP server's tool calls by tool and by client, how each client is labelled, and what is never stored. - [Protocol versions](https://docs.latitude10.tech/hosted-mcp/protocol-versions.md): The MCP protocol versions every Latitude 10 MCP endpoint serves, stateless, from the 2026-07-28 revision back to the legacy initialize ones. - [OAuth sign-in](https://docs.latitude10.tech/hosted-mcp/oauth.md): Let people sign in to a hosted MCP server through your own identity provider, on Pro and up, with per-server tokens and claim rules. ## Docs - [Docs hosting](https://docs.latitude10.tech/docs-hosting.md): Write guides in Markdown in your repository, push them from CI, and serve them beside your API reference with files for agents. - [The docs folder](https://docs.latitude10.tech/docs-hosting/bundle.md): How to lay out a docs folder, every latitude10.docs.json key and front matter field, page addresses, reserved paths and refusals. - [Markdown in guides](https://docs.latitude10.tech/docs-hosting/markdown.md): The Markdown a docs page may use, what it can't, and how to write within those limits so every page renders as you meant. - [Push your docs](https://docs.latitude10.tech/docs-hosting/push.md): Push a docs folder from CI with tar and curl, to production, as a version or as a branch preview, and read what the push answers. - [Files for agents](https://docs.latitude10.tech/docs-hosting/agent-files.md): The files every docs site gives AI agents with nothing to set up, from llms.txt and Markdown pages to its own MCP server. - [Custom domains](https://docs.latitude10.tech/docs-hosting/custom-domains.md): Serve a docs site on your own subdomain with one CNAME record, on Pro and up, and what happens to a domain after a downgrade. - [Docs traffic](https://docs.latitude10.tech/docs-hosting/traffic.md): Daily counts of who reads a docs site, people and each family of AI agents, by what they read, and what is never stored. ## SDKs - [SDKs](https://docs.latitude10.tech/sdks.md): TypeScript and Python SDK packages generated from a registry version and your latitude10.sdk.json, published from your CI under MIT. - [The SDK config](https://docs.latitude10.tech/sdks/config.md): Every field of latitude10.sdk.json, what each one sets in the generated packages, and how the file is checked. - [The TypeScript package](https://docs.latitude10.tech/sdks/typescript.md): What a generated TypeScript SDK holds, where it runs, and how it handles auth, retries, timeouts, errors and pagination. - [The Python package](https://docs.latitude10.tech/sdks/python.md): What a generated Python SDK holds, its sync and async clients, its types, and how it handles retries, errors and responses. - [The publishing workflow](https://docs.latitude10.tech/sdks/workflow.md): The GitHub Actions workflow that pushes your spec, generates your SDKs and publishes them with your own npm and PyPI trust. - [SDK versioning](https://docs.latitude10.tech/sdks/versioning.md): How each generated SDK package's version follows the registry's breaking-change diff and its exported names, and how previews are versioned. - [OpenAPI extensions for SDKs](https://docs.latitude10.tech/sdks/openapi-extensions.md): The two OpenAPI extensions the SDK generator reads, for method names, grouping and pagination, and how it detects paging on its own. - [What the SDKs cover](https://docs.latitude10.tech/sdks/coverage.md): What the SDK generator leaves out of a package or types as unknown, the warnings it writes in GENERATION.md, and the operations cap. ## Enterprise - [Enterprise](https://docs.latitude10.tech/enterprise.md): SSO over OpenID Connect, roles, the audit log and the SLA, for teams that need to control and prove who does what in a workspace. - [SSO](https://docs.latitude10.tech/enterprise/sso.md): Sign in to a Latitude 10 workspace through your identity provider over OpenID Connect, and require it for every member. - [Email domains](https://docs.latitude10.tech/enterprise/domains.md): Prove your company's email domains with a DNS TXT record, so your identity provider can sign in addresses there, and how proofs are rechecked. - [Roles](https://docs.latitude10.tech/enterprise/roles.md): What owners, admins, editors and viewers can each do in a Latitude 10 workspace, and what the API and pages answer when a role may not. - [Break-glass](https://docs.latitude10.tech/enterprise/break-glass.md): How a workspace's owners still get in when SSO is required and the identity provider is down, and how every such entry is recorded. - [Audit log](https://docs.latitude10.tech/enterprise/audit-log.md): Every action the audit log records, the detail each one carries, and how to export the log as CSV or JSON Lines with a checksum. ## Changelog - [Changelog](https://docs.latitude10.tech/changelog.md): What changed on the Latitude 10 platform that customers can see, day by day, with the pull request behind each change. ## Registry API - [Registry API](https://docs.latitude10.tech/registry-api.md): What the registry API does, its base URL, how a project key authenticates it and how its quotas answer. - [Errors](https://docs.latitude10.tech/registry-api/errors.md): The registry API's error body, each HTTP status it answers with, and what to do about each one. ## Registry API - [Latitude 10 Registry API](https://docs.latitude10.tech/reference.md): every operation, its parameters and responses