What 149 trending AI and developer tools call
As of 2026-10-09 — counted from the results published that day
We read 149 repositories that appeared in tech news (GeekNews, Hacker News) and on GitHub trending. Each was read at one commit without running it, and every result is pinned to that commit. This note looks at the 149 together.
The four states
| State | Repositories |
|---|---|
| Calls external APIs | 65 |
| Calls external APIs · local option | 14 |
| No external APIs found | 46 |
| Needs review | 24 |
A little over half, 79, have code that calls an external API. For 14 of them the code has a way to run the same call against a local server (Going local with one line). 46 were read to the end of a set scope with no external API call found (what that means), and 24 say neither, because part could not be read (Why “Needs review” remains).
The APIs called most
29 providers from the pricing catalog came up. By number of repositories, the top ones are:
- OpenAI — 35
- Anthropic Claude — 28
- Google Gemini API — 18
- OpenRouter — 14
- DeepSeek — 12
- Groq — 11
Of the 192 repository–provider pairs, 183 (95%) call the provider with the user's own API key; the rest use OAuth or cloud account sign-in instead of a key. “It is open source, so it is free” and “you need your own key to use it” can both be true. The full provider list is at Repositories by API.
When one repository calls many APIs
Split by how many places they call (service addresses outside the catalog included), the 79 repositories that call external APIs look like this:
- 1: 26
- 2–4: 21
- 5–9: 18
- 10 or more: 14
Of the 14 with ten or more, 8 put several providers behind the same feature and let the user pick one. In such a repository “calls ten” is closer to “can call one of ten”; the result page groups those calls under one feature as “Optional”. Also, 29 of the 79 call only services outside the catalog. This site has not checked those services' pricing, so result pages show “No pricing info” for them.
How languages differ
| Language | Calls external APIs | Local option | None found | Needs review |
|---|---|---|---|---|
| Python | 19 | 4 | 13 | 2 |
| TypeScript | 21 | 5 | 7 | 4 |
| Rust | 12 | 0 | 6 | 2 |
| C · C++ | 3 | 0 | 5 | 9 |
The language is the main language GitHub gives the repository. Python and TypeScript have many AI apps built around model APIs, hence many “Calls external APIs”. C and C++ have many “Needs review” because this site does not read source in those languages: when unread code is a real share, it does not say “No external APIs found”.
How to read these numbers
These numbers are counts, not judgements. Calling external APIs does not make a tool bad, and none found does not make it safe. For any repository the result page shows the call sites by commit-pinned line numbers, and if something is wrong, “This result is wrong” on the result page reaches us and we fix it. The rules are in the methodology.