WP Consent API is the layer maintained by Really Simple Plugins and contributors so any plugin can declare which consent categories it relies on and any consent banner can read the current visitor decision through a single, well-defined function. It registers consent types (functional, statistics, statistics-anonymous, marketing, preferences), exposes a global cookie hook and tracks which active plugins declare support and which do not.

The plugin's admin is intentionally light: registration screens and a debug log. The data privacy officers and developers actually want, how many active plugins declare consent support, which categories they touch, which banner plugin is paired with WP Consent API and when registrations were last updated, sits across the active-plugin list, the registered consent types and the options metadata.

SleekView reads those registries directly. Sort by plugin name. Filter by declared_category to see what the stack touches, by paired_banner to confirm the banner pairing, by registration_updated to find recent changes. The plugin still owns the protocol. SleekView only adds the coverage audit table.

WP Consent API is doing important infrastructure work: a shared function any plugin can call to know whether the visitor has consented and any banner can call to write the decision. The plugin's own admin is intentionally small because the value is at the protocol level. The questions privacy officers and developers ask, though, are coverage-shaped.

How many active plugins on this site declare support, what categories does the stack actually touch, is a consent banner paired correctly. SleekView reads the same registries and renders them as one sortable audit surface. Same plugin, same protocol, but a coverage table that matches the questions a real privacy review asks.