InfiniteRanks documentation

Read workspace and brand context

Use the workspace route to identify the scope of a read-only key and the brands referenced by answer records.

InfiniteRanks editorial team

Supported request

GET /api/v1/workspace on https://app.infiniteranks.com with an Authorization: Bearer <read-only-key> header. The result has a workspace object with id, name, market, language, createdAt and brands. Brand fields include id, name, domain, aliases, owned and color.

A practical client workflow

Request the workspace with the Bearer header before reading answers. Resolve mention brand IDs against this brand list and retain the workspace ID with your exported dataset.

Limits and interpretation

The route accepts no query parameters. A key cannot choose another workspace by adding a workspaceId parameter. Context is metadata, not proof that every configured provider is available. 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.