Skip to main content
πŸ‘€ For humans This is a Claude Code skill file. Save it as .claude/skills/tamradar/SKILL.md in your project. Claude Code will load it automatically when you mention TAMradar, or invoke it directly with /tamradar. Give this link to your agent: https://docs.tamradar.com/agentic/tamradar-skill.md

TAMradar Monitoring

Full instructions: https://docs.tamradar.com/agentic/tamradar-agent.md Base URL: https://api.tamradar.com Β· Auth: x-api-key: $TAMRADAR_API_KEY on every request β€” no Bearer prefix

Key Rules

  • Auth: check $TAMRADAR_API_KEY in env first β€” if unset, ask the user
  • webhook_url: optional β€” omit for poll-only radars (default); include only if the user provides a real webhook URL for push delivery
  • updates_since: use the user’s timeframe. If unspecified, recommend recent weeks (or earlier months for hires/promotions) and confirm before creating. Send a past or current RFC 3339 timestamp with timezone; calculate it from the agreed timeframe.
  • include_historical: deprecated β€” do not send it; use updates_since
  • Persistence: save (domain, radar_type, radar_id) to ./tamradar-radars.jsonl after every 201
  • Idempotency: check ./tamradar-radars.jsonl before every POST β€” skip if already exists
  • Singles vs bulk: ≀10 targets β†’ single POSTs; >10 β†’ POST /v1/radars/bulk (async queue, max 1000 items per request). Optional priority (low / normal / high, default normal) orders the user’s own bulks; use high only for urgent lists.
  • 409 is not an error β€” read errors[0].conflicting_radar_id, store it, move on
  • Polling response: field is updates[] β€” not data[]
  • Polling cap: max 10 radar_id values per call β€” split into multiple requests if needed
Set updates_since to include recent activity. Choose a date a few weeks or months back for eligible activity from that period plus ongoing updates. If omitted, most radars start at their exact creation time, not the start of today: even a post published one minute earlier is excluded. Your first check may return no results, and updates may take time to arrive. New hires and promotions use UTC calendar-month precision: set updates_since to an earlier month to include activity from that month onward. If omitted, eligibility starts in the month the radar was created. contact_job_changes monitors detected changes, not historical job moves. To see sample findings first, use Preview where supported. Preview chooses its own lookback and does not accept updates_since.

Flow

Endpoint reference (machine-readable)

  • https://docs.tamradar.com/api-reference/create-company-radar.md
  • https://docs.tamradar.com/api-reference/create-contact-radar.md
  • https://docs.tamradar.com/api-reference/create-industry-radar.md
  • https://docs.tamradar.com/api-reference/poll-updates.md
  • https://docs.tamradar.com/api-reference/account.md

Pre-flight

balance_remaining_usd == 0 β†’ STOP Β· < 5 β†’ WARN and confirm Β· >= 5 β†’ proceed

Create β€” company

The company and industry examples use an illustrative, user-confirmed April 1, 2026 cutoff. Replace it with the date calculated from your user’s timeframe.
Domain accepts any format (https://www.openai.com/about β†’ normalized to openai.com). Best practice: bare domain.

Create β€” contact

For contact_job_changes, use an individual email or a LinkedIn /in/ person profile; role-based/shared emails and company, school, or /pub/ LinkedIn URLs are rejected. Within the same domain and radar type, either an email match or a normalized profile URL match returns 409; full_name alone is not a duplicate key. Read errors[0].field to see whether identifiers.email or identifiers.profile_url matched.

Create β€” industry

Persist after every 201

Poll for findings

Paginate: while has_more: true β†’ fetch with cursor={next_cursor} plus the same since and filters (the cursor does not remember them). Findings retained about 60 days.

Error handling

Summary (always present when done)