Attribution requirements apply to public Community use from the start
of plan enforcement. Integration verification and the quota bonus are
planned and are specified here so you can prepare. See the
changelog.
When attribution is required
“Public display” means showing scores, rankings, prices, or derived charts to anyone outside your organization — a website, an app, a newsletter, a public dashboard, a bot reply. Internal tools do not need attribution on any plan.
Attribution is a licensing requirement, not a technical one: the API does not block unattributed Community use, but unattributed public use is a terms violation that can lead to
entitlement_suspended. See Acceptable use.
How to attribute
Any of these satisfy the requirement. Choose the one that fits your surface.- Badge (recommended)
- Source link
- Plain text
A signed badge image linking back to the source. Badge loads from your allowed host are the observation evidence we record for an integration. See Embeds and badges.
- Visible without interaction, on the same screen as the data or in a clearly labeled footer.
- Names “LLM Stats” and, where links are possible, links to
llm-stats.comor the model page. - Not hidden by
display: none, tiny fonts, or same-color text. - Does not imply LLM Stats endorses your product.
Verified integrations
An integration is a public place where you show LLM Stats data. Declaring it and getting it verified will earn a fixed quota bonus once the bonus ships (see the rollout status above).
The bonus is fixed — it does not grow with traffic — and will be reflected in
X-Quota-Limit and /v1/account when an integration becomes verified.
Lifecycle
Only
verified and grace carry the bonus. Declaring an integration alone changes nothing.
What we measure
What we record automatically today:- Observation days: each UTC day on which your badge is loaded with a
Referermatching the allowed host counts as one observed day. Referer-less loads render but are not evidence. - Eligibility: an
observedintegration with at least 7 observed days and a badge load within the last 30 days is recorded as eligible for review. Eligibility does not change the state or grant the bonus by itself. - Clicks:
/goredirects are counted per day so you and we can see that the badge sends real traffic.
verified:
- Presence: the declared URL shows the badge or a link to
llm-stats.comcarrying yourutm_source. - Visibility: the element is rendered (not
display: none, not off-canvas, contrast above a minimum). - Consistency: the page continues to show the data it attributes.
Re-verification, removal, and appeal
- A
graceintegration returns toverifiedwith no loss of bonus once the attribution is restored and confirmed. - A
revokedintegration can be re-declared after fixing the issue. It restarts atdeclared. - Deleting an integration removes its bonus immediately.
- If you believe an integration was rejected or revoked in error, reply to the notification email with the URL and a screenshot. We review appeals within five business days.
- We may revoke integrations that violate acceptable use — for example a badge on a page that strips attribution from the data itself, or a URL farm created to collect bonuses.
Privacy and analytics disclosure
Badge and embed requests reach our servers, and we log the requesting IP,Referer, and user agent to verify integrations and to compute aggregate traffic. We do not set cookies from badges or embeds, and we do not use the logs for advertising. If your privacy policy lists third-party assets, list api.llm-stats.com. Retention of raw logs is 90 days.
If you prefer not to send visitor requests to us, use a plain source link instead of a badge. Plain-link integrations can still be verified from page presence and referral traffic to llm-stats.com, though verification may take longer.