evokai
Evokai summons AI agents into any app: any model provider, your app's tools over MCP, skills and voice, always acting as the signed-in user, within budgets.
This package installs the Python client, evokai-client, and nothing
else: pip install evokai and pip install evokai-client give you the same evokai module. The service itself is
distributed as a container image: see the quick start.
Metadata
Release files for evokai 0.1.0
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 |
|---|---|---|---|---|
| evokai-0.1.0.tar.gz | 5.3 kB | With provenance | Details for evokai-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| evokai-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for evokai-0.1.0-py3-none-any.whl |
Total release size: 11.3 kB
Release files / evokai-0.1.0.tar.gz
| Download URL | evokai-0.1.0.tar.gz |
|---|---|
| Size | 5.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
dcdfbdb62945b322c7bce0f33617b4670f7c5be302e26fd2eb244168d98b7390
|
|
BLAKE2b-256 checksum How to use checksums |
51ced0da6f61fcefc965661b26b87aecb457878c17be98fe55dd0f7534be6d49
|
| 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 20, 2026.
Transparency logRelease files / evokai-0.1.0-py3-none-any.whl
| Download URL | evokai-0.1.0-py3-none-any.whl |
|---|---|
| Size | 5.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e6364b39fed622587391bc4b684d1ce70fbc0bd4eb236b4be4ac559225058ddc
|
|
BLAKE2b-256 checksum How to use checksums |
58f9fadc29921893020139bd332b0af3945972fa8ec70e73d3de7ce424294de6
|
| 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 20, 2026.
Transparency logSecurity for evokai 0.1.0
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 evokai-0.1.0.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 20, 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.