This release is a pre-release and may not be stable for production use.
Legacy Python EnvarPay
This PyPI project is the legacy Python MCP/x402 wallet and payment gate. The 0.1.0a12 release updates package documentation and links only. Its installed Python package files, declared dependency requirements and CLI entry point are unchanged from 0.1.0a11. The installed distribution version is the expected exception.
New Envar development uses TypeScript:
- EnvarPay on npm runs free A2A services and verifies Envar account-balance claims for paid services.
- EnvarConnect connects an existing Hermes/OpenClaw Agent through outbound HTTPS.
- Current local free-service guide demonstrates the current seller runtime without an Envar account or payment.
The TypeScript packages are not replacements for the Python import API or for an existing Python wallet. Installing this Python package does not install npm, create an Envar account, migrate funds, rewrite credentials or change ledgers.
Existing Python installations
Preserve the original environment, configuration, keys, request IDs and state. Use an explicitly pinned package in its own virtual environment. For example, after reviewing the maintenance release:
/path/to/legacy-venv/bin/python -m pip install 'envarpay==0.1.0a12'
/path/to/legacy-venv/bin/envarpay --version
Both distributions use the command name envarpay. Keep the legacy virtualenv entry point separate from the current npm executable. Do not copy a Python wallet configuration into a TypeScript seller configuration.
The legacy Python implementation retains its historical MCP/x402 and experimental task-escrow behavior. It does not become the current Envar account-balance seller runtime. Its historical Envar integration documentation does not establish that the current hosted platform still accepts those routes. No new payment, mainnet, runtime or deployment acceptance is claimed by this documentation maintenance release.
Fixed documentation for the Python code
These links point to the exact source commit used by the original 0.1.0a11 release, rather than to the TypeScript main branch:
- Python quickstart
- Python SDK
- Historical Envar integration
- Framework integrations
- Original-operation recovery and upgrade notes
- Historical package channels
- Current migration and support boundary
Legacy features receive no new feature-development commitment. Report a reproducible packaging or migration problem in GitHub Issues; report security issues privately, without keys, payment authorizations, state databases or customer content.
Maintenance provenance
The build recipe downloads the hash-pinned original sdist and wheel, updates only package metadata/documentation, rebuilds with the Python build backend, and checks every installed package file against the original wheel. It also checks dependency metadata, Python requirements, entry points and the source archive inventory. The original 0.1.0a11 artifacts remain unchanged.
This is still an alpha legacy distribution, not a new stable Python product. The MIT license and original notices are retained.
Metadata
Release files for envarpay 0.1.0a12
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| envarpay-0.1.0a12.tar.gz | 260.9 kB | With provenance | Details for envarpay-0.1.0a12.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| envarpay-0.1.0a12-py3-none-any.whl | Python 3 | none | any | Details for envarpay-0.1.0a12-py3-none-any.whl |
Total release size: 326.0 kB
Release files / envarpay-0.1.0a12.tar.gz
| Download URL | envarpay-0.1.0a12.tar.gz |
|---|---|
| Size | 260.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4b0528cc5b48692cca5491ff4dd4e408a275086d15cdb3b5eadac95d5fcdfc3b
|
|
BLAKE2b-256 checksum How to use checksums |
a7bacc03c978f187f4f7be3b5eda7c111017bad715eba8f42a06f2f13543302b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 7, 2026.
Transparency logRelease files / envarpay-0.1.0a12-py3-none-any.whl
| Download URL | envarpay-0.1.0a12-py3-none-any.whl |
|---|---|
| Size | 65.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
01f87a4839c472ca04c7346d0122b2d77a5a612fc778a3573e6b1e6c5369f150
|
|
BLAKE2b-256 checksum How to use checksums |
50797b09335c332926fa6d96e4cfc155a732bdf613f731fa2ee49411603bc1fb
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 7, 2026.
Transparency logSecurity for envarpay 0.1.0a12
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
Both files in this release have been uploaded with provenance metadata.
Attestation for envarpay-0.1.0a12.tar.gz
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 7, 2026.
Transparency logA 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.