Skip to main content

Node Mantis

Node Mantis automates web tasks with AI. Describe a goal in plain English and it carries the goal out in a real Chrome browser on your machine, navigating, clicking, typing and reading the page the way a person would, then returns the result to your code. Use it from Python, Node.js or the command line; it uses your Google Chrome (or provides Chrome for Testing when Chrome is missing), and new accounts start with $10 in free credit.

python -m pip install --upgrade node-mantis
export NODEMANTIS_API_KEY="sk_live_<copy-from-dashboard>"
import asyncio
from nodemantis import NodeMantis


async def main():
    async with await NodeMantis.start() as mantis:
        result = await mantis.run(
            "Go to https://sandbox.nodemantis.com. Open Travel & Adventure, add one copy of Journey to the Center of the Earth to the cart, then open the cart and report the title and quantity.",
        )
        print("Status:", "success" if result.ok else "failed")
        print(result.reason)


asyncio.run(main())

Quickstart · Docs · API reference · Get an API key · Pricing · Website

Secrets

Pass passwords, API keys and one-time codes with secrets. The values stay in the local Node Mantis process; only their names are shared, and Node Mantis types a value into the page when the task asks for it by name.

result = await mantis.run(
    "Sign in as the user ada with the account password.",
    secrets={"account_password": os.environ["ACCOUNT_PASSWORD"]},
)

On the command line, pass --secrets account_password and set NODEMANTIS_SECRET_ACCOUNT_PASSWORD. Names use letters, digits and underscores, and you can point at one in a prompt as <secret:account_password>. The value never leaves your machine while it is typed, and password fields are hidden in the page snapshot. Use secrets with fields that hide what you type: a page that shows the value as readable text exposes it like any other page content. See Secrets.

Browser

Node Mantis drives Google Chrome. It uses, in order: CHROME_PATH, your installed Google Chrome, or Chrome for Testing (Google's official automation build of Chrome) in a private Node Mantis cache. If none exists, it downloads the latest Stable Chrome for Testing (about 200 MB) the first time a browser is needed (Python wheels cannot run install steps); nodemantis install-browser does it ahead of time and nodemantis doctor shows which browser is used. No admin rights are needed and your own browser is never touched. To remove it, delete the cache folder: ~/Library/Caches/nodemantis/chrome (macOS), %LOCALAPPDATA%\nodemantis\cache\chrome (Windows) or ~/.cache/nodemantis/chrome (Linux, honours XDG_CACHE_HOME). Set NODEMANTIS_SKIP_BROWSER_DOWNLOAD=1 to turn every automatic download off, for example on locked-down machines. On Linux, Chrome for Testing needs the usual Chrome system libraries (libnss3, libatk-bridge2.0-0, libgbm1, libasound2, ...); nodemantis doctor names any that are missing.

Startup-failure reports

If a run, session start or nodemantis doctor fails before the first step reaches the Node Mantis API (for example the engine is missing, Chrome does not launch, the API key is rejected, or the network is down), the SDK sends one short report to https://api.nodemantis.com/v2/client-events so we can fix first-run problems we would otherwise never see. It is sent in the background with a 2-second limit and never changes output or exit codes.

  • Sent: which step failed, an error code, a short error message with URLs, file paths, email addresses and keys removed, the SDK, engine, OS, CPU and Node.js/Python versions, the command, how the CLI was installed (when known), whether it runs in CI, and a random install ID stored next to your config file. When an API key is configured it is sent as the usual Authorization header so the report is linked to your account.
  • Never sent: your task or prompt, page URLs or content, selectors, file paths, environment variables, or the API key itself in the report.
  • Opt out: set NODEMANTIS_TELEMETRY=0 (or false/off), or DO_NOT_TRACK=1. nodemantis doctor --offline never sends one.

Metadata

Release files for node-mantis 0.1.7

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

Built distributions (wheels)

Table of built distributions (wheels) for node-mantis 0.1.7
File Actions
node_mantis-0.1.7-py3-none-win_amd64.whl Python 3 none Windows x86-64 Details for node_mantis-0.1.7-py3-none-win_amd64.whl
node_mantis-0.1.7-py3-none-manylinux_2_17_x86_64.manylinux2014_x86_64.whl Python 3 none Linux glibc 2.17+ x86-64 Details for node_mantis-0.1.7-py3-none-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
node_mantis-0.1.7-py3-none-macosx_11_0_arm64.whl Python 3 none macOS 11.0+ ARM64 Details for node_mantis-0.1.7-py3-none-macosx_11_0_arm64.whl
node_mantis-0.1.7-py3-none-macosx_10_12_x86_64.whl Python 3 none macOS 10.12+ x86-64 Details for node_mantis-0.1.7-py3-none-macosx_10_12_x86_64.whl

Total release size: 43.5 MB

Release files / node_mantis-0.1.7-py3-none-win_amd64.whl

Download URL node_mantis-0.1.7-py3-none-win_amd64.whl
Size 10.8 MB
Tags Python 3 Windows x86-64
SHA-256 checksum
How to use checksums
6e05088f69c50d88c113e6ce53be7cdc811fab884fbeb349eb68209063f3263b
BLAKE2b-256 checksum
How to use checksums
f8f936309631f95ee9503e77945dff67fdd319fa8e6c5827d7dcca93cd889f82
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.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 Nov 15, 2026.

Transparency log

Release files / node_mantis-0.1.7-py3-none-manylinux_2_17_x86_64.manylinux2014_x86_64.whl

Download URL node_mantis-0.1.7-py3-none-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
Size 11.5 MB
Tags Linux glibc 2.17+ x86-64 Python 3
SHA-256 checksum
How to use checksums
e5d62ff4ffd2ffa1a057b8726fbd056a417d784c86baf42f91ebaccb408fc478
BLAKE2b-256 checksum
How to use checksums
c2d38b4f008d9a17043d1b926a0cdb5fcc47bdfca579b4611267c722a47efed3
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.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 Nov 15, 2026.

Transparency log

Release files / node_mantis-0.1.7-py3-none-macosx_11_0_arm64.whl

Download URL node_mantis-0.1.7-py3-none-macosx_11_0_arm64.whl
Size 9.8 MB
Tags Python 3 macOS 11.0+ ARM64
SHA-256 checksum
How to use checksums
950e1bc47d1d9a1f96bc80230a66038035e518a236c69a9fefc12e0f6def64ef
BLAKE2b-256 checksum
How to use checksums
a49bfb8f8c1bdb02078c38e9f9afee0f5749c554a9deffef819d66ef1ba1d3b3
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.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 Nov 15, 2026.

Transparency log

Release files / node_mantis-0.1.7-py3-none-macosx_10_12_x86_64.whl

Download URL node_mantis-0.1.7-py3-none-macosx_10_12_x86_64.whl
Size 11.4 MB
Tags Python 3 macOS 10.12+ x86-64
SHA-256 checksum
How to use checksums
caf46f448b6f8969fd03a072703ab4d91ae6cfaf238e9827fa46bcab4327ad07
BLAKE2b-256 checksum
How to use checksums
55c2db950d684e60d0b82aca82ae5b5d49fb2deab57d44404b30c72f048a9bce
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.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 Nov 15, 2026.

Transparency log

Security for node-mantis 0.1.7

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.

Full provenance

All 4 files in this release have been uploaded with provenance metadata.

Select from 4 files

Attestation for node_mantis-0.1.7-py3-none-win_amd64.whl

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 Nov 15, 2026.

Transparency log

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

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