InfiniteRanks resources
InfiniteRanks documentation
Find the current task guides for workspace setup, prompt management, answer review, reporting, content workflows and read-only developer access.
What is InfiniteRanks?
InfiniteRanks is a workspace for researching buyer questions, capturing AI answer evidence and reviewing content improvements. This retained help URL documents InfiniteRanks, not another vendor’s product.
documentationHow the InfiniteRanks evidence workflow works
The workflow moves from brand and question setup to collection, evidence review and a documented content decision.
documentationSign up and set up an InfiniteRanks workspace
Confirm the brand and measurement scope before saving the questions you want to track. Keep the demo and connected setup separate.
documentationGetting started checklist: verify your first evidence cohort
Use these checks to confirm setup, collection and interpretation before expanding coverage.
documentationAI search measurement glossary
Use these definitions when reading InfiniteRanks reports. They describe the measurement contract rather than a universal industry standard.
documentationRead the overview dashboard without losing the denominator
The overview summarizes loaded workspace evidence. Check the time window, platform and eligible counts before interpreting a percentage.
documentationUnderstand the visibility rate and its sample
The principal visibility measure is answer-level brand presence within an eligible sample. It is not a universal AI rank or market-share estimate.
documentationInterpret detected brand position in an answer
Position summarizes a detected order in saved answers. It should not be treated as an ordinary search-engine rank across every possible conversation.
documentationReview sentiment claims against the original answer
Treat sentiment as an interpretation of wording that needs a rubric. Stored answer evidence is the reference for review.
documentationInspect captured answers and their provenance
The answer view contains saved observation evidence. “Recent chats” here means captured records, not access to private conversations from real consumers.
documentationExport a visibility report with a clear history scope
Build a private report from loaded workspace evidence and show the capture window, platforms and missing results alongside the summary.
documentationManage tracked prompts and import a question set
Prompts are versioned buyer questions. Keep the wording, topic and tags deliberate so the history remains interpretable.
documentationConfigure the owned brand, aliases and competitors
Brand definitions determine which text mentions and domains the workspace recognizes. Confirm the entity before interpreting a report.
documentationOrganize prompt topics and tags without fragmenting the cohort
Use topics for the main buyer problem and tags for dimensions that cross topics. Consistent names make reporting easier to reproduce.
documentationQuery fan-out: distinguish suggestions from observed retrieval
A model may use related searches in a search-enabled workflow, but a suggested related question is not proof that a particular hidden search occurred.
documentationTrack citations with explicit completeness
Citation tracking records source links returned with saved answers. It should not infer unreturned sources or confuse a cited publisher with a mentioned brand.
documentationAnalyze cited domains and URLs
Use domain grouping to find recurring publishers and URL grouping to identify the actual pages worth reading.
documentationTurn a recommendation into an accountable page task
A useful recommendation names the evidence, affected page, owner and acceptance test. Review it before changing a product claim.
documentationUnderstand the bounded AI readiness check
The workspace technical audit inspects a homepage and default discovery files. It is a bounded diagnostic, not an exhaustive crawl or a ranking prediction.
documentationCreate content from approved research and a reviewed brief
Keep source approval, brief approval and draft review as separate decisions. A generated draft is editable work, not verified publication.
documentationInterpret content checks as an editorial diagnostic
Content checks flag structure, readability, source links and answer focus. They are not a search-engine score or proof that an AI system will cite a page.
documentationReview competitor source gaps without inferring page content
A source gap is a pattern in saved answer evidence. Inspect the cited page before deciding what caused the pattern or which edit to make.
documentationMaintain brand context for accurate research and writing
Brand context should supply verified product facts and wording constraints. It must not become a place to store unsupported claims or secrets.
documentationManage organization members and invitations
Organization roles control membership administration. Review the intended account and workspace access before sharing client evidence.
documentationChoose the correct workspace and preserve its measurement context
A workspace groups brand definitions, prompts and saved evidence. Confirm the workspace whenever changing settings or exporting a report.
documentationUnderstand billing status, plan estimates and collection allowances
Read the current connected billing state before assuming a public plan is an active subscription. Provider costs and app plan allowances are separate concepts.
documentationRun a reviewed AI search workflow
Use a sequence of evidence review, source approval, content review and follow-up. Keep external publishing as an explicit action.
documentationIntegration 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.
documentationMove reviewed InfiniteRanks content into WordPress
Use the reviewed export workflow and WordPress preview. InfiniteRanks does not claim an automatic WordPress publishing connector in this implementation.
documentationPublish an approved content export through your CMS
Treat export and publication as two separate steps. Use your CMS’s own access controls, preview and approval process.
documentationShare evidence with Slack and compatible AI tools
Use a reviewed export or a read-only assistant connection. No built-in Slack message delivery is promised by this guide.
documentationConnect Claude or another MCP client to InfiniteRanks
Add https://app.infiniteranks.com/mcp as a remote MCP server. Claude signs in with OAuth; other clients can use a read-only workspace key.
documentationInfiniteRanks read-only REST API
Read saved workspace context, prompts, answers and sources with a scoped Bearer key. Learn pagination, limits and the unsupported write boundary.
documentationAuthenticate with a scoped read-only workspace key
Create, store and revoke a workspace Bearer key. Understand rate limits, browser-origin restrictions and the difference from app sessions.
documentationDerive brand positions from saved answer evidence
InfiniteRanks exposes answer evidence rather than a standalone public brand-rankings endpoint. Calculate only the metric your selected eligible cohort supports.
documentationBuild a cited-domain report from the sources API
Read saved citations and group their domains in your client. The public API does not expose a pre-ranked top-domains endpoint.
documentationBuild a cited-URL report from saved source records
Use exact source URLs to identify pages worth reading. Preserve the original returned URL before applying any deliberate normalization.
documentationList saved answer evidence with the public API
The answers resource returns persisted captures and provenance. It is not access to private consumer conversations or a request to generate new answers.
documentationFind an individual saved answer by ID
There is no separate public answer-detail path in this contract. Locate the record in the paginated answers resource and preserve its evidence fields.
documentationRead workspace and brand context
Use the workspace route to identify the scope of a read-only key and the brands referenced by answer records.
documentationList saved prompts and their latest revisions
The prompts resource returns saved question records with latest revision and tag information. Reading it does not start collection.
documentationFind a saved prompt in the read-only prompt resource
Locate a prompt by ID in the paginated list. The public contract does not include a separate GET-by-ID prompt route.
documentationDerive prompt topics from the current prompt library
Topics are saved on question revisions. Read the prompt resource to build a topic list; there is no standalone public topics resource.
documentationRead brands through workspace context
The public workspace route includes brand metadata. It is the supported route for resolving brand IDs in saved answers.
documentationFind a brand in the workspace metadata response
Locate the brand ID inside workspace.brands. There is no separate public brand-detail endpoint in the supported contract.
documentationRead assigned prompt tags through the prompts API
Prompt records expose their assigned tags. The public API does not publish a standalone complete tag-catalog route.
documentationRemove a topic from use through prompt review
There is no public topic-delete endpoint. Topics live on saved question revisions rather than an independently writable developer resource.
documentationCreate a topic through the prompt editing workflow
The public developer contract does not expose topic creation. Add a meaningful topic when creating or reviewing questions in the authenticated app.
documentationChange prompt topic assignments with a review trail
No public PUT topic endpoint is supported. Review current questions in the app when their topic assignment needs to change.
documentationPlan a partial topic correction safely
The read-only API does not accept PATCH requests for topics. A partial correction must use the app’s supported editing workflow.
documentationCreate prompts in the app or supported import flow
There is no public POST prompts endpoint. Use the authenticated prompt interface and its reviewed import operation.
documentationRevise a tracked prompt without losing historical meaning
The public API is read-only and does not expose a PUT prompt operation. Edit a prompt through the authenticated app.
documentationMake a bounded prompt metadata change
No public PATCH prompt endpoint is supported. Use app controls for the intended state, wording or tag change.
documentationRetire a question while preserving its answer evidence
The public read-only API does not expose DELETE prompts. Use the app’s supported prompt lifecycle controls; pausing can retain history without new scheduled work.
documentationRun a reviewed collection from the authenticated app
Developer keys and MCP tools cannot launch paid collection. Start supported collection through the connected app after reviewing availability and limits.
documentationRemove a tag after reviewing its prompt assignments
The public API does not expose DELETE tags. Manage tag lifecycle through the authenticated workspace controls.
documentationCreate a useful prompt tag in the workspace
No public POST tags endpoint is supported. Use authenticated tag controls and an agreed naming rule.
documentationRename a tag without obscuring its reporting meaning
The public contract has no PUT tag endpoint. Edit supported tag metadata through workspace controls.
documentationCorrect tag metadata through the supported interface
PATCH tags is not a public developer operation. Use the authenticated app for a bounded name or color correction.
documentationAdd a brand or competitor through workspace setup
The read-only developer API does not expose POST brands. Use supported setup and workspace controls to maintain the tracked entities.
documentationReview a brand identity correction
No public PUT brand endpoint is supported. Correct identity through the authenticated workspace workflow.
documentationMake a bounded brand metadata correction
The public API has no PATCH brand operation. Use app controls for the supported correction and verify the saved result.
documentationRetire a competitor without rewriting earlier comparisons
There is no public DELETE brand endpoint. Use supported app settings for the current tracked set and preserve evidence needed for historical reports.
documentationDistinguish display filtering from changing tracked brands
No public visibility-toggle endpoint is supported. A display filter and an entity-definition change have different analytical effects.
documentationReview 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.
Start with the task
Complete setup, inspect the first answer and verify the measurement scope before expanding collection. The results section explains rates, position, sentiment interpretation and report history. Tracking guides cover question revisions, identity, topics and tags. Citation guides keep source relationships and completeness explicit.
Use the supported contract
The public API reads workspace, prompts, answers and sources; MCP exposes four read-only tools. Retained write-operation help pages explain the supported app workflow instead of inventing endpoints. Integration guides distinguish manual CMS export from automatic publishing. Check live account availability and billing messages alongside these documented boundaries.
Sources and further reading
Sources explain the underlying standards. They do not endorse InfiniteRanks or guarantee a ranking outcome.