Advisor · Document Engineer (and the retired Personal Engineer)
Open the app: Ask the Advisor → (products.documentize.ai) · Open Document Engineer → (products.documentize.ai)
Summary
Three "talk to it" apps share this chapter: Advisor tells you how to do a document job with Documentize, Document Engineer (the page behind the name "Documentize Engineer" in the plan) builds a small .NET program for a document job, and Personal Engineer is retired. All three are chat surfaces: you type a request, not upload a file.
| Advisor | Document Engineer | Personal Engineer | |
|---|---|---|---|
| Status | Live | Live (page /ai-prod/document-engineer) |
Retired in the code I reviewed |
| You give | A question in plain words | A job description in plain words | – |
| You get | A grounded answer: which Documentize tool, API call, CLI plugin or MCP tool to use, plus workflows | A buildable .NET 10 console project as a zip, with README | – |
| Runs your code? | No | No: it is built, never run | – |
| Best for | "What can Documentize do for my project?" | "Write me a utility that merges all PDFs in a folder and adds a TOC" | Use the other two |
Details
Advisor
What it is. A chat that breaks your request into concrete operations (convert, extract, merge, sign, summarise...) and matches each one to a real Documentize capability: an online tool, a REST API call, a CLI plugin, the MCP server, or the self-hosted engine. Multi-step goals become an ordered workflow with links to the live tools. Anything Documentize cannot do is stated plainly, because the answer comes from the product catalog, not from guesswork.
How to use it.
- Open Advisor and describe your project in a sentence or two (up to 2,000 characters per message).
- Choose an answer style: Detailed (default), Concise or Code-first (ready-to-use samples).
- Ask follow-ups in the same chat. Each turn is answered fresh from the catalog, so restate the key fact if you change topic.
- Download the chat transcript as a PDF if offered.
Good to know.
- The same assistant also appears as a small help box on every app page ("how do I use this app", "why did it fail"); that version is grounded in that page's own help text and is not metered. A third variant answers questions on the documentize.cloud architecture pages for engineers.
- The page's older text mentions uploading a prompt file; the current page is a chat (verify on the live app).
- Your messages go to a language model; do not paste secrets.
Try it. Ask: "I get 200 scanned invoices as photos every week. I need one searchable PDF per supplier with a table of contents." Check that the answer names real apps in a sensible order, and compare with the recipes.
Document Engineer
What it is. A chat on the left and a workbench on the right. A request such as "merge every PDF in a folder and add a table of contents" becomes a complete .NET 10 console project that uses the latest NuGet packages Documentize and Aspose.PDF.FOSS, delivered as a zip with a README.
How to use it.
- Describe the job. Pick a Target OS (Any, Windows, Linux, macOS); it only changes the run commands in the README.
- Read the answer: it lists the files, the packages and whether the build passed.
- Browse the file tree and code preview. Use the Changes tab to compare versions, and Download ZIP.
- Each further prompt changes the latest version and creates the next one (v1, v2...).
What you get. <ProjectName>.zip with the .csproj (pinned package versions), the sources, README.md (what it does, packages, licensing, run commands, what it touches, assumptions) and build.log, plus plan.json.
Trust it this much.
- The project is built (up to 5 fix rounds) but never run. If it never builds, the zip still has the last sources and the README says so. Try it on your own sample before using real files.
- Names from the packages are checked against the real API; unknown ones are repaired and listed in the README.
- If the generated code uses no Documentize or Aspose.PDF.FOSS function, it is still shown with a warning.
- The older page text describes uploading a solution or templates for analysis; the current worker works from your prompt (verify on the live app).
Try it. Ask: "Console app that reads every .pdf in an input folder and writes the page count of each to a CSV." Download the zip, run dotnet build, then run it on a folder with two PDFs.
Personal Engineer
Retired. The worker was removed and its plugin slot is kept only so old queued tasks stay valid. Use Advisor to plan and Document Engineer to build.
Which one when
- Not sure which app solves it → Advisor.
- I know the job and want code → Document Engineer.
- Repository work → Repo Docs, Code Graph, Refactor Assistant.