Review methodology

How every number in the main Nectar AI coverage is checked, which sources rank as primary, how live testing sessions are set up, and what triggers a page update.

Source hierarchy

Facts on this site are ranked by source in three tiers. The site's coverage scope and independence stance are set out on the about page, and the source discipline described below applies to every published claim. Tier one is nectar.ai itself: the pricing page, the terms of use, the privacy policy, the removal and complaints policies, and any founder statements on record. Tier two is named independent testing, meaning reviews at Robo Rhythms, Genius Firms, The Social Climb, AI Girlfriend Expert and Medium contributor write-ups, each with a publication month attached. Tier three is community reports at r/NectarAI and inside the Discord community, used to corroborate patterns rather than as standalone evidence.

What gets verified before publication

Every price on the site is verified against nectar.ai/pricing on the day the page is published or updated, and the verification date sits visibly next to the pricing block. Founder details, incorporation address and the $3.9 million seed round come from the Finance Magnates writeup of September 2024 and the PitchBook company profile, both linked in the main Nectar AI page. Feature counts, such as the 350+ character customisation options, are cross-checked against the platform itself and against the theresanaiforthat.com listing.

How memory and credit claims are tested

The 50 message memory ceiling on Nectar AI is not the site's own finding. It comes from two independent March 2026 reviews (Robo Rhythms and Genius Firms) that ran matched persona sessions and reported drift starting around 45 to 50 messages, corroborated by AI Girlfriend Expert's Ultimate tier writeup. The credit burn figure of $60 to $75 per month for a heavy Premium user comes from Robo Rhythms' March 2026 tracking. Where numbers on this site depend on someone else's test, the source is linked and the month is stated in-line.

Live session testing

Where a claim needs first-hand verification, a session is run under a controlled persona setup: a single test character with a fixed backstory, a 100 message log window, and message-by-message tracking of persona drift and credit spend. Sessions are logged for later audit but not published in full for privacy reasons. All session-derived claims are attributed as such rather than framed as universal truths, since sessions are one data point and different users can hit different rate-limits at different peak hours.

What triggers an update

The main Nectar AI page is re-checked against nectar.ai on a rolling basis, and any of the following triggers a page update the same day: a new pricing tier or a pricing change, a change to what each tier includes, a change to the credit system, a public content-policy change (removal, complaints or anti-trafficking updates), a company statement about video or voice moving out of beta, or a legitimate corrections request from a reader.

Dates and version control

Every content page carries a visible last-reviewed date and a JSON-LD dateModified. The datePublished value is immutable after first publication. When an update happens, the last-reviewed date and dateModified are pushed forward together, and if the substance of a claim has changed, the old version stays inside an internal changelog that reviewers or corrections senders can request through the contact on the author profile. Reader-side rules for accessing the site are on the terms of service, the data-handling side is on the privacy policy, and the 18+ access gate is described on the age verification page.

What is deliberately not measured

The site does not run automated scraping against nectar.ai, does not attempt to jailbreak the platform's filter for content-classification tests, and does not publish user-generated character logs without consent. Any claim about how the filter behaves comes from named third-party writeups or from prompts that would fall inside the platform's own published content policy. The site's own position on hosting depictions of sexually explicit content sits in the 2257 records-keeping statement. The methodology is deliberately narrower than what would be technically possible.

Sample coverage list

Coverage that runs through the same source-hierarchy and testing model includes the pricing tier breakdown, the memory-ceiling analysis, the credit wallet burn analysis, the marketing-vs-reality section, the character creator depth walkthrough, the mobile-app status, and the alternatives comparison. Everything is written under the editorial policy and reviewed by Melissa Blake before publication.

Last reviewed: October 6, 2026 · by Melissa Blake