> ## Documentation Index
> Fetch the complete documentation index at: https://tokenterminal.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> To query the Token Terminal data catalog, read https://tokenterminal.com/docs/catalog/agents-manual.md first. It is the whole catalog as one page: table naming grammar, key columns, partition and cluster rules, units, additivity, and the tables that are documented but not served yet.
> Never query a catalog table on a time bound alone. Also filter its cluster key, which you read from INFORMATION_SCHEMA.COLUMNS; an empty result means the object is a view, whose pruning contract is on its page. Compute is billed to the caller's own Google Cloud project.

# Funding region agreement

> How often a wallet's region of activity matches its funding venue's expected band.

One row per funding venue, chain, funding confidence and region confidence, for wallets that venue funded. `hit_rate` is `hits` divided by `wallets_with_region`, null where the venue's expected band is not known.

## Columns

<table>
  <thead>
    <tr>
      <th width="230">Column</th>
      <th width="120">Type</th>
      <th>Description</th>
    </tr>
  </thead>

  <tbody>
    <tr><td><code>funding\_venue\_project\_id</code></td><td>STRING</td><td>Venue that funded the wallets in this row.</td></tr>
    <tr><td><code>chain\_id</code></td><td>STRING</td><td>Chain the wallets are on.</td></tr>
    <tr><td><code>chain\_family</code></td><td>STRING</td><td>Chain family the chain belongs to, from <code>dimensions.chains</code>.</td></tr>
    <tr><td><code>funding\_confidence</code></td><td>STRING</td><td><code>high</code>, <code>medium</code> or <code>low</code>, the wallets' funding confidence tier.</td></tr>
    <tr><td><code>region\_confidence</code></td><td>STRING</td><td><code>high</code>, <code>medium</code> or <code>low</code>, or null where region has no signal.</td></tr>
    <tr><td><code>wallets</code></td><td>INT64</td><td>Wallets funded by this venue, on this chain, at this funding confidence tier.</td></tr>
    <tr><td><code>wallets\_with\_region</code></td><td>INT64</td><td>Of those, wallets with a non-null region.</td></tr>
    <tr><td><code>expected\_band</code></td><td>STRING</td><td>Region band this venue is expected to fall in. Null where the expectation is not known for this venue and chain family.</td></tr>
    <tr><td><code>hits</code></td><td>INT64</td><td>Of <code>wallets\_with\_region</code>, wallets whose region matched <code>expected\_band</code>.</td></tr>
    <tr><td><code>hit\_rate</code></td><td>FLOAT64</td><td><code>hits</code> divided by <code>wallets\_with\_region</code>. Null where <code>expected\_band</code> is null.</td></tr>
  </tbody>
</table>

## Sample queries

<Tabs>
  <Tab title="One venue's hit rate by chain">
    `hit_rate` compares a venue's wallets against its own expected band, so filtering to one venue reads how consistent it is across chains and confidence tiers.

    ```sql theme={null}
    select
        chain_id,
        funding_confidence,
        region_confidence,
        wallets_with_region,
        hit_rate
    from `reports_accounts.funding_region_agreement`
    where funding_venue_project_id = 'coinbase'
    order by chain_id, funding_confidence
    ```
  </Tab>

  <Tab title="Hit rate across every venue, at high confidence">
    Summing `hits` and `wallets_with_region` before dividing avoids averaging an average across venues of very different sizes.

    ```sql theme={null}
    select
        funding_venue_project_id,
        sum(hits) as hits,
        sum(wallets_with_region) as wallets_with_region,
        safe_divide(sum(hits), sum(wallets_with_region)) as hit_rate
    from `reports_accounts.funding_region_agreement`
    where funding_confidence = 'high'
      and expected_band is not null
    group by funding_venue_project_id
    order by hit_rate desc
    ```
  </Tab>

  <Tab title="Venue name alongside the hit rate">
    `funding_venue_project_id` joins `dimensions.projects` for the display name.

    ```sql theme={null}
    select
        projects.name,
        agreement.chain_id,
        agreement.funding_confidence,
        agreement.hit_rate
    from `reports_accounts.funding_region_agreement` as agreement
    join `dimensions.projects` as projects
        on agreement.funding_venue_project_id = projects.project_id
    where agreement.expected_band is not null
    order by agreement.hit_rate desc
    limit 50
    ```
  </Tab>
</Tabs>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.