How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

PCI Express

PCI Express is the PCI-SIG standard for high-speed serial interconnect between a processor and peripherals — GPUs, NVMe storage, network adapters and accelerators — defining the electrical, protocol and topology layers that effectively every modern computer is assembled around.

PCI Express is the interconnect the modern computer is built around. Governed by PCI-SIG, a member consortium, it defines how a processor talks to a GPU, an NVMe drive, a network adapter or an accelerator — as point-to-point serial lanes rather than the shared parallel bus it replaced.

  • Generational doubling - Each generation roughly doubles per-lane bandwidth, and the industry plans product cycles around the cadence.
  • Lanes and topology - Devices negotiate link width and speed, which is why the same card works at different performance in different slots.
  • The substrate for others - CXL builds cache-coherent memory semantics on the PCIe physical layer.
  • Member-governed, paid access - The specification is developed by PCI-SIG members; the full text is a membership benefit rather than an open publication.

PCIe is the most-referenced standard in the compute cohort of The State of Compute & Hardware APIs, appearing at twelve providers. It is also the sharpest illustration of that report’s standards argument. The stack is exhaustively standardized — PCIe, CXL, UCIe, JEDEC — and every one of those standards governs how parts talk to parts. None describes an interface a developer or an agent calls over a network. That is why the layer scores 10.7 while the layer renting it out scores 36.5, and why Redfish — the one network-facing standard in the market — has such a visible effect wherever it is implemented.

Referenced in API Evangelist papers

This standard shows up in my published research. These reports read the machine-readable evidence provider by provider — and put this standard in the context of a real sector.

The State of Compute & Hardware APIs

The most-referenced standard in the compute cohort at twelve providers — and the clearest example of §7's argument: this market's standards specify how parts talk to each other, never how a network client talks to the product.