slug: intelligems
provider: Intelligems
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: 4
edges:
- tag: Perform Experience Action
  spec_file: intelligems-perform-experience-action-api-openapi.yml
  capability_id: BC-4280.50
  capability_id_l1: BC-4280
  capability_name: A/B Test Execution
  confidence: 0.78
  evidence: POST /v25-10-beta/experiences/{experienceId}/actions/{action} — vendor is an "A/B testing,
    pricing optimization, and personalization platform"
  reason: Performing an action (e.g. start/pause/stop) on an experience is runtime control of a running
    A/B test or personalization, matching A/B Test Execution.
- tag: Create Experience
  spec_file: intelligems-create-experience-api-openapi.yml
  capability_id: BC-4280.50
  capability_id_l1: BC-4280
  capability_name: A/B Test Execution
  confidence: 0.75
  evidence: POST /v25-10-beta/experiences ... 'manage Intelligems A/B tests, personalizations, and experiences'
  reason: Creating an 'experience' in this vendor is creating an A/B test / personalization variant configuration,
    matching A/B Test Execution (configuration and targeting of running tests). Some ambiguity because
    experiences also drive pricing/content personalization rather than pure experimentation.
- tag: Update Experience
  spec_file: intelligems-update-experience-api-openapi.yml
  capability_id: BC-4280.50
  capability_id_l1: BC-4280
  capability_name: A/B Test Execution
  confidence: 0.75
  evidence: PUT /v25-10-beta/experiences/{experienceId} — "manage Intelligems A/B tests, personalizations,
    and experiences"
  reason: Updating an experience definition is configuration of an A/B/personalization test, which is
    A/B Test Execution configuration and targeting rather than product spec or pricing governance.
- tag: Fetch Experience Data
  spec_file: intelligems-fetch-experience-data-api-openapi.yml
  capability_id: BC-4280
  capability_id_l1: BC-4280
  capability_name: Product Telemetry & Experimentation Management
  confidence: 0.7
  evidence: GET /v25-10-beta/analytics/resource/{experienceId} ... POST /v25-10-beta/analytics/experience/{experienceId}/timeseries
  reason: Retrieves per-experiment analytics and the experience definition, i.e. monitoring and analysis
    of experiments. L1 experimentation/telemetry is clear; split between A/B Test Execution monitoring
    and usage analytics, so no L2 asserted.