Skip to main content

Autoverse

Command-line client for Autoverse literature search. The default API is https://app.autoverse.nz.

pipx install autoverse
autoverse login
autoverse whoami
autoverse search "HER2-low breast cancer" --domain medicine --limit 5
autoverse resolve doi:10.4143/crt.2023.1138
autoverse related pmid:38291745 --via references --limit 5
autoverse usage
autoverse topup
autoverse update --check

autoverse login opens a browser confirmation page on the Autoverse site (email or GitHub). Credentials go into the OS keyring. Named profiles use --profile and do not share the file fallback with default.

whoami shows the signed-in account and remaining credits. usage shows credits and recent usage. topup prints the registered email and the three store pack links; it does not charge. autoverse --help shows the Autoverse wordmark.

autoverse update --check checks PyPI without modifying the installation. Human terminals may show one cached update hint per 24 hours; --json --quiet output never receives ambient notices. Set AUTOVERSE_NO_UPDATE_NOTICE=1 to disable the human hint.

CI and scripts can store a console platform key instead:

autoverse login --token sr_live_...
# or
export AUTOVERSE_API_KEY="sr_live_..."

Do not commit the key. Agents use the same CLI commands and machine-readable --json output; official scenario Skills compose the CLI rather than a separate tool protocol.

For automation, put global flags before the command and parse stdout only:

autoverse --json --quiet search "retrieval augmented generation" --limit 5

Failures are one JSON object on stderr with error.code, request_id, and retryable; stdout remains empty.

Curated paper commands now keep the same public research fields across search, resolve, batch, and related: full authors, publication types, public identifiers, per-source citation counts, OA information, subjects, dates, and venue metadata. Internal routing, billing, provider status, provenance, and raw upstream objects remain available only through the API escape hatch. authors also returns aliases, paper count, citation counts, H-index, and external IDs.

An empty successful search still exits 0. If every usable source failed and the server returns only partial=true warnings with no papers, the CLI emits ALL_SOURCES_UNAVAILABLE on stderr and exits 1 instead of presenting an empty result as success.

Requires Python 3.12+. The package and the command are both autoverse.

Internal design lives under doc/ (start at doc/README.md). Official system and scenario Skills live under skills/, not inside the wheel.

Release files for autoverse 0.3.2

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for autoverse 0.3.2
File Size Uploaded
autoverse-0.3.2.tar.gz 25.5 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for autoverse 0.3.2
File Interpreter ABI Platform
autoverse-0.3.2-py3-none-any.whl Python 3 none any Details

Total release size: 58.1 kB

Release files / autoverse-0.3.2.tar.gz

Download URL autoverse-0.3.2.tar.gz
Size 25.5 kB
Tags Source
SHA-256 checksum
How to use checksums
11cdd2b3b7218251b4c4843bb3e9b70a70ea2265c6243cdf5fa969f057e85604
BLAKE2b-256 checksum
How to use checksums
cdd20c305e1cce181281f03656ef83cb21510a46419540e214c1dd780775c1c2
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Aug 31, 2026.

Transparency log

Release files / autoverse-0.3.2-py3-none-any.whl

Download URL autoverse-0.3.2-py3-none-any.whl
Size 32.6 kB
Tags Python 3
SHA-256 checksum
How to use checksums
c8210e899fca9e95f2a4d2d4a5a41ce93fe91377c8d241aea85a5ae38d2d71ff
BLAKE2b-256 checksum
How to use checksums
409f1ea0903b5682c8c755e7a82ad93e7cddd9001c01415c53165cc83c7aaa2a
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Aug 31, 2026.

Transparency log

Release history Release notifications | RSS feed

0.3.6

2 release files

0.3.5

2 release files

0.3.4

2 release files

0.3.3

2 release files

This release

0.3.2 This release

2 release files

0.3.1

2 release files

0.3.0

2 release files

0.2.1

2 release files

0.2.0

2 release files

0.1.0

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page