Foller.me is a Twitter/X analytics dashboard (est. 2009) that queries the Twitter API on-demand to display profile statistics, topic clouds, hashtag analysis, sentiment detection, and activity patterns for any public Twitter handle. It is not a people-search or background-check tool. Zero of its data overlaps with Phase 0b's core fields (addresses, phones, relatives, employer, AKAs). Five independent research tracks all returned the same verdict: OMIT.
This is a category error — evaluating Foller alongside actual people-search tools like EnformionGO, BeenVerified, or FastPeopleSearch is like evaluating a calculator as a phone. It's the wrong tool type entirely.
| Category | Max | Score | Rationale |
|---|---|---|---|
| Data Coverage | 3 | 0.0 | Zero Phase 0b fields — no addresses, phones, relatives, employer, AKAs, or any people-search data |
| Accuracy | 2 | 0.3 | No accuracy framework, no identity matching (requires prior Twitter handle), zero reviews on any platform |
| API / Automation | 2 | 0.0 | No API (/api returns 404), no programmatic access, web-only manual lookup |
| Pricing | 2 | 0.2 | Free, but irrelevant — you can't buy what doesn't exist |
| Unique Value vs Alternatives | 1 | 0.0 | No unique value for background checks; alternatives (SocialBlade, Twitonomy) do the same thing better |
| TOTAL | 10 | 0.5 |
Coverage: No published US profile count. Foller does not maintain a database — it queries Twitter's API on-demand per lookup. Coverage bounded by Twitter's public API.
Platforms: Twitter/X only. No Facebook, Instagram, LinkedIn, TikTok, or any other platform.
Identity matching: None. Foller requires a prior-known Twitter @handle. No reverse lookup by name, email, phone, or address. You cannot search for "John Smith" — you must already know his Twitter handle.
Accuracy claims: None published. No methodology, no confidence scores, no false-positive analysis.
After 16 years online (since 2009), the complete absence of any review or community discussion is itself noteworthy — it suggests very low usage volume.
Data source fragility: All data is derivative of Twitter's API. Any change to Twitter/X API access, rate limits, or pricing directly breaks Foller's entire product. Twitter has repeatedly tightened API access since Elon Musk's acquisition.
https://foller.me/api returns HTTP 404| Phase 0b Field | Foller Provides? |
|---|---|
| Full name | Twitter display name only (self-reported, unreliable) |
| Current address | No |
| Previous addresses | No |
| Phone numbers | No |
| Email addresses | No |
| Relatives/associates | No |
| Employer/occupation | Twitter bio only (self-reported) |
| AKAs/aliases | No |
| Age/DOB | No |
| Criminal records | No |
| Property records | No |
| Tool | Type | Score | Verdict |
|---|---|---|---|
| EnformionGO | Data broker aggregator | ~7/10 | CONSIDER |
| BeenVerified | Consumer people search | ~6/10 | CONSIDER |
| FastPeopleSearch | Free people search | ~5/10 | CONSIDER |
| ContactOut | Professional email finder | ~4/10 | CONSIDER (limited scope) |
| Classmates | School/yearbook records | ~3/10 | OMIT |
| Foller.me | Twitter analytics | 0.5/10 | OMIT |
Foller.me has zero relevance to Phase 0b background checks. It is a single-platform Twitter analytics dashboard — useful for social media managers evaluating Twitter accounts, but completely irrelevant for people-search or identity verification.
Should Phase 0b expand to include social media profile discovery? This is a reasonable question for a future evaluation cycle, but Foller is the wrong vehicle for it. If social media discovery becomes a Phase 0b requirement, tools like Pipl, Spokeo, or Social Catfish (which aggregate across platforms and support reverse lookup by name/email/phone) would be more appropriate candidates.
Five independent research tracks were dispatched via kanban_create and completed in parallel. Each track performed web-based research against primary sources (foller.me pages, API endpoints, robots.txt) and secondary sources (review platforms, OSINT communities, API directories). The synthesis worker verified the homepage independently via direct HTTP fetch and compiled all findings.