Company profile · 4 min read
Antinuous: autonomous research agents with a still-forming product
Antinuous is building autonomous research agents for R&D, discovery, education and knowledge work, with current public packaging and pricing still unspecified.
Published · Updated
Antinuous is presenting a broad ambition: make autonomous research available to people who have a hard question but do not want to build a custom research harness. The company’s public materials are clear about the desired end state—agents break down a question, research it, test ideas and repeat—but light on a current packaged product or pricing path.
What it does
The YC profile describes autonomous research agents for research, development, discovery, education and knowledge work. It says the system should take a question, decompose it, research the answer, test new ideas and simulate environments with elastic compute. The current homepage expands that into a platform where a person can ask a question once and agents perform the surrounding research and experimentation.
The public YC launch linked from the profile is for an earlier product, Salesgraph, a Slack-native sales-research and deal-context tool. That history is useful context for the founders’ direction, but it should not be confused with the current Antinuous product. The checked public pages do not publish pricing, a concrete onboarding flow, supported integrations or an example customer deliverable for the current platform.
Why I’d look closer
The potential buyer is a technical founder, R&D team, educator or research-heavy operator who repeatedly asks questions that require multiple sources, experiments and iterations rather than one answer. The company’s pitch is attractive because it targets the setup tax: every new problem currently requires someone to wire tools, data, evals and a record of what happened.
The tradeoff is scope. “Any hard question” is a compelling north star, but it also makes quality, permissions, provenance and stop conditions harder to judge. A research agent that can test ideas or operate tools needs an explicit boundary around what it may access, how it records evidence and when a human must approve the next step.
What I’d ask
What can a new customer run today, and what remains a research prototype? Can a user define a fixed source set, eval and budget before the run begins? Are every claim, experiment and failed branch recorded? Which actions stay simulated or local, and which can touch external systems? What is the first repeatable workflow where Antinuous has evidence of value?
My editorial take
Keep Antinuous on the watchlist for teams with a clear research bottleneck and the technical ability to define their own evaluation. I would not buy the vision as a general-purpose answer engine yet. The next convincing proof is a narrow, replayable workflow with inspectable sources, bounded compute and a useful artifact at the end.
Quick facts
| Field | Sourced detail |
|---|---|
| Product direction | Autonomous research agents for R&D, discovery, education and knowledge work |
| Buyer | Research-heavy founders, R&D teams and educators |
| Current evidence | Public ambition and company history; current package and pricing not published |
| Related prior launch | Salesgraph appears in the YC profile; not treated as the current Antinuous product |
| Main question | What narrow research workflow can a buyer run and replay today? |
Sources checked
| Source | Checked |
|---|---|
| YC company profile | 2026-09-19 |
| Antinuous homepage | 2026-09-19 |
| Salesgraph launch linked from YC | 2026-09-19 |
Cohort context
Antinuous is listed in Spring 2026. In our 2026-09-18 directory snapshot, 112 of 193 listed companies in that cohort have YC’s primary industry label B2B (58.0%). This is a current-directory comparison, not an original intake count or a performance ranking. Nine-cohort dataset.
Public website snapshot
Observed 2026-09-19T16:16:04.134Z in raw homepage HTML. This records visible metadata and advertised links, not agent execution or product quality.
| Signal | Homepage observation |
|---|---|
| Product description metadata | Observed |
| Canonical link | Not observed in this response |
| H1 or H2 heading | Not observed in this response |
| Typed structured data | Not observed in this response |
| Docs/developer link | Not observed in this response |
| Pricing link | Not observed in this response |
| llms.txt link | Not observed in this response |
| Markdown alternate | Not observed in this response |
Public observations · Collection method. Missing links here do not establish that a capability or file is absent elsewhere.
