jobhunt.app/mcp

Share your Hunt Page

Introduce yourself with a public page you can manage from your chat.

Updated

Step by step

  1. Choose how to use it

    Use your Hunt Page as a career introduction for recruiters, a link after a networking conversation, or a destination in your email signature. Choose the resume and public links that fit your audience. Your pipeline and private notes remain separate.

  2. Review the preview

    Open Hunt Page. Check your profile, displayed documents and the desktop, tablet and mobile previews. Your agent can also show private document-page previews; those images do not show the complete page layout or count as your approval to publish.

  3. Edit from your chat

    Ask your connected agent to show your current Hunt Page settings, then describe the changes to your resume selection, display name, links or appearance. Review what will change. Saving settings on an already-public page updates it immediately; changes to its linked resume or profile can also appear publicly.

  4. Choose one resume

    A new Hunt Page selection uses one resume. Cover letters, reference lists and statements remain in Hunt Docs; your agent may see them in the source list, marked unavailable for this selection. An older saved collection stays readable until you explicitly replace its selection. Saving or publishing page settings then requires choosing one resume, which replaces that collection; your agent asks before doing so.

  5. Choose your page address

    Choose an available address and review what will be visible. You can ask your agent to change the address later; check the resulting public link and any old link before continuing to share it. Search discovery is separate from whether the page is public.

  6. Make it public when ready

    After reviewing the page, ask your agent to publish it or use the publication control. Editing or previewing a private page does not publish it. A public page can be opened by anyone with its link, and search engines such as Google can list it so people can find you by name. Search listing is on for a new page. The website says so beside the Make public button, and your agent tells you before it publishes and again in its result.

  7. Keep your page out of search

    Open Hunt Page, choose Page options, untick “Allow search engines to find my public profile” and save. Or ask your agent: “Keep my Hunt Page out of search engines.” You can do this before or after publishing. The page stays public for anyone with the link. It is marked as not for listing and leaves the JobHunt sitemap straight away; a search engine that already listed it can take a while to remove it. Making the page private removes it from the web: its address then answers “not found”. A page that was already public keeps the search setting it had; nothing changes until you change it.

  8. Get the link or make it private

    Ask: "Give me my live Hunt Page link." The agent checks fresh publication and source availability before returning the current public address. A candidate address on a private page is not a live link; asking for the link does not publish it. To stop public access, ask to make the page private; changing search discovery alone does not make it private.

  9. Know what the link proves

    A saved public link is JobHunt’s recorded address. It does not prove that a recipient can open the page or that a search engine has indexed it.

What happens next

Only the page and documents you choose to display are shared. Your pipeline stays private.

Troubleshooting

A demo preview does not reserve an address or publish a real page. Search engines may take time to reflect a changed discovery setting. If someone opens an address that is mistyped, or a page you have made private, they see the JobHunt "Page not found" page with links to the home page and the sitemap. It looks the same in both cases, so it does not reveal whether a page was ever published there. Ask your agent: "Is my Hunt Page public right now, and what is its address?" to check the link before you send it. Open jobhunt.app without www; an address typed with www moves to the same page automatically.

Technical detailsAPI operations and permissions

These operation details and permissions come from the API contract.

READget hunt page workspace

Read the complete current Hunt Page workspace in bounded source/profile pages, including owner identity, selected collection publication fingerprints, source document types and versions. Uses the same authorized domain projection as the website; no initialization or publication. Existing get_hunt_page_v2 keeps its original strict schema.

GET /api/v1/journey/get_hunt_page_workspace

DECLARED PERMISSIONS

  • read:profile
  • read:documents
View input, output and access requirements →
READget hunt page

Read your saved Hunt Page settings, selected documents and profile choices. Paginated in groups of 25. Never creates or publishes a page.

GET /api/v1/journey/get_hunt_page_v2

DECLARED PERMISSIONS

  • read:profile
  • read:documents
View input, output and access requirements →
WRITEsave hunt page

Save the complete reviewed Hunt Page settings at the current revision. Uses the same profile, document and handle rules as the website. Saving an already-public page changes it immediately and requires acknowledge_public_update=true. Private pages stay private. Reuse request_id after lost responses.

POST /api/v1/journey/save_hunt_page_v2

DECLARED PERMISSIONS

  • read:profile
  • read:documents
  • write:profile
View input, output and access requirements →
READpreview hunt page document

Privately render one page of a selected Hunt Page document using the website renderer. Require the reviewed page revision and complete preview fingerprint. Recheck authority and sources after rendering. Does not publish or create a page; image chunks are private JPEG data.

GET /api/v1/journey/preview_hunt_page_document

DECLARED PERMISSIONS

  • read:profile
  • read:documents
View input, output and access requirements →
WRITEset hunt page visibility

Publish or make private the explicitly reviewed Hunt Page. Public exposes its selected documents and profile on the web. Require explicit user confirmation and the current preview fingerprint and revision. Never publish just because a user previews or edits. Reuse request_id for exact retries.

POST /api/v1/journey/set_hunt_page_visibility_v2

DECLARED PERMISSIONS

  • read:profile
  • read:documents
  • write:profile
View input, output and access requirements →
READget job hunt operation

Read a saved JobHunt operation after a retry or lost response. Use the original operation ID or request ID and operation name; optionally bind the expected payload hash. Full profile-photo receipts expose original non-secret photo artifact IDs in data.related_ids. Payload-hash-bound application-document customization checks also expose the exact created role-document ID. Payload-hash-bound submission-report checks expose the exact reported submission ID. Other receipt namespaces do not expose related IDs. Never repeat an uncertain create with a new key.

GET /api/v1/journey/get_job_hunt_operation

DECLARED PERMISSIONS

  • read:profile
  • read:applications
  • read:documents
  • read:campaigns
  • read:tasks
  • read:contacts
  • read:interviews
  • read:companies
  • read:calendar
View input, output and access requirements →