# agent cache vs content.dev: tool vs diy pipeline

> content.dev is an open-source toolkit for building docs extraction pipelines. agent cache is a working tool. same extraction, different effort. here's why.

content.dev is an open-source project that helps developers build documentation extraction pipelines. it's a toolkit. libraries, scripts, configuration options.

agent cache is a tool that downloads docs and gives you a zip file.

both extract documentation. content.dev makes you build the tool. agent cache is the tool already built. this is the "build vs buy" debate, except "buy" is free.

## content.dev supplies the extraction pieces

content.dev is a collection of open-source packages for extracting documents. it provides parsers, converters, chunkers, and extraction recipes. you configure it. run it. maintain it. troubleshoot when sites change their layout.

it's customizable. you can write custom extractors for frameworks that aren't supported yet. you can tweak parameters. you can integrate it into your own toolchain.

it's free (as in open source). you self-host. you manage dependencies. you handle updates.

**but it's not a finished product.** it's a toolkit for building one.

## agent cache has the pipeline already built

agent cache is a working product. paste a url. get a zip. that's the whole workflow.

it already handles:
- framework detection (mintlify, docusaurus, gitbook, etc.)
- acquisition ladder (llms.txt → github → direct .md → html → fallback)
- navigation extraction
- content cleaning per framework
- meta.yaml generation
- zip packaging

you don't configure any of this. it just works.

**and it's free.**

## building the pipeline takes more than running it

content.dev gives you the ingredients. agent cache gives you the meal.

with content.dev:
1. clone the repo
2. install dependencies
3. configure extraction rules
4. write custom extractors for unsupported frameworks
5. handle edge cases (dynamic rendering, bot protection, layout changes)
6. debug when a site breaks
7. update when upstream changes

with agent cache:
1. paste url
2. wait
3. download zip

if you're a developer with time and specific needs, content.dev is great. you get full control.

if you just want docs and don't want to build a pipeline, agent cache is obvious.

## content.dev gives you control over each step

**full control.** you own every step. you can modify extraction logic. add custom cleaning rules. integrate with your existing toolchain. 

**no dependency on someone else's uptime.** content.dev runs on your infrastructure. agent cache's web app depends on a web service. (though agent cache's cli will be local-only when it ships.)

**learning.** building with content.dev teaches you how docs extraction actually works. that's valuable if you plan to build more tools on top of it.

**internal integration.** if you need to pipe docs extraction into an internal pipeline, deploy it as part of a larger system, content.dev's modular approach fits better.

## agent cache handles setup and framework quirks

**zero setup.** no dependencies. no configuration. no maintenance. no updates to apply when a framework changes. it just works.

**tested.** i've extracted 100+ sites with agent cache. success rate is 88%. those 12 failures taught me what breaks. that knowledge is baked into the product. with content.dev, you learn those lessons yourself.

**framework-specific intelligence.** agent cache knows mintlify's sidebar structure, docusaurus's category system, fumadocs's version tabs. content.dev has generic extractors. you write the framework-specific logic.

**meta.yaml out of the box.** agent cache generates structured metadata: keywords, intent triggers, ecosystem links. with content.dev, you build that yourself.

**free.** both are free. but content.dev costs developer time. agent cache costs zero time after extraction.

## content.dev for integration, agent cache for a ready zip

content.dev is the right choice if you're building a docs extraction platform or integration pipeline. it's a toolkit for builders.

agent cache is the right choice if you just want documentation extracted, formatted, and ready to use. it's a tool for users.

use content.dev when you need to integrate extraction into a larger system and can afford the setup time.

use agent cache when you want to spend zero time on tooling and get clean docs immediately.

---

**related:**
- [agent cache vs context7](/compare/context7)
- [agent cache vs firecrawl](/compare/firecrawl)
- [how agent cache chooses an extraction method](/blog/acquisition-ladder)