No license visible as far as I can tell. For EU markets, Eurostat publishes comparable occupational data through ISCO-08 and the EU's Joint Research Centre has their own AI exposure methodology — so the data is there to build it.

The lazy loading approach is smart. We've been publishing agent skills too and the context budget is a real constraint; six skills with reference docs would blow past 30k tokens if loaded eagerly.

Filtering at load time based on what the agent actually needs makes a huge difference. Curious if the orchestrator/executor split causes issues with state handoff between the two context forks.

Interesting approach. The annual churn stat seems brutal, I imagine that gets worse in certain categories (restaurants, pop-ups, seasonal businesses).

How do you handle conflicting signals? E.g., a business shows as open on Google, closed on Yelp, and the website returns a 404. Is there a confidence score in the API response or is it binary (exists/doesn't)

We have models which take all of this into account when producing the verdict. For enterprise clients we emit a calibrated confidence score. With public api we decided to start simpler. Also, we are not using Google data. I’m not a lawyer, but doing that for any maps-related company is simply against Google’s terms of use

FWIW it may be legal to break terms of use

It doesn't fit into our plans of building this

Fair enough. Just remember that in case terms of use bother you in the future. Consult your company's lawyer before doing it.

Completely agree - we have been in constant communication with them