Skip to main content
Agent guide: CLI and SDK instructions →

​
1. Have your context ready

Have target companies, job families or roles of interest, freshness rules, and the allowed review action.

​
2. Ask your agent

Paste this into your agent, then provide your task and example inputs when it asks:
Complete any requested sign-in yourself. Give the agent the missing information before approving execution. Provider-backed work can incur usage.

​
3. Review the result

The signal is supported by the actual role and source. A job posting is evidence of a stated requirement, not proof of internal infrastructure or purchasing intent. Ask your agent:
Approve a larger job, recurring work, or external changes only after reviewing that decision.

​
Check your understanding

Does a job posting prove that a particular team has purchased or selected software?
No. It supplies evidence of a posted role under that source. Software selection needs additional evidence.