gptr.dev valid

GPT Researcher

GPT Researcher is an open-source autonomous AI research agent that conducts comprehensive deep research on any topic, gathers information from dozens of trusted sources in parallel, and produces long-form research reports with inline citations. It is the #1-ranked deep-research system on Carnegie Mellon University's DeepResearchGym benchmark and powers production research workflows for thousands of teams.

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-21T23:29:19.069Z. Cached copy · Source on gptr.dev

# GPT Researcher

> GPT Researcher is an open-source autonomous AI research agent that conducts comprehensive deep research on any topic, gathers information from dozens of trusted sources in parallel, and produces long-form research reports with inline citations. It is the #1-ranked deep-research system on Carnegie Mellon University's DeepResearchGym benchmark and powers production research workflows for thousands of teams.

## What it is

- An autonomous agent (not a chatbot) that plans, searches, validates, and writes.
- Pluggable across LLMs (OpenAI, Anthropic, Google, Mistral, DeepSeek, local models via Ollama, LiteLLM) and search providers (Tavily, Bing, Google, DuckDuckGo, SearXNG, etc.).
- Open source under MIT, available as a Python package, a self-hosted FastAPI server, a Docker image, and an MCP (Model Context Protocol) server.
- Designed to be embedded inside other agents, IDEs, and workflows.

## When to use it

- When a single LLM call or web-search tool is not enough and you need a *researched* answer with sources.
- When you need long-form reports (executive summaries, market analyses, due-diligence briefs, literature reviews) generated end-to-end.
- When an LLM agent (Claude, ChatGPT, Cursor, custom) needs a "deep research" sub-tool to fetch grounded, cited context.
- When you want full control over the LLM, search engine, and data sources (including private / internal docs).

## Primary capabilities

- `deep_research` - autonomous multi-source research with planning, source validation, and citation tracking.
- `quick_search` - low-latency web search with snippets across any GPT Researcher-supported retriever.
- `write_report` - generate long-form research reports from accumulated research context.
- `get_research_sources` - list all sources gathered during a research run.
- `get_research_context` - return the full accumulated research context.
- Streaming output via WebSockets and Server-Sent Events.

## Use cases

- Investment & equity research (company / sector deep-dives)
- Market and competitive intelligence
- Academic literature review and citation gathering
- Due-diligence reports and risk analyses
- Briefing documents for executives and product teams
- Long-form content generation grounded in real sources

## Constraints and important notes

- Deep research runs typically take 30 - 60 seconds per query. This is the trade-off for grounded, multi-source reports.
- Quality depends on the configured LLM and retriever. The defaults (OpenAI + Tavily) work out of the box; everything is swappable.
- GPT Researcher requires Python 3.11+ and at least one LLM API key plus one search-API key.
- Output includes inline citations, but the user / calling agent is responsible for final fact-checking.
- The hosted research at gptr.dev is a marketing landing page; the *product* is the open-source agent at github.com/assafelovic/gpt-researcher and the MCP server at github.com/assafelovic/gptr-mcp.

## Key links

- Homepage: [gptr.dev](https:
…

Related sites

Other listed sites in Science and research. See the whole category →

Machine-readable: GET /v1/resolve?q=gptr.dev · GET /v1/domain/gptr.dev · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for gptr.dev:
1. POST https://agentwebmap.com/v1/sites/gptr.dev/claims and keep claim_id and claim_secret private.
2. Publish the proof: add the line "AgentWebMap ownership: <token>" (token from step 1) to https://gptr.dev/llms.txt, or use the DNS, meta-tag or well-known method the response describes.
3. POST https://agentwebmap.com/v1/sites/gptr.dev/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/gptr.dev).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.