slug: fullcontact
provider: FullContact
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: Identity
  spec_file: fullcontact-identity-api-openapi.yml
  capability_id: BC-420.10
  capability_id_l1: BC-420
  capability_name: Customer Data Management
  confidence: 0.85
  evidence: 'POST /v3/identity.resolve resolveIdentity; vendor: ''unifying fragmented identifiers (email,
    phone, name, address, device IDs) into a single person-centric graph'''
  reason: Identity mapping/resolution/deletion across customer identifiers is explicitly the 'identity
    resolution, golden record' content of Customer Data Management.
- tag: Enrich
  spec_file: fullcontact-enrich-api-openapi.yml
  capability_id: BC-420.10
  capability_id_l1: BC-420
  capability_name: Customer Data Management
  confidence: 0.75
  evidence: POST /v3/person.enrich Enrich a person record; POST /v3/company.enrich Enrich a company record
  reason: Appending attributes to person and company records to build a fuller customer record maps to
    Customer Data Management (customer master, golden record). Some ambiguity with master-data management
    generally.