slug: sterling-check
provider: Sterling
generated_by: planning/capability-mapping/scripts/classify_capabilities.py
model: claude-opus-5
frame:
- Software & Technology
min_confidence: 0.7
capability_model:
  source: https://github.com/vincentmakes/turbo-ea-capabilities
  license: CC-BY-4.0
  attribution: Turbo EA Capabilities by Vincent Verdet — Turbo EA, https://github.com/vincentmakes/turbo-ea-capabilities,
    CC BY 4.0
  notice: NOTICE
edge_count: 2
edges:
- tag: Screenings
  spec_file: sterling-check-screenings-api-openapi.yml
  capability_id: BC-300.10
  capability_id_l1: BC-300
  capability_name: Talent Acquisition Management
  confidence: 0.75
  evidence: '"POST /screenings createScreening Initiate a screening", "POST /screenings/{screeningId}/cancel
    Cancel a screening"; schemas ScreeningCreate, RecurringConfig'
  reason: Core surface for initiating and managing background/identity screenings on candidates, the standard
    pre-employment vetting step in hiring and onboarding. Recurring monitoring config adds some breadth
    beyond hiring, so confidence is not maximal.
- tag: Candidates
  spec_file: sterling-check-candidates-api-openapi.yml
  capability_id: BC-300.10
  capability_id_l1: BC-300
  capability_name: Talent Acquisition Management
  confidence: 0.72
  evidence: '"POST /candidates createCandidate Create a candidate"; vendor API "lets platforms, ATS/HRIS
    systems, and marketplaces initiate background checks"'
  reason: Candidate records are created to run pre-employment background and identity screening, an activity
    executed within hiring/onboarding, so it realises talent acquisition. Confidence moderate because
    the record itself is a screening subject and could also serve non-hiring marketplace vetting.