Sixtyfour

Sixtyfour

Sixtyfour turns one identifier—email, name, phone, or company—into a fully cited profile of a person or business using autonomous research agents.

62/100MonitorFree planFreemium

Sixtyfour is worth a trial if your team runs repeat investigations, not one-off lookups. Chief strengths in our view are cited sourcing on every verified record and relationship, Lattice accumulating findings across cases into network intelligence, and a documented Research API path via a single POST to /people-intelligence. Named alternatives differ in kind: Exa and Parallel return candidate pages you still have to resolve, and Sixtyfour's own RECON benchmark write-up positions it against Exa, Parallel, and Grok. The benchmark numbers are vendor-published but externally validated by HUD with a public methodology, so they are checkable—run your own test cases before standardising. The

Verified 4h ago · liveness 62/100 · cite: rightaichoice.com/tools/sixtyfour

Best for
  • Trust and safety teams investigating fraud rings, banned accounts, and rented gig-worker accounts
  • Compliance and financial-crime analysts running enhanced due diligence, adverse media, and alert triage
  • Workforce identity teams checking candidates and contractors before interviews or onboarding
  • Investigations teams that need one identifier resolved into a full, cited subject footprint
Not ideal for
  • Casual one-off people lookups where an enterprise investigation platform is overkill
  • Builders who only need raw candidate pages and want to do the resolution themselves
  • Teams that need every finding to stay portable if they leave the platform, since Lattice intelligence lives in Sixtyfour
Visit Website

IntermediateFor an analyst, first value usually comes within the first investigation: you supply one identifier, the agents run, and a cited profile returns in the same session—no data ingestion project first. For a product team wiring the Research API, expect an integration-sized effort around the single POST to /people-intelligence, choosing a tier and the struct of fields you want, plus handlingWeb · APIAPI availableVerified 4h ago
Pricing
Free plan
FreemiumFree tier3 hidden costs
Learning curve
Intermediate
For an analyst, first value usually comes within the first investigation: you supply one identifier, the agents run, and a cited profile returns in the same session—no data ingestion project first. For a product team wiring the Research API, expect an integration-sized effort around the single POST to /people-intelligence, choosing a tier and the struct of fields you want, plus handling
Runs on
WebAPI
API available
Who it's for
Trust and safety analyst at a marketplaceCompliance analyst running enhanced due diligenceProduct engineer embedding research via API
Live sentiment
Is Sixtyfour actually worth it?

We scan live Reddit threads, YouTube comments, X posts, G2 reviews and other communities — and hand you an honest verdict in under a minute.

  • Honest verdict, not marketing
  • Real pros & cons from real users
  • Attributed quotes with receipts
Run a free scan

3 free scans · no card needed

Skip it if

Skip Sixtyfour if you only need occasional one-off people lookups and are happy to resolve raw candidate pages yourself—its value compounds across repeat investigations and a shared Lattice graph, not a single query.

The 30-second take
Biggest gripe

API usage runs on tiers like 'micro' with a struct of fields you declare, so wide field sets on high-volume pipelines cost more per call than a narrow lookup—model your expected field count before committing.

Price reality

Functionally it competes with search-and-fetch layers like Exa and Parallel—cheaper per query because they hand you candidate pages—and with enterprise investigation platforms that bundle analyst seats. Sixtyfour's Research API is documented with a 'start free, scale to millions' framing, so the cost question at volume is metered API usage, not seats. Getting current pricing means contacting the

In short

Sixtyfour — Sixtyfour turns one identifier—email, name, phone, or company—into a fully cited profile of a person or business using autonomous research agents. Best for Trust and safety teams investigating fraud rings, banned accounts, and rented gig-worker accounts, Compliance and financial-crime analysts running enhanced due diligence, adverse media, and alert triage, Workforce identity teams checking candidates and contractors before interviews or onboarding. Free to use.

What's new in Sixtyfour

Checked today

Across the latest 5 updates: 5 news mentions.

