jobhunt.app/mcp

Create your document package

Give your reusable resume and related documents a home.

Updated

Step by step

  1. Open Hunt Docs

    Choose Doc Package to create a package for a role type or direction you are pursuing.

  2. Write your resume

    Use the document editor to add your experience. Keep facts and claims true to your own work.

  3. Open the saved result

    When creating with your agent, ask it to read the new document back and give you its saved revision, package and private review link. Keep an existing default unless you explicitly choose a different one. If creation is interrupted, recover the original request instead of creating another document just to check whether it saved.

  4. Add related documents

    Keep cover letters, references or statements with the relevant package. Review each document before using it.

  5. Keep your resume selection

    Creating a cover letter, reference list or statement does not make it your default resume or select it as an application resume. Role-specific copies stay separate even if their application link is removed. Your first reusable master resume can still become the default if you create one later. Applications with a resume already selected keep that selection; the first master resume fills only applications that have no resume selected.

  6. Mark it ready

    Use the Draft / Ready to distribute toggle after reviewing your resume. Packages and individual documents have independent statuses; filter either list to find work in progress. A reusable Ready resume completes the onboarding milestone. Editing or restoring content keeps your choice. Versions shows the factual status-change history. Ready does not publish, send, prepare a PDF, verify facts or submit an application.

What happens next

You have reusable private documents that can be selected for individual applications.

Troubleshooting

Contact details may be managed by a linked Hunt Profile. Edit them there. If creation is unconfirmed, choose Check original or review its recovery copy in Hunt Docs before retrying.

Technical detailsAPI operations and permissions

These operation details and permissions come from the API contract.

READlist document packages

Read owned master document packages and their real version, sharing and usage counts. Follow has_more for packages and documents_have_more for members; package_id selects one exact package. Role copies remain in their application. No resume bodies are returned.

GET /api/v1/journey/list_document_packages_v2

DECLARED PERMISSIONS

  • read:documents
View input, output and access requirements →
WRITEcreate resume template

Create a Linen master from user-supplied career facts through the same package service as the website. The first saved document becomes primary and links previously unlinked applications; later creation preserves existing links and primary selection. Stages an optional private contact card from the explicit document or selected owned profile, never an account/default identity fallback. Label unsupported details as drafts, never fabricate achievements or qualifications. Keep the same request_id on retry. Existing resumes remain unchanged.

POST /api/v1/journey/create_resume_template_v2

DECLARED PERMISSIONS

  • write:documents
View input, output and access requirements →
READget document

Read one owned resume or cover letter with revision and fact sources. Use explicit detail reads for editing; summaries intentionally omit body content.

GET /api/v1/journey/get_document

DECLARED PERMISSIONS

  • read:documents
View input, output and access requirements →
WRITEadd package document

Add a private resume, cover letter, reference list or statement to an explicitly selected master package. Uses the browser creation rules and selected source identity; does not publish or submit. Keep request_id and account unchanged on retry.

POST /api/v1/journey/add_package_document_v2

DECLARED PERMISSIONS

  • write:documents
View input, output and access requirements →
READget document creation original

Check one exact native document creation original by captured account, immutable document ID, request UUID and byte descriptor. Read-only; returns recorded IDs/revision, not source content. Works after later changes or source removal. not_found is not permission to replace the original request.

GET /api/v1/journey/get_document_creation_original_v1

DECLARED PERMISSIONS

  • read:documents
View input, output and access requirements →
WRITEclose document creation original

Explicitly close unused retries of this exact native document creation original before clearing its local recovery. Atomically fences late creation or reports recorded/expired evidence. Never deletes, rolls back or recreates a document. Expired evidence does not prove creation never happened.

POST /api/v1/journey/close_document_creation_original_v1

DECLARED PERMISSIONS

  • read:documents
  • write:documents
View input, output and access requirements →
WRITEcreate native document file

Create the explicitly reviewed full native document original from an approved private host file, up to 16 MiB content plus request envelope. Exact account/document/request IDs and file bytes must match the retained descriptor. Shares the browser package transaction, original receipt, Linen/primary/owned application links/optional explicit-identity card and immutable initial snapshot. Raw facts remain unconfirmed; linked identity requires read:profile. No implicit default identity, publication or submission. Retry only this original; exact replay skips downloading and never recreates deleted work.

POST /api/v1/journey/create_native_document_file_v1

DECLARED PERMISSIONS

  • read:documents
  • write:documents
View input, output and access requirements →