Deep Research reports as PDF in Vamo

Every finished Deep Research report, for a developer or for a repository, downloads as a PDF. Vamo renders it from the same page you read in the app, so what you send to a hiring manager or a client is what you saw.

What the PDF is

The PDF is made on Vamo's side. A browser in Vamo's infrastructure opens the report page, with the same components the app uses, and prints it to PDF. Nothing depends on the browser you are using or its print settings.

A developer report keeps everything the screen shows: the profile header, the signal sections, the reads, notable followers and the contribution garden. A repository report keeps its builders, its audience and its momentum sections. Cards are kept whole across page breaks where they fit on one page.

Vamo keeps a rendered copy for a short while, so asking for the same report again is quick. A refreshed report renders fresh.

Your logo on the header

Each PDF opens with a header in the style of the Vamo app. When your account has a report logo, the header carries it. You set the logo in Deep Research settings, the same place you manage the GitHub accounts research runs through. PNG and SVG both work.

Getting a PDF through the API

Programs and agents can get the same PDF with an API key. There are three ways, and they all return the same document:

• Ask the report's PDF route for the bytes directly.
• Ask for a short-lived download link. This suits an agent that hands the file to a person, since the person opens the link and the key never leaves the program.
• Read the report with Accept: application/pdf, and the report read answers with the PDF instead of JSON.

The API reference lists the routes and their options.