Unwrapped

Teardown · mintlify

MINTLIFY

MINTLIFY

CategoryDeveloper DocumentationLast round · $45M · 2026Site ↗
  • YC W22
  • Andreessen Horowitz
  • Salesforce Ventures

Customer docs + repo content + LLM APIs + packaged doc platform.

01

Public data / API layer

Customer documentation files
Customer documentation filesYours
GitHub repositories
GitHub repositoriesAPI
OpenAPI specifications
OpenAPI specificationsPublic
Third-party SaaS integrations
Third-party SaaS integrationsAPI

Internal replication score

Easy
0.75

Feasibility of a useful internal substitute built with Claude (or similar), the same data access, and light agent logic — not rebuilding the whole product.

IRS = 0.30·D + 0.25·L + 0.20·O + 0.15·R + 0.10·Sthis record · 75%
  • D

    Data accessibility

    weight 0.300.85
    • 1.0mostly customer-owned / public / standard third-party sources
    • 0.5mixed accessibility
    • 0.0hard-to-access or proprietary source layer
  • L

    LLM substitutability

    weight 0.250.80
    • 1.0mostly retrieve / prompt / cite / summarize / classify / compare
    • 0.5mixed standard + custom behavior
    • 0.0strongly custom model behavior (fine-tunes on proprietary data, etc.)
  • O

    Output simplicity

    weight 0.200.75
    • 1.0straightforward internal work product (memo, list, reply, SQL query)
    • 0.5moderately specialized
    • 0.0highly specialized (e.g. FDA-graded clinical text)
  • R

    Review / risk tolerance

    weight 0.150.70
    • 1.0internal use with human review is acceptable
    • 0.5moderate risk
    • 0.0very low tolerance for error (e.g. external legal filings)
  • S

    Surface complexity

    weight 0.10inverse — higher means less surface dependence0.35
    • 1.0a simple internal shell is enough
    • 0.5polished workflow matters somewhat
    • 0.0product surface / rollout / trust posture is central to value
LabelsEasy ≥ 0.67Medium ≥ 0.34Hard < 0.34

Missing factor rows use heuristics from wrapper scores. Editorial heuristic, not investment advice.

Build it yourself

Recreate the workflow inside your org.

Internal build

Build it yourself

Same GitHub sync + frontier LLM + hosted docs site — loses the polished workflow and agent optimizations.

Internal use only. Replacing them in-market is a different bar than replaying the useful workflow inside your org.

01 · Connectors & flow

Customer documentation files
Customer documentation files
GitHub repositories
GitHub repositories
OpenAPI specifications
OpenAPI specifications
Third-party SaaS integrations
Third-party SaaS integrations

Internal build map

Data in

Connectors
Connectors

Agent layer

Planner
Tools + retrieval
Reasoning model

Logic

LLM API
retrieve
generate
summarize
maintain
optimize for agents
not custom weights

Outputs

Internal search
Answer
Citations

02 · Claude / agent prompt

Paste as the system or developer message in Claude (or your agent runtime). Scroll to read; Copy grabs the full text.

Claude / agent prompt

// Documentation assistant for internal developer docs You are a documentation assistant inside [YOUR_COMPANY]. You help engineers and product teams find answers using ONLY materials in the company's internal documentation repository, GitHub repos, and API specs. ## What you must do 1. Retrieve first: Search the indexed docs and repo before answering. Never fabricate endpoints, parameters, or procedures. 2. Cite rigorously: Every answer must link to the specific doc page, code file, or API spec that supports it. Use markdown links. 3. Surface conflicts: If multiple docs contradict each other, list all versions and flag the conflict for human review. 4. Scope: You answer questions about how to use internal APIs, SDKs, deployment procedures, and architecture. You do not write production code or make configuration changes. ## What you are not You are not a replacement for reading the full documentation. You surface relevant sections and provide context, but engineers must review the primary source before making changes. Internal use only. ## Refusal If a question is about external APIs, third-party products, or tools not documented in the internal repository, say: "I only have access to [YOUR_COMPANY] internal documentation. For external tools, please check the vendor's docs directly." ## Safety Internal posture: answers are sourced from version-controlled documentation. If a doc is outdated or flagged as deprecated, note that in your response and suggest the engineer verify with the owning team.

03 · Result

How do I authenticate with our internal analytics API?
Internal docs repository

Use Bearer token auth. See `/docs/apis/analytics/auth.md` for endpoint and token generation.