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 byactor_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.4
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| apify_hermes_agent_plugin-0.1.4.tar.gz | 14.4 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| apify_hermes_agent_plugin-0.1.4-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 25.8 kB
Release files / apify_hermes_agent_plugin-0.1.4.tar.gz
| Download URL | apify_hermes_agent_plugin-0.1.4.tar.gz |
|---|---|
| Size | 14.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
09d1f4a01beeeb0309b6240b160602a19ca61f0143e1e3342d338d733f76a041
|
|
BLAKE2b-256 checksum How to use checksums |
bed48a8bf48db1690ac2db4d4846adc82458c8ac73ad66264dd6de713964646b
|
| 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 18, 2026.
Transparency logRelease files / apify_hermes_agent_plugin-0.1.4-py3-none-any.whl
| Download URL | apify_hermes_agent_plugin-0.1.4-py3-none-any.whl |
|---|---|
| Size | 11.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
6a46dc0ce81904a8c27fe000c340c58f090881e8e45af4109e81a176db5a16b2
|
|
BLAKE2b-256 checksum How to use checksums |
3bc7bd983886261a8553c168f068eb62f6905e35eee6364e8d6964fb7e0e439a
|
| 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 18, 2026.
Transparency log