That’s interesting!
Because I recently spoke with an Airtable enthusiast and they said that “we need a Databricks or Snowflake for Airtable!” Because the analytic side of things is definitely not present with Airtable.

Both are incredibly expensive options and likely overkill.  I should not have to fetch full record details for every record/table in order to get basic stats like (“How many records match where field = X?”).  These stats are _already_ getting computed by Airtable to power the WebUI -- all I’m asking for, is exposing that _existing_ logic in the official Airtable API.

Like, the closest thing to built-in stats would be:

1. Build a formula.
2. Fetch all records but set the output field to ONLY emit a RECORD_ID().
3. Count the number of distinct RECORD_ID()’s.

This is like gathering wood, tinder, and rubbing 2 sticks together to start a fire -- rather than being given a lighter.  Night and day.