axcient-jobs

# Axcient Jobs ## Overview A job is one configured backup task running against a device — the thing that actually produces recovery points. Jobs always nest under a specific `client_id` and `device_id`; there is no organization-wide job list. Get a device's job IDs from `axcient_get_device` (the `jobs` array) or `axcient_list_devices_by_client` first. ## Tools | Tool | Description | Arguments | |------|-------------|-----------| | `axcient_list_jobs_by_device` | All jobs for a device | `client_id`, `device_id` | | `axcient_get_job` | One job's detail | `client_id`, `device_id`, `job_id` | | `axcient_get_job_history` | Run history for a job | `client_id`, `device_id`, `job_id`, `limit?`, `offset?`, `starttime_begin?` | There is no job-level list at the organization or client level — jobs are always reached through a specific device. ### Job Types: BRC vs Replibit The job schema is a tagged union — `org_level_jobs_response` is one of `org_level_brc_job` or `org_level_replibit_job`, mirroring the device-level `product` split (`BRC` vs `X360RECOVER`). Handle both shapes: a legacy appliance's jobs return the BRC shape, current-generation appliances and D2C devices return the Replibit shape. Don't assume one field set applies to every job in a fleet with mixed appliance generations. ### Job Thresholds Jobs carry the same threshold structure as devices — `vault_rp_threshold`, `cloud_rp_threshold`, `local_rp_threshold`, `protection_threshold` — each an object with `value`, `...