---
title: "Contact and corrections"
description: "How providers and readers can correct a record, dispute a classification, or reach the people maintaining the catalog."
canonical_url: "https://freeinferencing.com/contact/"
md_url: "https://freeinferencing.com/contact.md"
last_updated: "2026-10-06"
---

# Every record is correctable.

> Bring one current first-party source that settles the disputed field.

## What can change

- Rate limits, quotas, and credit amounts
- Rotating model lists
- Retention, training, and routing terms
- Free-tier and privacy classifications
- Offers that launched, changed, or ended
- Names, endpoints, operators, and source links

## What a correction needs

Identify the provider record, the field that is wrong, the proposed correction, when the replacement source took effect, and a current provider-owned pricing, documentation, limits, catalog, or governing-terms link. A launch post or marketing page is a lead rather than proof; when an announcement and the governing terms disagree, the more specific governing document wins. Dashboard-only values are labeled as such instead of guessed.

For a quota correction, include the unit, time window, account or plan, reset behavior, and what happens after exhaustion. For a model change, include the exact machine-readable ID and the live catalog or documentation URL. For privacy, identify the service and plan covered by the terms rather than relying on a company-wide policy that may not govern developer prompts.

## How a correction lands

The record is re-audited against first-party sources and updated in the published source dataset. Because the site is generated from that dataset, the provider page, catalog ordering, summary counts, Markdown mirror, and discovery files update together. The earlier claim remains in the record's audit history, so the change is inspectable rather than silent.

## How to make the report decisive

Use the provider record ID or exact name, identify the field that should change, summarize the replacement fact, and link the newest provider-owned page that governs it. If the evidence exists only inside an account, provide the page title, capture date, account type, and enough reproducible detail to label the limitation honestly. Do not send credentials, private account data, or sensitive prompts. Conflicting sources are useful when both are linked and the report explains which appears newer or more specific.

## Boundaries

Records are not removed merely because a classification is unflattering, and a free offer is not called private without plan-specific evidence. Watchlist and excluded entries move when evidence changes, not on request alone. The no-free directory is a dated finding that no provider-funded hosted offer was verified for the scoped product; it is not a judgment about the provider or the value of its paid services.

## Where to send it

- [Hackers In the Loop Discord](https://discord.gg/3Qs2uejUf9)
- [@iammrduncan on X](https://x.com/iammrduncan)

The full source dataset is available at [data-raw.yaml](/data-raw.yaml), with a machine-oriented guide at [data.md](/data.md).

## Sitemap

See the full [semantic sitemap](/sitemap.md) for every page and markdown mirror.