Skip to main content

apify-hermes-agent-plugin

Hermes Agent plugin for Apify, the world's largest marketplace for AI tools - discover Actors in Apify Store, start runs, and collect structured results, all from natural language, via Hermes Agent.

Install

pip install apify-hermes-agent-plugin
hermes plugins enable apify

Then run:

hermes apify-setup

This prompts for your APIFY_API_TOKEN (get one at https://apify.com/account/integrations), saves it, and enables the Apify Actors toolset for the CLI. Pass --token <token> to skip the prompt.

Troubleshooting: hermes plugins enable apify fails

If that command prints Plugin 'apify' is not installed or bundled., your installed hermes-agent predates 0.18.1, when entry-point plugin discovery was fixed upstream. Check your version and upgrade first:

hermes --version
pip install --upgrade hermes-agent

If you can't upgrade, enable the plugin manually instead: open ~/.hermes/config.yaml and add apify to the plugins.enabled list:

plugins:
  enabled:
    - apify

Then run hermes apify-setup as above - it still takes care of enabling the toolset for you.

Tools

  • apify_discover - search Apify Store by keyword, or fetch an Actor's input schema + README by actor_id.
  • apify_start - fire-and-forget batch Actor starts (up to 10 per call).
  • apify_collect - poll run statuses and return completed dataset results.

Development

pip install -e ".[dev]"
pytest

Releasing

Releases are cut from the Actions tab, not by creating a GitHub Release by hand: open the publish workflow → Run workflow → choose a release type (auto, patch, minor, major, or custom). The pipeline then bumps the version, updates CHANGELOG.md, creates the GitHub Release, and publishes to PyPI automatically.

auto infers the version bump from Conventional Commits since the last tag, and only works correctly when at least one qualifies (feat:, fix:, etc. — see AGENTS.md's Release process for the exact rules). If you're not sure, pick patch/minor/major explicitly instead — those always compute correctly regardless of commit history.

Release files for apify-hermes-agent-plugin 0.1.3

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

Source distribution (sdist)

Source distribution for apify-hermes-agent-plugin 0.1.3
File Size Uploaded
apify_hermes_agent_plugin-0.1.3.tar.gz 14.4 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for apify-hermes-agent-plugin 0.1.3
File Interpreter ABI Platform
apify_hermes_agent_plugin-0.1.3-py3-none-any.whl Python 3 none any Details

Total release size: 25.8 kB

Release files / apify_hermes_agent_plugin-0.1.3.tar.gz

Download URL apify_hermes_agent_plugin-0.1.3.tar.gz
Size 14.4 kB
Tags Source
SHA-256 checksum
How to use checksums
6113e9638eaddf21d015fac6e3edfc3fe99999a2e023bf306b3c3fd8110c143b
BLAKE2b-256 checksum
How to use checksums
95d67c65920da33abf4fcdfd3fa58ce2439afc3ff53e3e4148066df635228f96
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 Sep 17, 2026.

Transparency log

Release files / apify_hermes_agent_plugin-0.1.3-py3-none-any.whl

Download URL apify_hermes_agent_plugin-0.1.3-py3-none-any.whl
Size 11.4 kB
Tags Python 3
SHA-256 checksum
How to use checksums
8440668c3ca726dbd81a033912f587f78578fb0d05fcf552c1eb22c47fff6878
BLAKE2b-256 checksum
How to use checksums
176068c73743b8ba3e5a19756b5e3be109fea045369ef2e914f25ad981a309c7
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 Sep 17, 2026.

Transparency log

Release history Release notifications | RSS feed

0.1.4

2 release files

This release

0.1.3 This release

2 release files

0.1.1

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