slug: apiman
provider: Apiman
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: 5
edges:
- tag: Devportal
  spec_file: apiman-devportal-api-openapi.yml
  capability_id: BC-4270.30
  capability_id_l1: BC-4270
  capability_name: Developer Portal Management
  confidence: 0.85
  evidence: GET /devportal/organizations/{orgId}/apis/{apiId}/versions/{apiVersion}/definition  Get an
    API Definition (schema) for an API Version; GET /devportal/apis/featured  Get all featured APIs; POST
    /devportal/search/apis  Search Apiman APIs
  reason: 'The surface powers the standalone developer portal: browsing featured APIs, reading API definitions
    and endpoints, viewing plans and policies, and creating a developer''s home organisation. That is
    Developer Portal Management.'
- tag: Organizations
  spec_file: apiman-organizations-api-openapi.yml
  capability_id: BC-4270
  capability_id_l1: BC-4270
  capability_name: Developer Platform & API Ecosystem Management
  confidence: 0.8
  evidence: POST /organizations/{organizationId}/apis  createApi  Create API; POST /organizations/{organizationId}/apis/{apiId}/versions/{version}/policies  createApiPolicy  Add
    API Policy; POST /organizations/{organizationId}/clients  createClient  Create Client
  reason: 'The core API management surface: publishing APIs and versions, defining plans and policies,
    registering client applications and contracts, with usage/response statistics schemas (UsagePerPlanBean,
    ResponseStatsPerClientBean). This realises API ecosystem management spanning API lifecycle and consumption
    governance, so the L1 is asserted without choosing a single L2.'
- tag: Developers
  spec_file: apiman-developers-api-openapi.yml
  capability_id: BC-4270
  capability_id_l1: BC-4270
  capability_name: Developer Platform & API Ecosystem Management
  confidence: 0.75
  evidence: GET /developers  getDevelopers; GET /developers/{developerId}/contracts  getAllClientContracts  Get
    all client contracts; GET /developers/apis  getAllPublicApiVersions
  reason: Operations manage developer records and the clients, contracts and public API definitions visible
    to each developer — developer-ecosystem management on an API management platform. Ambiguous between
    developer identity/credential stewardship and developer portal management, so only the L1 is asserted.
- tag: Experimental
  spec_file: apiman-experimental-api-openapi.yml
  capability_id: BC-4270.30
  capability_id_l1: BC-4270
  capability_name: Developer Portal Management
  confidence: 0.75
  evidence: GET /devportal/organizations/{orgId}/apis/{apiId}/versions/{apiVersion}/endpoint  Get endpoint
    information for an API Version; GET /devportal/apis/featured  Get all featured APIs
  reason: Despite the non-descriptive 'Experimental' tag, every operation is a /devportal path serving
    API discovery, definitions, plans and policies to developers — Developer Portal Management. Operations
    outweigh the tag string, but the tag's provisional nature lowers confidence slightly.
- tag: Roles
  spec_file: apiman-roles-api-openapi.yml
  capability_id: BC-620.20
  capability_id_l1: BC-620
  capability_name: Identity & Access Management
  confidence: 0.7
  evidence: POST /roles, PUT /roles/{roleId}; schemas NewRoleBean, UpdateRoleBean, RoleBean — vendor notes
    'multi-tenancy, events, notifications, permissions'
  reason: Roles here are permission-bearing authorisation roles within the API manager, i.e. role-based
    access administration, which maps to Identity & Access Management. Confidence held down because operations
    are bare CRUD with no explicit permission grant semantics shown.