InfiniteRanks documentation
Integration methods and their supported boundaries
Use exports for handoff and read-only REST or MCP for saved evidence. A connector name does not imply publication or write access.
Choose the smallest supported connection
For a one-time report, download the relevant CSV, JSON or printable report. For repeated server-side reads, use a scoped developer key. For a compatible assistant, use the MCP endpoint. All three should preserve the workspace, capture window and provenance needed to interpret the records.
Know what the public API cannot do
The public contract exposes workspace, prompts, answers and sources as read-only resources. It does not create content, change topics, send messages, launch paid collection or publish to a CMS. Authenticated app routes are separate internal application interfaces and should not be represented as a stable third-party write API.
Review external permissions
Keep credentials outside browser bundles and documents. Give an external system only the access needed for the agreed job. Test its output with one saved observation, then revoke the test key if it is no longer required. Verify any external CMS or messaging workflow independently before using it on client data.
Sources and further reading
Sources explain the underlying standards. They do not endorse InfiniteRanks or guarantee a ranking outcome.