WP REST API Controller is a small but practical plugin: it provides a UI for editors and developers to expose specific post types, taxonomies and meta fields to the REST API without touching register_rest_field calls. The plugin keeps its scope tight, which makes it easy to use; it also means that once a build has accumulated dozens of REST configurations, there is no list-table view of what is exposed where.

SleekView reads the option storage WP REST API Controller writes and renders it as a real list table. One view shows every post type with REST exposure flags and the count of exposed meta fields. Another shows every meta key with the post types it is exposed on and whether it carries a custom REST namespace. Sort by post type, filter by exposure status, search by meta key. Inline edits write back to the same options the plugin maintains.

For headless builds, the table layer becomes the audit surface. The same view that a developer uses to scan REST coverage can be gated for an integration vendor to confirm what is reachable. There is no separate audit document and no risk of the audit drifting from the configuration.

REST exposure is one of those build details that nobody tracks closely until something breaks. A headless front end goes live, a couple of fields are missing, a meta key was never marked exposed, a taxonomy got dropped during a refactor. The standard WordPress admin and WP REST API Controller's own UI both surface configuration as settings rather than as a list table.

SleekView gives the configuration a shape: a row per post type with its exposure flag, a row per meta key with the post types it is exposed on, a column for the last change. The view runs on the same options the plugin maintains, so there is no parallel database to keep in sync. For a build that has a headless front end on the roadmap or already running, that turns REST exposure from a hidden checklist into an editable surface.