InfiniteRanks documentation

Read brands through workspace context

The public workspace route includes brand metadata. It is the supported route for resolving brand IDs in saved answers.

InfiniteRanks editorial team

Supported request

GET /api/v1/workspace on https://app.infiniteranks.com with an Authorization: Bearer <read-only-key> header. workspace.brands includes the brand ID, name, domain, aliases, ownership flag and color. These fields support identity review and report labeling.

A practical client workflow

Read workspace context and create an ID-to-brand lookup before displaying mentions from /api/v1/answers. Show the ownership flag separately from competitor status in your reporting logic.

Limits and interpretation

A name match can still be ambiguous. A domain citation is separate from an answer-text mention. Do not claim a public /brands route exists merely because workspace context contains brands. 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.