Your API Docs Are Embarrassing You.
Fix It for $99/Month.

Swagger UI (/docs) is free and it’s fine for internal use. But it has three real problems:

1. It goes down when your API goes down. If you’re having an incident, your docs are offline — exactly when your customers need them to debug the integration. 2. It exposes your live backend URL. Every person who reads your docs is hitting your production server. 3. It looks like 2009. That’s not a judgment call. It’s a sales problem. When an enterprise buyer opens your docs and sees Swagger UI, they’re calibrating you as a small shop.

DocoAPI serves docs independently, hides your backend, and looks like you hired a docs team. For $99/month, it’s the cheapest fix to all three problems at once.

Mintlify raised from $150 → $180 → $300/month. That’s a pattern of a VC-backed company raising prices as they chase growth metrics.

DocoAPI is bootstrapped. We’re not trying to 10x ARR in 18 months to justify a Series A. We’re not raising the next round on your back. $99/month is the price because it’s fair — and we won’t change it until we ship something that’s worth more.

Good question. Two answers:

1. If you cancel: Your published docs portal goes offline. But your OpenAPI spec still lives in your FastAPI app — the source of truth is your code, not DocoAPI. You can always regenerate docs from your spec using open-source tools. You don’t lose your data, you just lose the portal.

2. If DocoAPI shuts down: We’re a small bootstrapped company, not a VC-funded rocket ship burning cash. We’re not going to hit the wall without warning. If we ever need to wind down, we’ll give customers 90 days notice and export access to their spec history.

Your content is always in your codebase. DocoAPI is the renderer, not the source of truth.

DocoAPI keeps 20 versions of your spec with one-click rollback. If a bad deploy syncs a broken spec, you roll back to the last working version in seconds from the dashboard.

Sync is SHA-256 deduped — DocoAPI only re-processes when your spec actually changes. No unnecessary reindexing, no thrashing.

The AI search uses pgvector (PostgreSQL’s vector extension) with OpenAI’s text-embedding-3-small model. It’s semantic — not just keyword matching. Type "get user by email" and it finds GET /users/lookup even if that phrase doesn’t appear in the path.

It’s not an LLM chatbot. It’s fast vector similarity search.

The AI semantic search is vector-based (pgvector + OpenAI embeddings) and unlimited — not keyword matching.

Yes. Every project gets one automatically — at {yourproject}.docoapi.com/mcp. No setup on your end. No separate dashboard. Publish your docs, the MCP server is live.

Point Cursor, Claude Code, or Windsurf at that URL and your AI assistant can call your actual API endpoints — not just look up what they do. Real HTTP requests against your real API.

Mintlify ships an MCP server too. Theirs is search-only — it reads your docs and returns text. DocoAPI’s proxies real API calls. That’s the difference between an AI that can explain an endpoint and one that can hit it.

Your API key never touches DocoAPI. You configure auth in your MCP client — the request passes through our proxy to your API and back. We see the call structure. We never see or store your credentials.

$99/month is per workspace. Your whole team works in one workspace. The $99 covers 1 owner seat and 5 projects.

Need more team seats or more projects? Email us at [email protected]. We’ll price it fairly. We don’t have a per-seat pricing trap.

10 minutes is the real number if your FastAPI app is running and accessible. The steps:

1. Sign up (2 min) 2. Create a project, paste your OpenAPI URL or connect GitHub (2 min) 3. Trigger sync — DocoAPI fetches your spec and indexes it (1–2 min) 4. Your docs portal is live at yourproject.docoapi.com (instant after sync)

That’s it. No MDX configuration. No nav tree YAML. No theme tokens.