Questions about Vitae

What Vitae is

Your CV stays yours, with the same career facts in Norwegian and English.

For a candidate applying in two languages, Vitae keeps one career story true in both CV editions, with the facts and files still yours. You and your AI add roles together, check dates and structure, recover earlier entries and make typeset PDFs. You choose publication and can export JSON Resume data.

What people use it for

Keep my Norwegian and English CV true to the same career.

Yes — that is what Vitae is built for. A role is added to two languages in one step, and it is refused if the dates would differ between them. `parity_check` tells you where one edition has something the other lacks; wording and titles may differ, because that is what a translation is.

Ask your AI
Add my new job to both CV editions; check their facts match.
What it does
  • cv_get
  • entry_add_pair
  • parity_check
What you get
Both editions updated together, with structural differences reported.
Turn my career notes into a CV I can send.

Yes. Your assistant puts your supplied career facts into structured fields, and cv_render typesets an edition. cv_pdf_link returns your complete owner download, which requires your session. If you choose to publish, the public version excludes street address and postcode but includes email, phone and city.

Ask your AI
Make a CV from my career notes and give me the PDF.
What it does
  • cv_create
  • basics_set
  • entry_add
  • cv_render
  • cv_pdf_link
What you get
Structured career facts and a typeset owner PDF.
Bring back one job without undoing my later edits.

Yes. Inspect the change list and diff, then cv_cherry_pick restores that one role while keeping later changes. It affects one language edition, so your assistant should run parity_check afterwards and show any differences that need your attention.

Ask your AI
Restore the role I removed, keeping my later changes.
What it does
  • cv_changelog
  • cv_diff
  • cv_cherry_pick
  • parity_check
What you get
One restored entry, with any language mismatch reported.
Let me bring my CV in and take it with me again.

Yes, when the input is a JSON Resume document. Import replaces a language edition rather than merging it, so your assistant validates it first and supplies the current source hash to protect newer changes. Export returns JSON Resume data you can take to another tool.

Ask your AI
Import my JSON Resume file, and show me how to export it.
What it does
  • cv_validate
  • cv_get
  • cv_import
  • cv_export
What you get
A checked edition replacement and portable JSON Resume data.
Use a photo in my Norwegian CV but leave it out in English.

Yes. Upload the photo once, then choose whether readers see it separately for each language edition. New photos start hidden; hiding one keeps the file, while clearing it deletes the stored photo.

Ask your AI
Show my photo in Norwegian and hide it in English.
What it does
  • photo_set
  • photo_visibility_set
What you get
Separate photo choices for each edition; the stored photo stays.
Let recruiters read my CV, then close the link.

Yes. You choose publication with visibility_set; cv_pdf_link reports whether the public PDF currently opens. Unpublishing blocks the public page, PDF and photo immediately. It cannot recall downloaded copies; republishing revives old links unless you rotate them.

Ask your AI
Publish my CV for recruiters; unpublish it when I finish applying.
What it does
  • visibility_set
  • cv_pdf_link
What you get
A public CV link you can switch off, with clear contact disclosure.

How to

How can I use Vitae to keep two language editions consistent?

Say: “Add this new job to my Norwegian and English CV.” Your AI reads both editions with cv_get, asks you for missing facts, then uses entry_add_pair with matching dates and ongoing status. For a change to an existing role it uses entry_update_pair with the stable key returned by cv_get. It runs parity_check and shows any differences. You get the same career facts in both editions, while wording and job titles can differ; the check does not judge translation quality.

How can I use Vitae to make a PDF from my career notes?

Say: “Make a CV from these career notes and give me the PDF.” Your AI creates the intended language editions with cv_create, sets basics_set and adds the supplied roles with entry_add_pair for two languages or entry_add for one. It checks the structured document with cv_validate, calls cv_render, then cv_pdf_link. You get a typeset PDF through the owner download URL, which requires your session. Publication is a separate choice; your AI must not invent employers, dates or achievements.

How can I use Vitae to recover just one removed role?