What people actually say about Sixtyfour — is it worth it?

We scanned public community sources for Sixtyfour on Aug 29, 2026 and could not establish that the discussion we found is about this tool rather than something else sharing its name. Our own analysis of that scan says the posts were off-subject. Rather than publish a sentiment score built on the wrong subject, we publish nothing here and re-run the scan.

Viability Score

62/100
Monitor

How well maintained and how widely used is Sixtyfour? Built from what the vendor actually publishes (docs, changelog, tutorials, integrations, pricing), whether the site is live, and how much real users discuss it. How we calculate this

Recent activity
90
Traction
100
Site health
95
User sentiment
45
What the vendor publishes
0

Last calculated: October 2026

How we score →

Key Features

  • Identifier-based research starting from name, email, phone, username, wallet, or company
  • Autonomous AI agents browse, extract, and cross-reference open web, dark web, official records, and documents
  • Cited evidence attached to every verified source, record, and relationship
  • Social account detection and linking across X/Twitter, GitHub, and Reddit
  • Entity affiliation mapping across companies, roles, and jurisdictions
  • Business registration searching with state registry and registered agent address matching
  • Agent filing checks against corporate registries
  • Dissolved entity resolving and dissolution record lookup
  • Directorship verifying against archival filings
  • Risk signal detection for sanctions, PEP status, court records, and adverse media
  • Dark web exposure checks against breach databases and leaked credentials
  • Digital footprint gap analysis, such as flagging a months-long online absence
  • Lattice shared graph accumulating findings across investigations
  • Network intelligence including high-risk associations, second-degree exposure, and cluster density
  • Fraud cluster detection linking applicants via shared IP address and device ID

About Sixtyfour

FreemiumIntermediateAPI availableWeb · API

Sixtyfour is an identity intelligence platform for teams whose findings have to survive scrutiny. You start with any single identifier—an email address, a name, a phone number, a company, a username, or a wallet—and autonomous AI agents browse, extract, and cross-reference the open web, dark web, official records, and unstructured documents. What comes back is one cited intelligence profile rather than a list of links. Feature coverage includes business registration searching against state registries with registered-agent address matching and agent filing checks, dissolved entity resolving with dissolution record lookup, directorship verifying against archival filings, social account detection across platforms such as X/Twitter, GitHub, and Reddit, entity affiliation mapping across companies and jurisdictions, risk signals for sanctions, PEP status, court records, and adverse media, and dark-web exposure checks against breach databases and leaked credentials. Digital footprint gap analysis—such as flagging a months-long online absence—is a documented signal-reading workflow. Two things separate it from a search wrapper. The first is Lattice, a shared graph where every investigation deposits findings, so repeated lookups accumulate network intelligence: high-risk associations, second-degree exposure, cluster density, and fraud clusters linked by shared IP address or device ID. The second is the Research API, where a single POST to /people-intelligence embeds the agents into onboarding flows, case-management systems, or data pipelines. Sixtyfour reports leading the RECON people-research benchmark with +70.6% weighted accuracy at XHigh and +54.3% at High, 85.9% precision and 84.4% recall across 140 people and 514 verified fields, externally validated by HUD with a published methodology. Practically, Sixtyfour is built for recurring investigation work—trust and safety, enhanced due diligence, workforce identity, and investigations—not for casual one-off lookups. Search-first tools such as Exa and Parallel return candidate pages; Sixtyfour resolves them into a cited dossier and a reusable graph, but that graph lives inside Sixtyfour.

Behind the Verdict

