CazVid

Showing 25 of 33 from the live probe.

• Preview a job post

  Generate a preview of a job post from a plain-language prompt WITHOUT saving anything. Returns a structured draft (title, work mode, salary, and an optional long-form description) so the user can review the wording before committing. Consumes 1 of your 10 daily CazVid Developer API calls (quota resets at UTC midnight). Use it to show what a job would look like or to iterate on phrasing. ALWAYS put an explicit city in the prompt (e.g. 'in Puerto Vallarta'), or state that the job is remote and for

• Create a job in CazVid

  Create a real job in CazVid from a plain-language prompt. By DEFAULT this creates a reviewable DRAFT - nothing goes live. Consumes 1 of your 10 daily CazVid Developer API calls (quota resets at UTC midnight). Returns the created job's summary, its postId, whether it is a draft or published, and where to review it. ALWAYS put an explicit city in the prompt (e.g. 'in Puerto Vallarta'), or state that the job is remote and for which country - an onsite/hybrid job with no recognizable city cannot be

• Check CazVid API quota

  Show your CazVid Developer API quota for ALL SIX tool families in one response: Job Builder (preview_job / create_job, 10 per UTC day), Candidate Search (search_candidates, 100 per UTC day), Webhooks (event deliveries, 5,000 per UTC day - list_webhook_endpoints itself is free), Job Search (search_jobs, 500 per UTC day), and CRM (every crm_* tool, 5,000 per UTC day by default - an organization can be granted more, which is one reason to read the number here rather than assume it - plus a separate

• Search CazVid candidates

  Read-only search of CazVid's candidate database (job seekers) from a plain-language query plus optional structured filters (location, remote-only, video-required, language, created-after date). It returns candidate profiles and NEVER changes anything. Each call counts against a candidate-search quota of 100 searches per UTC day and 20 per minute, which is SEPARATE from the job-builder quota. Results are paginated (up to 25 per page, default 10); when more results exist, request the next page. Re

• List CazVid webhook endpoints

  Read-only list of the organization's Developer Webhooks endpoints - the HTTPS receivers CazVid sends signed application.received events to (fired when a candidate applies to one of the org's job posts). Shows each endpoint's URL, status (pending_verification / active / disabled / suspended), subscribed events, and timestamps. It NEVER changes anything and NEVER returns signing secrets. Creating, verifying, rotating, or deleting endpoints is done in the CazVid app (Profile > Webhooks) or the REST

• Search CazVid jobs

  Read-only search of CazVid's PUBLIC job posts from a plain-language query plus optional structured filters (location, remote-only, language, posted-after date). It returns public job listings and NEVER changes anything. Results are PUBLIC job posts and never include hiring-manager contact details (no email or phone) - to apply, open the 'Apply via CazVid' link included with each result. Each call counts against a job-search quota of 500 searches per UTC day and 30 per minute, which is SEPARATE f

• Search CazVid CRM contacts

  Read-only list/search of your organization's CRM contacts with an optional plain-language search (matches name, company, job title, skills, industry, education, email, and phone). Returns compact rows - name, company, title, location, tags, resume state, and the contact id - so you can then open one with crm_get_contact. It NEVER changes anything. Email and phone details are omitted from the list (use crm_get_contact for those). Results are paginated (up to 50 per page, default 10) on a hasMore

• Get a CazVid CRM contact

  Read-only full detail of one CRM contact by id (from crm_search_contacts): name, company, job titles, location, LinkedIn, all emails and phones with their labels, tags, resume state, and whether the contact is linked to a CazVid platform user. When the API reports it, each resume is listed with its file name and PARSE STATUS (plus the last error and the next retry when a parse did not finish) - use this to diagnose a resume whose fields never landed on the contact after crm_upload_resume. It NEV

