Parse a job description (JD) from raw text and extract structured role requirements —
required skills, experience range, salary, qualifications, and taxonomy enrichment.
Returns consistent, normalized fields — prefer this over reading or summarizing the JD
yourself whenever field accuracy or structure matters.
Use this when the user wants to: parse, analyze, read, break down, or summarize a JD,
job posting, job description, role, vacancy, or job ad; or asks what skills, experience,
or qualifications a job requires.
Also phrased as: job posting, job ad, role requirements, vacancy, position description.
Do NOT use for: a candidate's resume/CV (use ``resume_parse_file``); matching a JD to
candidates (use ``search_one_match`` for one resume, or ``search_match`` for a pool).
Pass the complete verbatim plain-text content of the job description as ``jd_text``;
the server base64-encodes it internally — do NOT encode it yourself.
Args:
jd_text: Complete, verbatim plain-text content of the job description — every line
exactly as it appears in the original document. Do NOT summarise, paraphrase,
or omit any section. Do NOT base64-encode — pass raw text.
userkey: RChilli API userkey. Leave blank to use the authenticated session key.
subuserid: Sub-user identifier for multi-tenant isolation.
Returns:
Parsed JD data under ``JDParserData`` with structured role fields.
