InfiniteRanks documentation
Find an individual saved answer by ID
There is no separate public answer-detail path in this contract. Locate the record in the paginated answers resource and preserve its evidence fields.
Supported request
GET /api/v1/answers?limit=100 on https://app.infiniteranks.com with an Authorization: Bearer <read-only-key> header. The id identifies the saved answer; observationId identifies its collection observation. The nested observation records the exact question revision, method and eligibility.
A practical client workflow
Paginate answer records, find the required answer ID and retain its text, capture time, model and citation links together. A local cache may index IDs after a complete authorized read.
Limits and interpretation
Do not invent GET /api/v1/answers/{id} or a query filter the API does not accept. A displayed answer without its question revision can be misread after a prompt edit. 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.