not read yet
Use
- For
- Medical professionals and students exploring disease information across 7,000 conditions with symptoms, exams, and treatments.
- Price
- Price not read
- Activity
- Actively maintainedsite updated yesterday
- Company
- Domain since 2025domain registered
- Runs as
- API
- Search diseases by symptoms for differential diagnosis
- Compare diseases using structured medical data
- Access ICD-10 and ICD-11 coding information
- Domain since2025domain registered
Figure and bar: visits/mo, estimate · year: online since
- #1
Bright Data
Provides web scraping APIs, proxy infrastructure, and datasets for extracting structured data from websites at scale.
81.9kActiveFrom $1 per use2014 - #2
docAnalyzer v2
Analyzes documents across multiple files and formats, generating cited outputs like spreadsheets and PDFs from multi-turn conversations.
1.3kActiveFrom $8/mo2023 - #3
Peek
Turns Excel, CSV, JSON, SharePoint and Salesforce data into interactive charts and dashboards with AI.
5ActiveFrom $5/user/mo2024 - #4
Reportr
Chat interface to explore databases, generate reports, and surface insights through conversational queries.
2not readFrom $20/user/mo - #5
MedrecproMCP · sign-in
Imports DailyMed SPL zip files into a database, then serves them through a REST API, MCP server and label renderer.
2not read— - #6
zinfradb
Stores and searches vectors, graphs, and text in a single database binary.
EmergingMaintained—
What is Nosology.AI?
Database of 7,000 diseases with symptoms, exams, treatments, and prevalence data across continents in multiple languages. It is listed in the Atlas under Data.
Who is Nosology.AI for?
Medical professionals and students exploring disease information across 7,000 conditions with symptoms, exams, and treatments.
Do people use Nosology.AI?
Emerging.
Is Nosology.AI still maintained?
Actively maintained: site updated yesterday.
What are alternatives to Nosology.AI?
In Data, by use: Bright Data, docAnalyzer v2, Peek, Reportr, Medrecpro, zinfradb.
Not quite it? Describe the job
betaFive tools from the Atlas that fit it, each judged against what you wrote.
How we read a tool
No votes, no reviews, no vendor claims. Every week a crawler reads each tool's own site and a few public registries, and the words on the card are bands over what it read.
- Use: visits to the site (estimated), installs from npm and PyPI, presence in Chrome's usage report.
- Activity: the newest release on GitHub, npm or PyPI; the newest dated page on the site; open roles on a public jobs board.
- Price: the vendor's own pricing page, read with the date. A figure is printed only when it is on that page.
- The line and the use cases are written by us from the homepage, one tool at a time, and refused when they repeat the vendor's marketing.
How AI assistants read each site — the reading vendors ask us about — is on each tool's own visibility page.