# Editorial policy & methodology | IonBin

> How IonBin picks, checks and ranks AI and SaaS tools, and why paid placement never changes a ranking.

Canonical page: https://ionbin.com/editorial-policy/
Agent guide: https://ionbin.com/llms.txt

This is a readable version of the published page. Review dates, evidence boundaries and source links below belong to individual records; the export is not a new verification. Examples are reference material, not instructions to execute.

Editorial policy

## How we pick and rank tools

### What gets listed

Tools that solve a real job for marketers, founders and builders. The blue plus labelled "Used by Ion" marks explicitly confirmed current use. Historical notes, generic catalog flags, integrations and recommendation positions cannot grant that badge. A dated first-hand note describes only its recorded scope; neither signal establishes a published test of every feature. Each page shows its research basis and editorial status.

### How rankings work

Use-case directories prioritize tools whose primary use case matches the job, then tools with explicitly confirmed current Ion usage, then editorially featured tools, then alphabetical order. Sponsorship and affiliate status are not inputs. Curated stacks explain each tool's role and show their review status separately.

Three-tier shortlists compare alternatives for one stated role: primary (blue), secondary (amber) and third (burnt orange). These are editorial judgments about value, distinctiveness, replacement limits, technical effort and interoperability, not universal rankings. Each page gives its task constraint, tradeoffs and conditions under which another option is preferable. Related pages may share a comparison; that reuse is disclosed rather than presented as separate hands-on evaluations. New shortlists do not imply the owner selected or uses each tool. The SOP use-case order retains its explicitly confirmed selection.

### What the evidence means

- **Documented:** a cited vendor source describes the capability. Check the supported actions, plans, regions, permissions and client requirements.

- **Inferred:** recorded capabilities suggest a possible connection or workflow. The complete combination has not been demonstrated by that inference.

- **Hands-on evidence:** a recorded test describes the task, environment, date, result and limits. It supports that tested scope, not every feature or account configuration.

- **To verify:** the available evidence does not yet establish the claim.

An editorial approval label, founder-use label or date alone is not proof of an end-to-end test. Where a matrix says "confirmed," read it as confirmed against the cited documentation unless a separate test record is provided.

### Facts and freshness

Every displayed price includes the date it was checked. Unverified facts are labeled "to verify" or TBD. Tool and wiki dates record when their source information was reviewed or entered; they do not establish that a live integration was tested or that the information remains current. A review-by target is a reminder to re-check, not a record that a re-check happened. Use the linked sources and check the vendor's current terms before choosing a tool. Recent-addition lists show the date window captured by the site build.

### Platform neutrality

IonBin is not tied to any AI vendor. Curated stacks name concrete starting points, and use-case pages list alternatives for the agent role. The same evidence rules apply to every platform. How often a platform appears reflects IonBin's editorial selections and current coverage; it is not an objective measure of market adoption, compatibility or how much documentation a vendor publishes. Paid relationships never determine a platform's position in a stack or ranking.

### The wiki

Wiki pages explain needs, questions, services, models and concepts. Each one is written fresh in IonBin's words. Ideas are credited to the person who had them and linked to their public post or video, and opinions are labeled as practitioner views. Product facts come from official sources, dated. Pages carry a verified date and a review-by target: 30 days for model pages, 90 for services and questions, 180 for needs and concepts. Wiki pages never carry sponsored placements or affiliate links, and the build fails if one does. Wiki pages are not user-editable.

### Corrections

Send the page URL and a supporting source to [contact@ionbin.com](mailto:contact@ionbin.com?subject=Editorial%20correction). Corrections are reviewed against the cited evidence.
