The public data your warehouse is missing

The unlock is geographic. The federal statistical system shares a common vocabulary of geography codes, and the Census Bureau publishes a free geocoder that translates the addresses a business already has into it. One call resolves a street address to its census tract and county; a batch call processes ten thousand addresses from a single upload; a reverse call works backward from coordinates.

Here is what that looks like against a real address. Wichita’s city hall resolves, in one call and under a second, to census tract 43.01 in Sedgwick County, Kansas, with the county code, block group, and coordinates attached.

That one translation makes everything else joinable. Demographics, business counts, income, and unemployment all key on the tract and county codes the geocoder returns, and the coordinates are exactly what the weather and traffic services take as input. A store list becomes a set of keys into the entire public statistical system.

The roster below is not hypothetical. Every source on it runs today as a cataloged connection on production Plexara deployments, where a retail operator’s agents use them for site evaluation and market analysis.

The American Community Survey answers who lives in a trade area: median household income, population, age structure, and housing, down to the block group, with pre-computed profile tables when percentages are all you need. County Business Patterns counts the competition by industry. Population Estimates says whether the market is growing. The Bureau of Economic Analysis adds per-capita income and county GDP; the Bureau of Labor Statistics adds the monthly unemployment series behind local spending power.

The National Weather Service contributes two different things: active severe-weather alerts for operations today, and the official point forecast for the week ahead. State transportation departments publish annual average daily traffic for road segments, which is the number a site-selection analysis wants first. Alongside the government sources sits Open-Meteo, an open archive of hourly weather history deep enough to backtest years of demand against the conditions that shaped it.

Put the join spine and the sources together and a market comparison stops being a project. The table below profiles three metro counties in a two-state trade area: five gateway calls, made while this article was being written, no key management, no format wrangling, and every number traceable to a federal table and vintage.

The numbers carry an analysis on their own. One county pairs the region’s highest median income with its lowest retail density per capita. Another trails it by nearly forty thousand dollars of median household income and runs the highest unemployment of the three. A revenue-per-store comparison across those markets that ignores this context is not a comparison; it is a coin flip attributed to management.

This is also what "instantly usable" means in practice. Nothing here was staged into the warehouse first. The agent asked each API for exactly the slice it needed, joined on the county codes, and the analyst read the result minutes after asking the question.

What makes these sources interesting is never any one of them. It is the join against private data, and weather is the sharpest example. The figure below is twelve weekends of real Wichita precipitation from the Open-Meteo archive, the kind of series an agent lays directly under a weekly sales curve.

For a seasonal retailer, one bar in that strip matters more than the rest: seven tenths of an inch of rain on the July 4 weekend itself, the highest-stakes trading days of the year. A demand dip on that weekend explains itself differently with the precipitation series in view, and a staffing plan for the next holiday reads differently next to the forecast of record and an active heat advisory. Questions that once justified a consulting engagement become questions an analyst asks before lunch.

When a result should outlive the session, it does. The agent exports the assembled dataset as a portal asset, queryable with SQL beside the warehouse, and the analysis it supports is shared from the portal rather than pasted into a thread.

An engineer could script any one of these calls in an afternoon, which invites the question of what the gateway adds. The answer is everything around the call. Each source is a cataloged connection whose operations the agent finds by intent, so "median household income for this tract" locates the right survey table without anyone memorizing variable codes. Requests are authenticated by the platform, and any credential a source requires stays server-side, never in a prompt. The Census Bureau’s data API now requires a registered key, which is exactly the kind of detail that belongs in a connection, not in every analyst’s environment.

The lessons accumulate too. The batch limits on the geocoder, the field mappings that differ between two states’ traffic services, the preliminary flag on the latest unemployment month: on the deployments described here, each of those lives in a knowledge page attached to the connection, teaching every future session what the first one had to learn.

The result is public data with the same standing as the warehouse: discoverable through the same search, governed by the same personas, documented in the same knowledge graph, and available to the same agent that can also act on what it finds. The best data your analysis is missing was free all along. What it cost was friction, and the friction is what the platform absorbed.