Say: “Restore the job I removed without undoing my other edits.” Your AI uses cv_changelog and cv_diff to find the retained version and the exact entry, then cv_cherry_pick to bring it back. It runs parity_check because the recovery changes one language edition. You get that role restored with later work intact, plus any mismatch that needs your attention; recovery is limited to retained history.

How can I use Vitae to move my existing CV in or out?

Say: “Bring in this JSON Resume file and keep a copy I can take elsewhere.” Your AI calls cv_validate, then cv_get for the current source_hash. It explains that cv_import replaces the entire selected edition, and passes expect_source_hash so a newer edit causes a refusal. It runs parity_check after import and uses cv_export for your portable data. You get a validated edition replacement and an open-format export; import is not a merge.

How can I use Vitae to choose different photo visibility by language?

Say: “Show my photo in Norwegian, but leave it out of my English CV.” Your AI stores the supplied image with photo_set if needed, then uses photo_visibility_set for each edition’s show value. It can use cv_render and cv_pdf_link to give you the updated PDFs. You get separate photo choices without a parity warning; hiding keeps the image, while photo_clear destroys it. A published photo still depends on the CV being published.

How can I use Vitae to control what recruiters can open?

Say: “Share my CV, then close access when I am done applying.” Your AI explains that publishing reveals real email, phone and city, but excludes street address and postcode. At your request it uses visibility_set published, then cv_pdf_link and checks public_resolves. Later visibility_set unpublished blocks the public page, PDF and photo; link_rotate and pdf_uuid_rotate replace old addresses if requested. You get sharing you can switch off, while copies already downloaded remain with their recipients. Without rotation, republishing revives the old links.

Can I use it with the AI I already use?

Yes. Add https://vitae.publifye.com/mcp to an OAuth-capable MCP client and sign in with your Publifye account. Your assistant edits structured CV data rather than asking you to learn a separate editor.

Privacy and trust

Who can see my CV?

A new CV starts unpublished and public visitors cannot open its page or PDF. Publishing makes the page and redacted PDF available to anyone with the address, including real email, phone and city, while street address and postcode remain excluded and search indexing is discouraged. Unpublishing blocks those links immediately; downloaded copies cannot be recalled, and existing links work again if you republish unless you rotate them.

Can I hide my email but still publish?

The email forwarding relay is not built, and relay_set only records a preference for a possible future feature. A published CV shows your real email, phone and city. Keep it unpublished and send an owner-downloaded PDF yourself if that is your preferred sharing choice.

Can I use it with the AI I already have?

Yes. Vitae is an MCP server: add https://vitae.publifye.com/mcp as a connector in Claude or another MCP client and sign in once — no key to copy.

Will it write my achievements for me?

It edits what you tell it. Vitae does not invent experience, and `parity_check` flags gaps rather than filling them.

A cover letter to go with it?

A cover letter is a separate document. Your assistant can draft one in a separately connected document service such as Doksi; Vitae does not provide a built-in application-pack or cover-letter integration.

Who can see my CV?

A new CV is unpublished, with no public page or PDF. Publishing reveals the page and redacted PDF including email, phone and city, but never street address or postcode; unpublishing blocks links immediately. You cannot recall a copy already downloaded, and republishing revives old links unless you rotate them.

Plans and trial

Is there a free plan?

Yes, permanently: one CV in up to four languages, with the same typesetting, sharing and parity checks, and a daily call allowance. Vitae Access lifts that to 100 CVs with no language limit; a translation does not count as a second CV. Price: see the store.

Why would I pay for a CV tool?

Vitae keeps your CV in the open JSON Resume format and renders typeset PDFs. Use the free plan for one CV, or Vitae Access when you need more documents and languages; see the store for the current price.

What does Vitae Access include?

Vitae Access supports up to 100 CVs with no language cap. A translation is another edition of the same CV, not a second CV; version history, sharing, typesetting and parity checks are also available on the free plan.

Is there a free plan?

Yes. The permanent free plan holds one CV in up to four languages with the same typesetting, sharing and parity checks. Vitae Access raises the document and language limits; current allowances and prices are on the store.