Checks
The remediation intake: asking APIs.io to re-profile a listing, and reading where that request stands.
Ask APIs.io to (re)check a provider listing.
File a request against a listing — a listing is wrong or stale, a score looks incorrect, or a company is not in the catalog yet. A check can target a PROVIDER (the default) or a slice of the catalog — an industry, tag, area, or a company's estate — for an industry roster missing an obvious member, a tag that has drifted, or an area whose ranking looks wrong. A slug the catalog does not hold is never refused: for any target type it is queued as a request to ADD that thing, with near matches returned alongside so a typo is still visible. This does NOT score anything on the spot. A check means re-profiling the provider and running the full enrichment pipeline against their live surface, which a person runs by hand, so it queues work rather than returning an answer. Influence plan. Reporting an error costs nothing — the report_correction MCP tool and an issue on the provider's own repo at github.com/api-evangelist/{slug} need no key and no plan; what the Influence plan buys is queueing the re-profiling work itself.
Ask APIs.io to (re)check a provider listing. › Request Body
target_typeWhat slug names. Defaults to provider. estate is named for the company the estate roots at (e.g. cisco) — the API has no estates resource, so that root company is what gets validated, not the estate's membership.
slugThe target slug. A provider slug (e.g. stripe) by default, or an industry/tag/area/estate slug when target_type says so.
urlThe company or developer-portal URL — use this when there is no listing yet. Providers only.
kindDefaults to recheck when the slug is already in the catalog and profile when it is not. A slug we do not hold is a request to profile it, not an error.
contactEmail to notify when the status changes. Optional, and validated if given; without it there is nothing to notify, so keep the returned id and poll.
notesWhat is wrong, or what to look at. The more specific, the faster it is worked.
Ask APIs.io to (re)check a provider listing. › Responses
The queue was unreachable, so nothing was filed. Deliberately a 200 with queued: false and the human fallback rather than a 5xx — a request for a correction is never dropped silently.
okqueueddetailThe check requests you filed.
The status of one check request.
Where a check stands, with any notes an operator marked shareable. Internal triage notes are never returned — they are written candidly, and publishing them by default would make them either useless or unkind. Influence plan.
path Parameters
idThe id returned when the check was filed.
The status of one check request. › Responses
The check record.
idstatuskindslugurlcreated_atupdated_atclosed_atPresent only once the request is closed.
Operator notes explicitly marked shareable. Internal triage notes are never included.
queueA standing reminder that checks are worked by hand, not computed on demand.