Skip to main content

Automated literature surveys.

Project description

Automated literature surveys


PyPI Status Code Coverage License LastCommit Contributor Covenant

Developer:

Getting Started

Get a Semantic Scholar API key

The first thing to do is to request an API key for Semantic Scholar. Note that this can only be used for research purposes. Here are some suggested answers for the form:

> How do you plan to use Semantic Scholar API in your project? (50 words or more)*

Generate literature surveys using large language models with relevant papers in context, using the `auto-survey` Python package. It re-writes the desired research topic into 10 different queries, pings the /paper/search endpoint for each of those for papers, and feeds those papers to a language model to generate a literature survey. It is only for my own private use.

> Which endpoints do you plan to use?

The /paper/search endpoint.

> How many requests per day do you anticipate using?

Around 100 requests per day.

When you have it, you create a file called .env in your current directory with the following content:

SEMANTIC_SCHOLAR_API_KEY="<your key here>"

If you already had a .env file, you can just append the line above to it.

Set up an LLM API key

Next, you need to set up an API key for the large language model (LLM) that you want to use. The default model is gpt-4.1-mini from OpenAI, which requires you to have an OpenAI API key, and again add it to your .env file:

OPENAI_API_KEY="<your key here>"

Installing and Running

Firstly, you need to install the pandoc and weasyprint packages, which allows for generating the final PDFs. You can do this on MacOS using Homebrew:

brew install pandoc weasyprint

On Ubuntu you can install them with apt:

sudo apt install pandoc weasyprint

Then, the easiest way to use the auto-survey package is as a uv tool. You can start generating a literature survey using the following command:

uvx auto-survey "<your topic here>"

This both installs the package and creates the literature survey, which typically takes about 10 minutes. With the default model, it costs about $0.05 per survey.

You can see all the available options by running the following command:

uvx auto-survey --help

Using Different Model Providers

The package supports all of LiteLLM's providers, including OpenAI, Anthropic, Google, xAI, local models, and more. You can simply set the --model argument to the model you want to use. For example, to use Claude Sonnet 4.5 from Anthropic, use

uvx auto-survey "<your topic here>" --model "claude-sonnet-4-5"

Some providers require you to prefix the model ID with the provider name. For instance, to use the Grok-3-mini model from xAI, you need to use

uvx auto-survey "<your topic here>" --model "xai/grok-3-mini"

All of this is documented in the LiteLLM provider documentation. If you use a different provider, you need to set different environment variables. See the LiteLLM provider documentation for more information on which environment variables to set.

Custom Inference API

You can also run the package with a custom inference API. In this case you need to set the --base-url argument with the URL to the inference API, and also set the --api-key-env-var argument with the name of the environment variable that contains the API key for the inference API. This variable must again be set in the .env file:

<value-of-api-key-env-var>="<your key here>"

Lastly, when using custom inference APIs, you need to use a custom prefix as well, dependending on what kind of inference server you're using. If it is running with vLLM, you need to use the hosted_vllm/ prefix, for instance, and Ollama models use the ollama_chat/ prefix. See the LiteLLM provider documentation for more information on which prefixes to use.

Project details


Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

auto_survey-0.2.5.tar.gz (702.4 kB view details)

Uploaded Source

Built Distribution

If you're not sure about the file name format, learn more about wheel file names.

auto_survey-0.2.5-py3-none-any.whl (20.2 kB view details)

Uploaded Python 3

File details

Details for the file auto_survey-0.2.5.tar.gz.

File metadata

  • Download URL: auto_survey-0.2.5.tar.gz
  • Upload date:
  • Size: 702.4 kB
  • Tags: Source
  • Uploaded using Trusted Publishing? No
  • Uploaded via: uv/0.11.19 {"installer":{"name":"uv","version":"0.11.19","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"macOS","version":null,"id":null,"libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}

File hashes

Hashes for auto_survey-0.2.5.tar.gz
Algorithm Hash digest
SHA256 3cb68d43ec0f8dce84377e4a161227fe8b014b4025cce4bd86bacd3cf05225ee
MD5 8fa31e2f34f763b36a5898ca82d4dca2
BLAKE2b-256 0d009ae7b2f33d8a49811d78c264f2b263dce875c0470c23fcf1a344c9bfe84e

See more details on using hashes here.

File details

Details for the file auto_survey-0.2.5-py3-none-any.whl.

File metadata

  • Download URL: auto_survey-0.2.5-py3-none-any.whl
  • Upload date:
  • Size: 20.2 kB
  • Tags: Python 3
  • Uploaded using Trusted Publishing? No
  • Uploaded via: uv/0.11.19 {"installer":{"name":"uv","version":"0.11.19","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"macOS","version":null,"id":null,"libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}

File hashes

Hashes for auto_survey-0.2.5-py3-none-any.whl
Algorithm Hash digest
SHA256 630c7c40d3a4fb13029fe1774f63c6803036abc6df59e5ca3f8a00b576a02a87
MD5 8ee37ab81f6825ba3bc9ec9b38a526e7
BLAKE2b-256 0fd792cf950cf6638e2d49580ead2b590deeda223fe5542547fc3f6f3d699ba3

See more details on using hashes here.

Supported by

AWS Cloud computing and Security Sponsor Datadog Monitoring Depot Continuous Integration Fastly CDN Google Download Analytics Pingdom Monitoring Sentry Error logging StatusPage Status page