3PAR (HPE 3PAR StoreServ)
3PAR is an enterprise storage platform, now part of Hewlett Packard Enterprise (HPE acquired 3PAR in 2010), that powers mission-critical applications with HPE 3PAR StoreServ and Primera arrays. For developers and automation engineers, 3PAR exposes the HPE 3PAR Web Services API (WSAPI) — a REST interface that manages storage provisioning, virtual volumes, hosts, ports, CPGs, snapshots, and remote copy on 3PAR/Primera/Alletra arrays, offering a more flexible and programmable alternative to the 3PAR Command Line Interface. HPE publishes first-party client libraries (Python, Ruby, PowerShell) plus Ansible, Puppet, Chef, OpenStack Cinder, and Docker volume integrations against WSAPI. This profile was surfaced as a venture-portfolio lead (Mayfield, Menlo Ventures backed the original 3PAR before its IPO and HP acquisition) and enriched from HPE's public developer surface.
More than an index entry, but the surface is still mostly links rather than artifacts — the cohort most likely to move a full band from modest, well-targeted work.
API Evangelist profiles 3PAR (HPE 3PAR StoreServ) the way a machine reads it — 1 machine-readable artifact across 1 API, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — 3PAR (HPE 3PAR StoreServ) scores 16.9/100 (emerging), with a separate agent-readiness read of 0/100 (human only). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile 3PAR (HPE 3PAR StoreServ)
Each block below is one kind of artifact we hold for 3PAR (HPE 3PAR StoreServ). For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 1
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
HPE 3PAR Web Services API (WSAPI)
REST API for managing HPE 3PAR StoreServ / Primera / Alletra storage arrays — virtual volumes, CPGs, hosts, ports, VLUNs, snapshots, and remote copy. Served by the WSAPI server ...
Resources
Every other property we hold for 3PAR (HPE 3PAR StoreServ) — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 1
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Build 3
SDKs, sample code, and the tooling you integrate with
Operate 1
Status, limits, changes, and where to get help
← All providers · Data indexed from github.com/api-evangelist/3par · machine-readable index on apis.io