Nectar Jobs status
Answered our latest tool-list check 16 hours ago with 7 tools. It will be marked verified after 3 successful checks in 7 days.
- Answered (30 days)
- 1 of 1 checks
- Last seen working
- 16 Nov, 18:16 UTC
- Last commit
- —
- Licence
- Not stated
Live checks
We call this hosted server's tools/list endpoint without credentials, from the public internet, every day while it answers and weekly otherwise.
- Answered
- Needs sign-in
- No answer
| Checked (UTC) | Result | Response time | Tools |
|---|---|---|---|
| 16 Nov, 18:16 | Answered | 2.8 s | 7 |
Tools (7)
Read from the server on 16 Nov 2026.
- search_jobs
- Search live job postings: use when the user asks what jobs are open for a role, a place, a salary or a skill. Each job carries ``url`` (its page on Nectar Jobs) and ``apply_url``. Args: query: keyword or natural-language query. Words that name an occupation ("manager", "software engineer") are matched against the TITLE; other words match the whole document (title, company, description), so a gener
- aggregate_jobs
- Aggregate counts for a filtered slice of the corpus — the tool for market/trend questions ("what kinds of roles are hiring in Pune?"), instead of issuing many limit-1 searches. Takes the same filters as search_jobs (keyword matching included, see its ``query`` note) and returns the slice's ``total`` plus breakdowns, each a {value: count} dict, biggest first: ``by_category`` (job function — the rol
- job_trends
- How a slice of the market has changed OVER TIME — use this for "is X growing/shrinking", "hiring trend", "more or fewer than last year". aggregate_jobs describes a slice as it stands today; this one shows its history. Takes the same filters as aggregate_jobs, plus ``bucket`` ("day"/"week"/"month"), ``since_days`` (at most 730), and ``measure``. Returns a ``series``, oldest first, each period carry
- find_similar_jobs
- Find jobs semantically similar to a given job (excludes its duplicates). At most ``max_per_company`` results per company (0 = uncapped; spellings of one employer, such as "Thales" and "Thales Group", count together), so one employer's near-identical postings don't fill the list; ``exclude_same_company`` drops the anchor's own company entirely ("roles like this elsewhere").
- recommend_jobs
- Rank jobs by how well they match a résumé or free-text description of what the candidate wants. Returns the best-matching jobs first. ``country`` (ISO-2, e.g. GB) or ``location`` (a city or region) is REQUIRED — ask the seeker where they can work rather than guessing. Semantic ranking over every country returns the nearest postings on earth, most of which the person cannot take. ``resume_text``: o
- get_job
- Fetch a single job's full details, including its description and any duplicate postings of the same role on other sources.
- get_stats
- Return corpus-wide coverage: total jobs, counts by source, and top companies. For the same numbers on a filtered slice (a location, a company, a query), use aggregate_jobs.