API surface area

What it means

API surface area describes public methods, endpoints, events, configuration options, or types that consumers can depend on. A larger surface can increase compatibility and documentation work. The useful unit depends on the interface and should distinguish supported contracts from internal helpers.

Example

A library exposes 40 public methods, although most consumers need only six. The team identifies the supported core, documents compatibility expectations, and hides accidental exports where practical.

Limitations

A small surface can still be difficult if its semantics are complex or poorly documented. Removing an endpoint may break unknown consumers, and generated APIs can inflate counts. Combine the measure with usage and compatibility evidence.

How to use the signal

Review the public contract with real consumers, because exported symbols that nobody uses can still become long-term compatibility obligations.

Weave can connect surface-area changes to review load and release rework. Keep API inventory and usage in contract tooling; use Weave to understand how interface changes move through engineering work.