Public Data Portal Intelligence
File-to-API candidates
Asset
What this page is
Review queue
This page does not say every file should become an API. It highlights file datasets that may deserve earlier human review.
High-demand first
The slice is biased toward rows that already show meaningful use, so the question is where easier access could matter most.
Lightweight public view
The browser reads a compact summary asset, not the full internal master dataset, so the page stays fast and readable.
How to read it
The shortlist lanes are meant to separate easy wins from rows that still need judgment.
Metadata-ready
Good demand plus visible response structure. These are the easiest records to spec first.
Demand leader
Usage is already strong, even if the metadata contract still looks thin.
Cross-channel demand
File demand is high and API-style demand is already visible, which can signal pressure for a cleaner delivery format.
Usage gap check
Demand looks large, but the join is not fully attached yet. These need verification before conversion planning.
Inspect first
Slice shape
This is the current shape of the file-to-API queue, not the whole merged catalog.