Sixtyfour is aimed at a specific buyer: the trust and safety, compliance, workforce identity, and investigations team that has to show its work. Where it earns its place is the combination of cited evidence and Lattice. Every verified source, record, and relationship resolves into one profile with the evidence attached, which is the difference between a defensible case file and a folder of links. Lattice is the more interesting half: your first investigation answers a question, and your ten-thousandth changes which questions you can ask, because each case deposits into a shared graph that surfaces high-risk associations, second-degree exposure, and cluster density. The vendor's own example—six applicants linked via IP 203.0.113.145 and device dev-4579, scored as a ring—shows the shape of that output. Feature breadth is real rather than decorative: business registration searching against state registries with registered-agent address matching and agent filing checks, dissolved entity resolving and dissolution record lookup, directorship verifying against archival filings, sanctions and PEP screening, court records, adverse media, dark-web exposure checks against leaked credentials, and digital footprint gap analysis such as a months-long online absence. The Research API matters for product teams—a single POST to /people-intelligence with a tier and a struct of fields lets you embed the agents into onboarding or case management, and the vendor says it starts free and scales to millions, with a field_confidence flag for per-field confidence. Benchmark-wise, Sixtyfour reports leading RECON at +70.6% weighted accuracy on XHigh and +54.3% on High, 85.9% precision and 84.4% recall over 140 people and 514 verified fields, externally validated by HUD. Treat those as vendor-favourable but methodologically public—review the study against your own use cases. Where it does not fit: casual one-off people lookups, builders who only want raw candidate pages and prefer to do resolution themselves, and teams that need every finding to remain portable after leaving the platform, since Lattice intelligence lives in Sixtyfour. Two practical cautions we would put in front of any buyer. First, official-records coverage varies by jurisdiction, so validate against your own geography before standardising a workflow on it. Second, the API is framed for embedding and batch-style research rather than live continuous monitoring—teams expecting streaming alerts should confirm that capability directly rather than assume it. The recent September 2026 field guides on email, phone-number, and account-linking investigations are a useful signal of how the vendor wants the product used: reading one identifier carefully, in a defined order, with the decision documented.

Researching Sixtyfour? Get your full AI stack in 60 seconds.

Free, no signup — tell us your goal and get tools matched to your budget & existing stack.

Real-world workflow fit

Concrete scenarios for the personas Sixtyfour actually fits — and what changes day-one when you adopt it.

Trust and safety analyst at a marketplace

A cluster of new seller accounts looks synthetic. You feed each applicant's email and phone number into Sixtyfour, let the agents check social accounts, breach exposure, and business registrations, then review the Lattice view for links via shared IP 203.0.113.145 or device IDs.

Outcome: The accounts resolve into one operator cluster with cited evidence attached, so you can ban the ring and document the decision with sources rather than suspicion.

Compliance analyst running enhanced due diligence

A counterparty's director needs checking before onboarding. You start from the name and company, pull directorship records against archival filings, business registration status, sanctions and PEP hits, court records, and adverse media into one profile.

Outcome: You get a source-backed dossier you can hand to an exam, instead of stitching together registry printouts and news searches by hand.

Product engineer embedding research via API

Your onboarding flow needs a risk check without leaving the app. You POST a name or email to /people-intelligence with a struct declaring the fields you want—title, email, LinkedIn, bio—and set field_confidence to true.

Outcome: The response returns the fields with per-field confidence, so your workflow can auto-clear low-risk applicants and route the rest to a human queue.

Use Cases

Limitations

  • Source coverage depth, especially for official records, varies by jurisdiction and should be validated against your own geography before you standardise a workflow on it.
  • The Research API is described as self-serve and framed for embedding and batch-style research rather than live continuous monitoring, so teams expecting streaming alerts should confirm that capability directly.
  • Benchmark claims against Exa, Parallel, and Grok are vendor-published—though the RECON methodology is public and the results are externally validated by HUD, so review the study against your own use cases.
  • Lattice is the core differentiator and it is also the lock-in: intelligence accumulated in the shared graph lives inside Sixtyfour.

as of 2026-10-09

Verification history

We have re-verified Sixtyfour 8 times since . Each pass re-reads the vendor's own pages and re-checks every listed field against that evidence; passes where nothing had changed are marked as such.

  1. — re-verified summary, description, our verdict, our analysis, pricing model, pricing tiers, features, integrations, who it suits, who should skip it
  2. — re-checked, vendor evidence unchanged
  3. — re-checked, vendor evidence unchanged
  4. — re-verified summary, description, our verdict, our analysis, pricing model, pricing tiers, features, integrations, who it suits, who should skip it
  5. — re-checked, vendor evidence unchanged
  6. — re-verified summary, description, our verdict, our analysis, pricing model, pricing tiers, features, integrations, who it suits, who should skip it

