slug: smile-io
provider: Smile.io
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: 8
edges:
- tag: Earning Rules
  spec_file: smile-io-earning-rules-api-openapi.yml
  capability_id: BC-420.40
  capability_id_l1: BC-420
  capability_name: Loyalty & Retention Management
  confidence: 0.85
  evidence: GET /earning_rules  List earning rules; "A RESTful interface for interacting with Smile.io
    loyalty programs"
  reason: Earning rules define how loyalty points are accrued — configuration of a loyalty programme,
    i.e. Loyalty & Retention Management.
- tag: Points Transactions
  spec_file: smile-io-points-transactions-api-openapi.yml
  capability_id: BC-420.40
  capability_id_l1: BC-420
  capability_name: Loyalty & Retention Management
  confidence: 0.85
  evidence: 'POST /points_transactions  Create a points transaction; schemas: PointsTransaction'
  reason: Issuing and listing loyalty point transactions (accrual/redemption ledger) is core loyalty programme
    execution, not financial accounting.
- tag: Activities
  spec_file: smile-io-activities-api-openapi.yml
  capability_id: BC-420.40
  capability_id_l1: BC-420
  capability_name: Loyalty & Retention Management
  confidence: 0.8
  evidence: POST /activities  post__activities  Create an activity; "A RESTful interface for interacting
    with Smile.io loyalty programs ... VIP tiers, and activities"
  reason: Activities are customer actions recorded in a loyalty/rewards program to drive points earning,
    so the surface realises Loyalty & Retention Management. Slight ambiguity only about whether it belongs
    under loyalty versus broader customer lifecycle engagement.
- tag: Customers
  spec_file: smile-io-customers-api-openapi.yml
  capability_id: BC-420.10
  capability_id_l1: BC-420
  capability_name: Customer Data Management
  confidence: 0.8
  evidence: 'GET /customers/{id}  Retrieve a customer; GET /customers  List customers; schemas: Customer'
  reason: CRUD/read access over customer records in the loyalty platform maps to Customer Data Management.
- tag: Points Products
  spec_file: smile-io-points-products-api-openapi.yml
  capability_id: BC-420.40
  capability_id_l1: BC-420
  capability_name: Loyalty & Retention Management
  confidence: 0.8
  evidence: 'POST /points_products/{id}/purchase  Purchase a points product; schemas: Reward, PointsProduct,
    RewardFulfillment'
  reason: Points products are loyalty rewards redeemable with points; purchasing/redeeming them is loyalty
    programme operation, not commercial product management.
- tag: Reward Fulfillments
  spec_file: smile-io-reward-fulfillments-api-openapi.yml
  capability_id: BC-420.40
  capability_id_l1: BC-420
  capability_name: Loyalty & Retention Management
  confidence: 0.8
  evidence: GET /reward_fulfillments  List reward fulfillments; "rewards and reward fulfillments"
  reason: Fulfilment of loyalty rewards earned with points is part of running the loyalty programme.
- tag: Customer Identities
  spec_file: smile-io-customer-identities-api-openapi.yml
  capability_id: BC-420.10
  capability_id_l1: BC-420
  capability_name: Customer Data Management
  confidence: 0.75
  evidence: 'POST /customer_identities/create_or_update  Create or update a customer identity; schemas:
    CustomerIdentity'
  reason: Creating/updating customer identity records in a loyalty platform is customer master/identity
    resolution — Customer Data Management. Thin surface (one operation) but the object is plainly a customer
    identity record.
- tag: Points Settings
  spec_file: smile-io-points-settings-api-openapi.yml
  capability_id: BC-420.40
  capability_id_l1: BC-420
  capability_name: Loyalty & Retention Management
  confidence: 0.75
  evidence: 'GET /points_settings  Get points settings; schemas: PointsSettings'
  reason: Configuration of the points program within a loyalty platform; supports Loyalty & Retention
    Management, though the surface is a single read endpoint.