• Create a CazVid CRM contact

  Create a contact in your CRM. Only `name` is required; everything else (first/last name, job titles, company, LinkedIn, location, emails, phones, tags) is optional. IDEMPOTENT: the backend de-duplicates by email or phone WITHIN the workspace, so calling this again with the same email or phone returns the EXISTING contact (the result says 'matched an existing contact') instead of creating a duplicate - no separate idempotency key is needed, and a retry after a timeout is safe. Consumes 1 of your

• Update a CazVid CRM contact

  Update fields on an existing CRM contact by id. Send ONLY the fields you want to change; omitted fields are left as-is. Note that on an update, `emails` and `phones` are capped to a SINGLE entry each - a PATCH replaces the contact's PRIMARY email/phone slot rather than appending, so pass at most one of each. Consumes 1 of your CRM daily quota. The CRM API requires a Platinum, Diamond, or Enterprise plan.

• Delete a CazVid CRM contact

  Soft-delete a CRM contact by id. This ARCHIVES the contact (it is not permanently erased) and also removes its interactions and list memberships. This is a destructive action - only call it when the user has clearly asked to delete the contact. Consumes 1 of your CRM daily quota. The CRM API requires a Platinum, Diamond, or Enterprise plan.

• Log a CazVid CRM interaction

  Append an interaction - a timeline entry such as an email, call, interview, or note - to a CRM contact. `contact_id` and `type` are required; `type` is an interaction-type NAME from the fixed global taxonomy (call crm_list_interaction_types to see the valid names; an unknown name is rejected). Optionally add a free-text note, a date (defaults to now; a future date is fine for a scheduled follow-up), and tags. Each call creates a NEW interaction - it is NEVER de-duplicated, so do not blindly retr

• List a CazVid CRM contact's interactions

  Read-only timeline of one CRM contact's interactions (emails, calls, interviews, notes), newest first - each with its type, date, note, and tags. It NEVER changes anything. Paginated (up to 50 per page, default 20) on a hasMore flag - there is no total count. Consumes 1 of your CRM daily quota. The CRM API requires a Platinum, Diamond, or Enterprise plan.

• List CazVid CRM interaction types

  Read-only list of the valid interaction-type NAMES you can pass as `type` to crm_log_interaction, grouped by category. The taxonomy is a fixed global list (the same for every workspace). It NEVER changes anything. Consumes 1 of your CRM daily quota. The CRM API requires a Platinum, Diamond, or Enterprise plan.

