Company
Latitude 10, the company
Latitude 10 isn’t raising money yet. It’s looking for a co-founder.
Facts as of 2026-10-23.
What problem does it solve?
An API team buys its reference, its docs, its SDKs and now an MCP server from different vendors.
Each of them reads its own copy of the OpenAPI document, so they drift apart.
Why now?
The Model Context Protocol’s 2026-07-28 revision is stateless.
Every Latitude 10 MCP server speaks it, beside the older versions.
On 2026-10-21, Claude Code’s first request to one of our hosted servers was a 2026-07-28 request.
Speakeasy announced on 2026-09-17 that its SDK generator is AGPL-3.0.
Our bet: Your next million API users won't be human.
What exists today?
Latitude 10 is an API platform: one OpenAPI document becomes a versioned registry, a hosted API reference with an API client, docs for people and AI agents, TypeScript and Python SDKs, and a hosted MCP server. It’s built by Jorge Ortega at October Moon LLC.
- Registry · Our registry API, its latest version and score
- API Reference · The registry API's hosted reference · The same reference, embedded
- API Client · Try it on the registry API, with your project key
- Docs · Our developer docs · The docs' quickstart · llms.txt · llms-full.txt · The reference as Markdown
- SDKs
- MCP server (Agentify) · The docs' MCP server, keyless
Who is it for, and how will we find them?
Who buys: companies that publish an OpenAPI document and want developers and AI agents to use their API.
Where we meet them: the free readiness check, the open-source CLI, the CI Action and the published docs.
What we’ll count: readiness checks run, workspaces created, specs pushed, references published, and upgrades from Free to Pro.
We’ll publish these once they mean something.
How does it make money?
- Free · $0 · Individual developers and small projects
- Pro · $150 a month ($125 a month, billed annually) · Startups and engineering teams
- Business · $600 a month ($500 a month, billed annually) · Growing SaaS companies and larger engineering teams
- Enterprise · Custom · Regulated businesses and complex API estates
- API readiness assessment: $500
- OpenAPI modernisation sprint: from $2,500
- MCP implementation: from $2,500
- SDK generation and CI: from $2,000
- Developer portal: from $5,000
- Directory listing: custom, from $11,000
- Migration and architecture: custom, from $10,000
Billing is through Stripe, monthly or annual, with a free trial.
We sell in the Americas only.
Who else does this?
| Capability | Latitude 10 | Scalar | Mintlify | Speakeasy |
|---|---|---|---|---|
| A docs MCP server | Yes | Yes | Yes | Yes |
| TypeScript and Python SDKs | Yes | Yes | No | Yes |
| Published prices | Yes | Yes | Yes | Yes |
Checked on the vendors’ own pages on 2026-10-23. Tell us if something changed.
What’s defensible, and what isn’t yet?
Defensible today
- Near-zero marginal cost: every module runs on one Cloudflare Worker inside its included usage, the heavy work happens in the customer’s browser or CI, and per-customer costs are capped.
- Generated SDK code is under the MIT licence.
- Speakeasy’s generator is AGPL-3.0.
- One source of truth: one OpenAPI document feeds every output.
- Agent-first features that already work: MCP sign-in through your own identity provider, a docs MCP server, llms.txt, and MCP 2026-07-28.
- Pace: what shipped, and when.
- 2026-05-09: The site’s first commit
- 2026-10-19: The API platform direction: plans and features data
- 2026-10-20: Workspace; registry with breaking-change diff; hosted API reference; hosted MCP; hosted docs
- 2026-10-21: MCP sign-in through your own identity provider; MCP 2026-07-28; API client; TypeScript SDKs; billing; Pro launched
- 2026-10-22: SSO, roles, audit log; Business launched; Enterprise launched; shared collections; Python SDKs; observability
- 2026-10-23: Latitude 10 on its own platform; the site rebuilt as a platform
Not yet
- No network effects.
- No usage data yet.
- No brand yet.
- No switching costs yet.
What does it cost to run?
One Cloudflare Worker serves the site, the APIs and every hosted surface.
Data lives in one D1 database and private R2 storage.
Error tracking and uptime checks run on free plans, and logs come with the Worker.
Stripe’s fees come only with a payment.
The support chat’s model spend is capped.
Where are we?
Pro launched on 2026-10-21; Business and Enterprise on 2026-10-22.
Free to start; Pro is $150 a month.
Who are we looking for?
A commercial co-founder, to complement an engineer founder: someone who has sold developer tools or API products to engineering leaders.
What they’d own
- Sales to API-first companies in the Americas
- Developer relations, and the community around the open-source rules
- Pricing and packaging
- And, later, the raise
We’ll talk about terms in person.
What are the risks?
- Infrastructure. The platform runs on Cloudflare (Workers, D1, R2); a Cloudflare outage takes it down. Done about it: uptime checks on the public pages, and a public status page.
- Third-party services. Payments depend on Stripe, and sign-in on GitHub and email delivery. Done about it: emailed links work without GitHub, and every Stripe event is re-read from Stripe before a plan changes.
- Security. A breach would cost customers’ trust. Done about it: sealed credentials, scrubbed telemetry and an append-only audit log.
- Changing standards. MCP and OpenAPI keep changing. Done about it: every MCP server speaks the 2026-07-28 revision beside the older versions.
- Competition. The market for API tools is competitive, with established, funded vendors. Done about it: one OpenAPI document feeds every module, SDK output is MIT, and there’s a free tier.