For developers
Search large documentation – with a link to the right docs page
The answer is somewhere between the API reference, guides and migration notes. Read the documentation once with CraCha and ask directly: How do I configure this? How do these two methods differ? Every answer links the docs pages it comes from – you jump straight to the right place.
100 free credits · No credit card required
Straight to the right page
CraCha searches by meaning and by exact terms such as function or option names. Instead of clicking through the sidebar and search results, you get an answer with links to the docs pages it is based on.
Code samples stay intact
Code blocks from the documentation are kept unchanged while reading, so answers can refer to the documentation’s actual code.
Ask in your language
Plenty of documentation is written in one language only. You can still ask your questions in yours.
Your reference, for good
The knowledge base stays in your account. Up to 25 knowledge bases per account, for example one per framework or library.
Sample questions
Phrasing aids, not recorded product results. Replace the placeholders with your own terms.
- How do I authenticate with the [service] API according to the documentation? Link the relevant pages.
- Which configuration options exist for [feature], and which defaults does the documentation give?
- What is the difference between [method A] and [method B]?
- Which breaking changes does the migration guide list for version [X]?
How to go about it
- Sign up for free. Create an account and confirm your email address. You start with 100 credits, no credit card needed.
- Enter the docs address. Enter the documentation’s start address in the dashboard. Use the sitemap or let CraCha follow linked pages up to five levels deep. Patterns limit reading to the section you need, such as /docs/.
- Let CraCha read. The dashboard shows the progress. As soon as the knowledge base is ready, you can ask.
- Ask and look it up. Ask your question in the chat and open the matching docs page via the source links.
What CraCha can’t do
- Up to 500 pages per run. For very large documentation, stick to the sections you really need.
- Publicly accessible HTML pages only: internal documentation behind a login, private repositories and PDF files are not read.
- CraCha works with the state of its last read. When a new version of the docs comes out, you read it again. Make sure to read the version you work with.
- CraCha doesn’t run code. Code samples in answers are untested and can be incomplete or wrong.
- You use CraCha in the browser; there is no extension for your IDE.
Frequently asked questions
Does it work with documentation in another language?
Yes. The documentation can be in English, German or another language, and you ask in yours. The source links lead to the original pages.
How large can the documentation be?
Up to 500 pages per run, as long as they are reachable and your balance covers them. Every page read costs 1 credit, every answer 5 credits. With the Pro pack (7,500 credits) you can, for example, read 500 pages and then ask 1,400 questions.
Can I read internal or private documentation?
No. CraCha only reads publicly accessible pages. Sections behind a sign-in are not fetched, and you can’t upload files.
Can I rely on the code in the answers?
Not without checking. The answer is based on the linked docs pages but can be incomplete or wrong. Compare code with the documentation and test it before you use it.
Is the knowledge base updated with new releases?
Not automatically. CraCha works with the state of its last read. After the documentation is updated, you read it again; that uses credits again.
More on costs and the process: Costs and FAQ · Guide with sample questions
Try it with the docs you have open right now
Pick a manageable section, for example a guide with 20 pages. With 100 free credits you then still have 16 questions – no credit card.
Start for free