slug: ezrentout
provider: EZRentOut
generated_by: planning/capability-mapping/scripts/classify_capabilities.py
model: claude-opus-5
frame:
- Transportation & Logistics
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: Purchase Orders
  spec_file: ezrentout-purchase-orders-api-openapi.yml
  capability_id: BC-500.30
  capability_id_l1: BC-500
  capability_name: Purchase Order Management
  confidence: 0.9
  evidence: POST /purchase_orders.api  createPurchaseOrder  Create a purchase order; PATCH /purchase_orders/{poId}/receive_items.api  Receive
    items against a purchase order; POST /vendors.api  createVendor
  reason: Plainly purchase order creation, update and goods receipt against vendors — Purchase Order Management
    within Procurement.
- tag: Customers
  spec_file: ezrentout-customers-api-openapi.yml
  capability_id: BC-420.10
  capability_id_l1: BC-420
  capability_name: Customer Data Management
  confidence: 0.75
  evidence: POST /customers.api Create a customer; GET /businesses.api List businesses; POST /contacts.api
    Create a business contact
  reason: Full CRUD over customers, business accounts and their contacts is customer master-record maintenance.
    It is clearly customer data management rather than sales pipeline or service, though 'businesses/contacts'
    could also be read as light account management.