InfiniteRanks documentation

List saved answer evidence with the public API

The answers resource returns persisted captures and provenance. It is not access to private consumer conversations or a request to generate new answers.

InfiniteRanks editorial team

Supported request

GET /api/v1/answers?limit=25 on https://app.infiniteranks.com with an Authorization: Bearer <read-only-key> header. Records include id, observationId, text, capturedAt, returnedModel, citationStatus, mentions, citations and an observation object containing state, eligibility, exclusion reason, surface, method, market, language and prompt revision.

A practical client workflow

Read each page until nextCursor is null, then select the intended capture window in your client. Preserve the full provenance when displaying an excerpt or calculating a rate.

Limits and interpretation

Pagination follows stable resource IDs, not a promise of newest-first chronological order. Do not call the first page the latest 25 answers without sorting the relevant complete dataset yourself. 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.