InfiniteRanks documentation

Build a cited-URL report from saved source records

Use exact source URLs to identify pages worth reading. Preserve the original returned URL before applying any deliberate normalization.

InfiniteRanks editorial team

Supported request

GET /api/v1/sources?limit=100 on https://app.infiniteranks.com with an Authorization: Bearer <read-only-key> header. Each source has a citation ID, answer ID, URL, domain and title. Answer metadata retains capture and citation completeness; answer eligibility is available through the answers resource.

A practical client workflow

Group by the source URL and count distinct answer IDs. Save the original URL with the observation cohort so a reviewer can open the page and inspect the claim it supports.

Limits and interpretation

Similar titles do not prove two URLs are the same page. Redirect and canonical handling needs explicit review, and a URL appearing with a competitor mention does not prove the page names that competitor. For list resources, use limit from 1 to 100 and continue with nextCursor. Keep raw record identifiers when presenting derived metrics.

Credential and error handling

Keep the key in trusted client or server configuration. It reads only its assigned workspace. Handle authentication failures without retry loops and respect Retry-After when the workspace request allowance is reached. Reading saved records does not trigger a paid provider call.

Sources and further reading

Sources explain the underlying standards. They do not endorse InfiniteRanks or guarantee a ranking outcome.

Be part of the conversation.

Explore a model response with your own provider key.