InfiniteRanks documentation
InfiniteRanks read-only REST API
The public REST API reads persisted workspace evidence. It does not start provider collection, mutate prompts or publish content.
Supported resource routes
Use GET https://app.infiniteranks.com/api/v1/workspace for workspace and brand context. Use GET /api/v1/prompts, GET /api/v1/answers and GET /api/v1/sources for paginated records. These routes use a workspace-scoped read-only key; they do not use your browser session as the developer authentication method.
Pagination contract
List routes accept only limit and cursor. limit is an integer from 1 to 100 with a default of 50. Results use {data: [...], nextCursor: string | null}. Pass the returned cursor unchanged for the same workspace and resource until it is null. Cursors are not interchangeable across resources. The workspace route accepts no query parameters.
Evidence fields and limits
Prompts include the latest revision and assigned tags. Answers include text, capture time, returned model, citation status, observation provenance, mentions and citations. Sources include their answer relationship. Do not infer a complete cohort from the first page or a universal score from raw records. The configured rate limit is 60 requests per workspace per minute; handle 429 using Retry-After.
Read-only is a deliberate boundary
There are no public POST, PATCH or DELETE resource operations in this contract. Authenticated application routes are separate and not a published automation API. Use app controls for editing and collection, or read-only MCP for supported assistant access. Keep keys outside client bundles and revoke any exposed credential.
Sources and further reading
Sources explain the underlying standards. They do not endorse InfiniteRanks or guarantee a ranking outcome.