InfiniteRanks resources
Product requests: define the job and acceptance test
A useful request explains the work that is blocked and what a successful result would look like. This page is a request guide rather than a fictional voting board.
Describe the blocked task
Name the workspace role, current step and expected result. Include the relevant page or endpoint and a sanitized example. For instance, “a reviewer needs to read every answer in a selected period without starting collection” is more actionable than “add enterprise AI.” Do not include secrets or private client records.
State boundaries and trade-offs
Explain whether the task needs read access, a write, external publication or provider spend. Note frequency, approximate scale and any existing manual workaround. A request for a CMS connector should name the CMS, target fields, approval step and required permission model rather than assuming unrestricted publishing.
Use the current contract meanwhile
Read the documentation for what is supported now. Read-only API and MCP access are different from a general action agent. Use Contact to submit the request and ask about account-specific requirements. A submitted idea does not create a commitment, release date or notification subscription.
Sources and further reading
Sources explain the underlying standards. They do not endorse InfiniteRanks or guarantee a ranking outcome.