Radar

A clean API and continuously refreshed data feed for contract tech opportunities.

Radar pulls fragmented contract listings into one normalized, deduplicated dataset, verifies whether they're still live, and adds structured intelligence around occupation, engagement type, commercial eligibility, rates, application destinations, and source provenance.

Try the API →View docs

Create account Pricing Sign in Talk to us

Predictable API plans

One read-only contract for already-computed intelligence.

No discovery, crawling, or paid model work occurs when a customer reads the API.

Production response excerpt

Real data. Explicit uncertainty.

Verified August 27, 2026 at 19:07 UTC. This is a dated excerpt, not a permanently live example.

Run the live playground →

Request

GET /v1/preview/opportunities
  ?job_family=data
  &job_subfamily=data_engineering
  &job_class=etl_developer
  &level=senior
  &liveness_status=live
  &limit=5

Dated production record

{
  "id": "ed30aafb-928f-455b-a5e7-174a87821127",
  "title": "Ab Initio Developer",
  "employer": "Info Origin Inc.",
  "job_family": "data",
  "job_subfamily": "data_engineering",
  "job_class": "etl_developer",
  "level": "senior",
  "engagement_models": ["ambiguous_contract"],
  "commercial_eligibility": "research_required",
  "liveness_status": "live",
  "last_verified_live_at": "2026-08-27T19:07:00.933559Z",
  "sources": [{ "name": "Dice" }],
  "evidence": [{
    "label": "generic_contract",
    "excerpt": "Contract"
  }]
}

More than a listing feed

Structured context that makes opportunity data usable.

Unknown values remain unknown. Evidence and provenance travel with the normalized record.

Canonical opportunities

Stable identities connect repeated and syndicated listings without discarding source evidence.

Technology taxonomy

Structured domain, family, class, level, management track, and specialization fields.

Engagement model

C2C, 1099, freelance, subcontract, W2 contract, ambiguous, and unknown remain distinct.

Commercial eligibility

Evidence-backed eligibility states prevent generic contract language from becoming false certainty.

Compensation

Normalized rates, units, and currency where the source actually provides them.

Geography

Remote status, country, region, city, and location restrictions in queryable fields.

Freshness and liveness

Publication precision, observation history, and current actionability are represented separately.

Source provenance

Publisher, source records, canonical destinations, and evidence remain inspectable.

Application destinations

Listing provenance stays intact while Radar resolves the actual application destination when it can be safely determined.

Use cases

Three ways to build with clean contract data.

Job-search products

Filter 1099, C2C, freelance, and other contract opportunities using structured engagement evidence instead of keyword matching alone.

Recruiting and staffing tools

Distinguish W-2 contract, independent eligibility, ambiguous contract language, currentness, and application destinations before someone acts.

Job boards, marketplaces, and automated products

Consume normalized opportunity records, stable IDs, liveness, and source provenance without rebuilding the acquisition and normalization layer.

Developer experience

One schema. Structured filters. Stable IDs. Provenance.

Read-only API keys, predictable errors, cursor pagination, and an OpenAPI contract make Radar straightforward to consume.

Run a real query

Open the developer explorer, change the filters, and inspect the authenticated response next to generated cURL, JavaScript, and Python.

Open playground →