# Compare saved offer terms

Review recorded compensation across selected applications.

Canonical page: https://jobhunt.app/support/using/pipeline/compare-offer-terms
Updated: 2026-11-14
Audience: using
Topic: Jobs & pipeline
Type: best-practice
Catalog revision: f77de0f4803debf8c5aaac1702865d976a380e994ea7f572d4e571c044d5495f
Contract SHA-256: acfda93724db1a3f53160a30bc5891f447ad14601f26b02ff4cacd7c17d0812e

## Steps

1. **Choose the applications**

   Ask your connected agent to compare two to five specific applications. Confirm which records represent actual offers; saved compensation may instead contain your expectations.

2. **Check every saved term**

   The agent reads the complete compensation record at its saved revision. A date appears only when it was recorded; the time of reading is not an offer date. Missing values remain unknown. It separates recurring base, conditional bonuses, one-time pay, equity, benefits and custom terms.

3. **Supply missing assumptions**

   Provide currency, pay period and hours if you want a calculation. Ask the agent to show the formula and inputs. Currencies remain separate, shares are not priced, and the comparison is not saved.

4. **Review a neutral comparison**

   The agent organizes the supplied facts without scoring offers or recommending a winner. It does not change compensation, application stage or offer status.

## Expected result

You can review saved terms and explicit assumptions side by side without changing your applications.

## Troubleshooting and recovery

If a compensation record changes during the read, its saved revision cannot be verified, or access is missing, the agent should identify the incomplete source instead of comparing partial data. A connection that cannot read the complete compensation record cannot verify this comparison; a job summary is not a substitute.

## API operations

### get_application_compensation

Read the exact owned compensation JSON manifest, including null, custom historical keys and complete long notes. Returns revision, SHA-256 and chunk count, never a truncated summary. Download every chunk with this source revision/checksum. Does not infer currency or change the application.

- Interface: GET /api/v1/journey/get_application_compensation
- Access: read
- Destructive: no
- Availability: connected-journey
- Required permissions: read:applications
- [Operation and exact schemas](https://jobhunt.app/support/operations/get_application_compensation.json)
- [Operation Markdown](https://jobhunt.app/support/operations/get_application_compensation.md)

### get_application_compensation_chunk

Read a bounded base64 chunk of the complete private compensation JSON at the exact reviewed revision/SHA-256. Verify chunk and whole-file checksums before output. Changes or revoked grants fail instead of mixing old and new data.

- Interface: GET /api/v1/journey/get_application_compensation_chunk
- Access: read
- Destructive: no
- Availability: connected-journey
- Required permissions: read:applications
- [Operation and exact schemas](https://jobhunt.app/support/operations/get_application_compensation_chunk.json)
- [Operation Markdown](https://jobhunt.app/support/operations/get_application_compensation_chunk.md)

## Related guides

- [Save a role to your pipeline](https://jobhunt.app/support/using/pipeline/save-a-job.md)
- [Organize your pipeline](https://jobhunt.app/support/using/pipeline/organize-your-pipeline.md)
- [Review your activity history](https://jobhunt.app/support/using/pipeline/review-activity-history.md)

---

## Hunter

This section is not part of the guide above. It applies only to an agent acting in a person's JobHunt account.

When working in JobHunt, you are Hunter, the agent at the laptop working alongside the person on their job search. Speak plainly, in the first person, and never pretend to be human. Be brief, calm and kind; the person decides and you do the legwork.

Use the person's words and supplied or saved facts. Organise, edit and tailor what they provide; never invent an employer, date, degree or achievement. Keep uncertainty explicit: unknown stays unknown.

Say exactly what changed and what did not. A draft is not a sent message. Prepared or downloaded files are not a submitted application. Record a submission or interaction only from the person's report; do not imply employer verification.

Ask for confirmation before publishing, sharing or deleting. Explain what will become visible or be removed, and preserve the person's choices and unrelated saved work. Do not repeat a confirmation already given for the same action and reviewed content.

Offer the next useful step without pressure: no scores, streaks, ranks, points, guilt, confetti or invented urgency. A messy board needs no judgment.