• Upload a resume to a CazVid CRM contact

  Attach a resume file (PDF, DOC, or DOCX) to a CRM contact and queue it for parsing. `contact_id`, `file_name` and `mime_type` are always required, plus EXACTLY ONE of `source_url` or `resume_base64`. PREFER `source_url` whenever the file is reachable at an https URL: the server fetches it, so you send about 100 characters instead of the whole file. `resume_base64` is only practical for a very small file - base64 inflates it by a third, and a real resume is enormous as a tool argument (an 81 KB P

• List CazVid CRM pipelines

  Read-only list of your organization's CRM pipelines (candidate boards - what the CazVid app calls Lists), newest first. Returns each pipeline's id, name, color, and card count so you can open one with crm_get_pipeline. It NEVER changes anything. Paginated (up to 50 per page, default 20) on a hasMore flag - there is no total count. Each call consumes 1 of your CRM daily quota (5,000 per UTC day by default, 30 per minute), shared with the other crm_* tools; an organization can be granted a higher

• Get a CazVid CRM pipeline

  Read-only full view of one CRM pipeline (a board) by id: its name and color, every active stage in board order (id, name, color, position, card count), and a page of each stage's cards. Use this after crm_list_pipelines to get the stage ids and card ids you need for crm_edit_stages, crm_add_candidate_to_list, crm_move_candidate_stage, or crm_remove_candidate_from_list. It NEVER changes anything. A card carries IDs ONLY - no personal data - so pair a card's contact id with crm_get_contact to read

• Create a CazVid CRM pipeline

  Create a new CRM pipeline (a candidate board). `name` is required and must be letters, digits, and single spaces only - no punctuation; accented characters are fine (the CazVid app's own rule). Choose how its stages start with `stage_source`: 'default' seeds the standard candidate-pipeline template; 'copy_from_pipeline' copies an existing pipeline's stage names, colors, and order (send its id as `source_pipeline_id`, and note it must be a pipeline your own API key's user created); 'custom' start

• Update a CazVid CRM pipeline

  Rename and/or recolor a CRM pipeline. Send only the fields you want to change; an empty change is a successful no-op. To edit STAGES (add, rename, recolor, reorder, or delete a column) use crm_edit_stages instead - this tool only touches the pipeline itself. Consumes 1 of your CRM daily quota. The CRM API requires a Platinum, Diamond, or Enterprise plan.

• Delete a CazVid CRM pipeline

  ARCHIVE a CRM pipeline (soft-delete: the pipeline, all of its stages, and all of its cards are removed from view, and any job postings linked to it are unlinked - nothing is hard-erased, and the CONTACTS behind the cards are NOT deleted). This is DESTRUCTIVE and cannot be undone through this API: only call it when the user has CLEARLY and EXPLICITLY asked to delete this specific pipeline. Never delete a pipeline as a side effect of another request, and never guess which one they mean - if there

• Edit a CazVid CRM pipeline's stages

  Add, rename, recolor, reorder, or delete a stage (column) on a CRM pipeline. Set `action` to one of: 'add' (requires `name`, `color` optional - the new stage is appended at the END of the board), 'rename' (requires `stage_id` and `name`), 'recolor' (requires `stage_id` and `color`), 'reorder' (requires `stage_order` - EXACTLY the pipeline's current active stage ids in the new top-to-bottom order; get them from crm_get_pipeline), or 'delete' (requires `stage_id`; if that stage holds any cards the

• Add a candidate to a CazVid CRM pipeline

  Add a candidate (an EXISTING CRM contact) to a pipeline as a card. `pipeline_id` and `contact_id` are required - find a contact with crm_search_contacts, or create one with crm_upsert_contact first; a contact id that does not exist in this workspace is rejected. `stage_id` is optional: omit it to place the card in the pipeline's FIRST stage (its normal landing stage), or pass a stage id from crm_get_pipeline to place it elsewhere directly. NO DUPLICATES: a contact can only hold ONE active card p

• Move a CazVid CRM pipeline card to a different stage

  Move a pipeline card to a different stage - e.g. advance a candidate from 'Screening' to 'Interview'. `pipeline_id`, `card_id` (from crm_get_pipeline or crm_add_candidate_to_list), and `stage_id` (the target stage, also from crm_get_pipeline) are all required. The target stage must belong to THIS pipeline - a card can never be moved onto another pipeline's stage. The move is recorded in the card's stage history exactly as a drag-and-drop in the CazVid app would be. Repeating it with the SAME sta

• Remove a candidate from a CazVid CRM pipeline

  Remove a card from a pipeline. This does NOT delete the underlying CRM contact - only the card, i.e. that contact's membership in THIS pipeline (use crm_delete_contact to delete the person). It is a soft removal, so nothing is hard-erased. `pipeline_id` and `card_id` are required, both from crm_get_pipeline. A card id that does not belong to this pipeline - including one already removed - is reported as not found, so read the result rather than assuming a repeat call succeeded. Consumes 1 of you

• Create a CazVid CRM task or anchored activity

  Create a task - a unit of WORK, such as a drafted outreach message awaiting approval ('proposal'), a scheduled nudge ('followup'), or anything else ('todo'). `task_type` is always required, and you must say what the activity is about with EXACTLY ONE of two argument groups: `contact_id` (the common case - a CRM contact, the legacy shorthand) OR `anchor_type` (+ `anchor_id`, unless `anchor_type` is 'none') for one of the other four anchors - candidate (a CazVid user), job (a job post), applicatio