Showing the 6 most recent of 8 verification passes.

Free to cite with attribution — this page re-verifies continuously.

Hidden costs & gotchas

What the public pricing page doesn't put in bold. Captured from pricing-page footnotes, contract terms, and recurring complaints.

  • API usage runs on tiers like 'micro' with a struct of fields you declare, so wide field sets on high-volume pipelines cost more per call than a narrow lookup—model your expected field count before committing.
  • Official-records and registry depth varies by jurisdiction, so covering additional countries can mean extra validation work or gaps rather than a flat per-seat cost.
  • Every case you run deposits into Lattice, which deepens the value but also makes the accumulated graph non-portable—factor in the cost of recreating context if you ever leave.

Where the pricing makes sense

The company stage and team size where Sixtyfour's pricing actually pencils out — and where peers do it cheaper.

Functionally it competes with search-and-fetch layers like Exa and Parallel—cheaper per query because they hand you candidate pages—and with enterprise investigation platforms that bundle analyst seats. Sixtyfour's Research API is documented with a 'start free, scale to millions' framing, so the cost question at volume is metered API usage, not seats. Getting current pricing means contacting the

Setup time & first value

How long it actually takes to get something useful out of Sixtyfour — broken out by persona, not the marketing-page minute.

For an analyst, first value usually comes within the first investigation: you supply one identifier, the agents run, and a cited profile returns in the same session—no data ingestion project first. For a product team wiring the Research API, expect an integration-sized effort around the single POST to /people-intelligence, choosing a tier and the struct of fields you want, plus handling

Switching to or from Sixtyfour

How to bring data in from common predecessors and how to get it back out — written for the switcher, not the buyer.

Migrating in
  • →From manual OSINT research: replace spreadsheet-and-tab workflows by starting from the same identifiers in Sixtyfour and keeping the cited profile as the case record.
  • →From search-first APIs like Exa or Parallel: keep them if you only need candidate pages, but route the resolution step—dossier, relationships, risk signals—through Sixtyfour's people-intelligence endpoint.
  • →From static people-data vendors: move the entities Sixtyfour covers natively (registrations, directorships, sanctions, PEP, adverse media, breach exposure) and keep the static vendor only for fields Sixtyfour does not
Migrating out
  • ↗To Exa or Parallel: possible only for the retrieval layer—you lose the cited dossier and the Lattice graph unless you rebuild resolution in-house.
  • ↗To an enterprise investigation platform: export case notes and re-run your highest-value subjects there, accepting that network intelligence accumulated in Lattice does not come with you.

Resources & Guides

Tutorials & Learning

YouTube returned 6 videos for “Sixtyfour”, and we withheld 6: 6 could not be judged, because “Sixtyfour” is a single word that other videos use for other things. We are showing none, because we could not prove any of them are about Sixtyfour.

Official links

Tools that pair well with Sixtyfour

Common stack mates teams adopt alongside Sixtyfour, with the specific reason each pairing earns its keep.

Featured Head-to-Head Comparisons

Alternatives to Sixtyfour

View all
Reddit Research Mcp

Reddit Research Mcp

Hosted MCP server that turns Reddit threads into cited, structured research data.

PaidTry
Socialprofiler

Socialprofiler

Socialprofiler runs an AI social media background check on a person and returns a readable report from public Facebook, TikTok, Instagram and X activity.

Contact SalesTry
Marvin User Research

Marvin User Research

Marvin is an AI-native customer insights platform that runs AI-moderated interviews and delivers cited answers from your research repository.

FreemiumTry

Frequently Asked Questions

Used Sixtyfour? Help shape our editorial sentiment research.