InfiniteRanks documentation

Review duplicate brand definitions before consolidating

The public API does not expose a brand-merge operation. Duplicate entities need a deliberate review rather than an invented automated endpoint.

InfiniteRanks editorial team

Supported way to perform the task

Compare names, domains, aliases and historical answer references. Decide whether they are truly the same entity or separate products. Export the evidence and use supported settings or contact the team for the appropriate correction.

What needs review

A careless merge can double-count mentions or erase the meaning of earlier comparisons. Keep original IDs in any review record and do not rewrite saved capture provenance.

Developer access boundary

The supported public resources are GET /api/v1/workspace, /api/v1/prompts, /api/v1/answers and /api/v1/sources. A read-only key cannot perform this write action. Do not reuse authenticated internal app requests as a promised public automation contract.

Verify the result

Read the relevant current records after saving through the app and retain the IDs, review date and evidence needed to explain the change. A client-side preview, successful export or generated instruction is not confirmation that a workspace mutation occurred.

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.