Sources
The public sources behind AltAPIs API records, repository rankings, model lists and attributed documentation previews.
API directory metadata
The connected public-apis/public-apis and Public API Lists repositories supply API names, descriptions, categories and reported access facts. APIs.guru adds one preferred OpenAPI definition per API, with specification and documentation links. Unreported authentication, HTTPS and CORS are left unconfirmed. Duplicate source URLs and matching names on the same documentation host are merged; this cannot detect every rebrand or alias. These are directory-reported attributes, not the results of an AltAPIs integration test. The entry’s provider/source link is preserved for checking current documentation and terms. The directory and linked provider material can have different licenses and usage conditions.
public-apis/public-apis on GitHub
GitHub discovery
Configured public sources include GitHub’s daily, weekly and monthly Trending pages and repository search queries for stars, forks, creation dates and selected topics. A search list captures at most 100 entries; Trending can return fewer. A repository found in several lists shares one detail record. The combined star ranking covers the recently observed imported sample, not a continuously updated copy of every repository on GitHub.
Hugging Face model discovery
Configured Hub queries capture trending models, recent downloads, cumulative likes, recently created repositories and selected model tasks. Each query is bounded to 100 entries. Reported downloads cover the Hub’s rolling 30-day metric, not lifetime usage or unique users. Task, library, license, architecture and parameter fields are shown only when supplied. These lists do not import an evaluation leaderboard or infer hardware requirements from popularity.
README and model-card previews
A separate bounded worker reads eligible public README or model-card text from approved GitHub and Hugging Face endpoints. It stores a short attributed excerpt of at most 150 words, selected headings, source-mentioned links and an observation timestamp—not a complete republished README. API entries whose source points directly to a GitHub repository can use this preview too. Other provider documentation is linked, not fetched by an unrestricted website crawler. Repository code and model weights are not executed or downloaded.
Refreshes, backlog and missing documents
API directory feeds default to hourly checks; repository and model lists remain daily. Three API feeds are fetched concurrently with conditional requests, bounded response sizes and upstream backoff. Failed or suspiciously shrunken feeds retain their last good records; removal requires owner review. A successful documentation preview becomes due again after 24 hours; provider budgets, cooldowns and the size of the queue can make the actual interval longer. New entries may therefore show a queued preview while already linking to the original document. Temporary failures retain the last usable snapshot with its date. Missing, access-restricted, hidden or opted-out documentation is not replaced with invented content.
Stronger claims need stronger evidence
Current primary provider documentation, official API references, model cards, release notes and policy pages are preferred for details beyond the imported fields. A source-reported statement is not an independent endorsement. Pricing, availability, security, benchmark results, production compatibility and rights to reuse or train on material require their own evidence. Opening a source link is a starting point for that evaluation, not a grant of permission.
Review and source concerns
Stored observation dates, selected metadata and recorded changes help reviewers understand updates. An archive record is not an immutable full copy of a provider’s website. Upstream API removals enter owner review, while source-ranked repositories and models can remain as dated detail records after leaving a top list. Authors and visitors can request corrections or raise documentation rights and opt-out concerns through the published contact routes.