Everpod SDK for Python
The official Python client for the Everpod API.
Everpod is an easy way to get your own always-on, persistent cloud computer for AI agents, working in minutes: as a developer pod with your pick of Claude Code, Codex, OpenCode, Pi, Hermes and OpenClaw installed, or with OpenClaw set up and run for you. A key lets an agent or an app you trust see your pods and start a new one for you, which you then pay for on everpod.ai. It can't pay, change or cancel a plan, delete anything, open your agent's control panel, or reach a developer pod's machine.
If you are connecting an agent such as Claude Code or Codex, you do not need this library: point it at Everpod's MCP server, as the API reference shows.
Install
pip install everpod-ai
Python 3.9 or later. No dependencies.
Use
To make a key, open everpod.ai/account/keys and sign in with your email address and the code we send you. If you have no account yet, signing in makes one. Give the key to the library from an environment variable.
import os
from everpod_ai import Everpod
everpod = Everpod(os.environ["EVERPOD_API_KEY"])
# Start an OpenClaw pod under the name you want for its agent. Nothing is
# charged: the pod stays unpaid until you open pay_url in a browser and pay there.
pod = everpod.start_pod("Otto")
print(pod["status"], pod["pay_url"])
# Or a developer pod: the machine's name, your username on it, which
# coding agents come installed (any of claude, codex, opencode, pi, hermes and openclaw; Claude Code and Codex when left out) and its size (s, m or
# l; the S when left out).
machine = everpod.start_pod("atlas", kind="developer", login="alex", agents=["claude", "codex"], size="m")
# The pods on your account, oldest first.
pods = everpod.list_pods()
# One pod by its id: how to check whether it has been paid for, and whether it is ready.
same = everpod.get_pod(pod["id"])
While your account has an unpaid pod, starting another returns that same pod, changed to the name and kind now asked for.
A pod's fields and what each status means are in the API reference.
When a request is refused
A refusal raises an EverpodError. Its message is the API's own sentence, which says what happened and what to do next; code and status are the refusal's.
from everpod_ai import EverpodError
try:
everpod.get_pod(pod_id)
except EverpodError as error:
print(error.code, error.status, error.message)
Questions
License
MIT
Metadata
Release files for everpod-ai 0.3.1
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 |
|---|---|---|---|---|
| everpod_ai-0.3.1.tar.gz | 7.3 kB | Without provenance | Details for everpod_ai-0.3.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| everpod_ai-0.3.1-py3-none-any.whl | Python 3 | none | any | Details for everpod_ai-0.3.1-py3-none-any.whl |
Total release size: 13.3 kB
Release files / everpod_ai-0.3.1.tar.gz
| Download URL | everpod_ai-0.3.1.tar.gz |
|---|---|
| Size | 7.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a6473b07abb8017ebc82c2e350560fc7eb374d94e9578f1ed961740bee9c39f5
|
|
BLAKE2b-256 checksum How to use checksums |
430f83908f1c305e75de4b84b7b39e84f06b718216a096ecfe27c79cc8271427
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.11.2
|
Release files / everpod_ai-0.3.1-py3-none-any.whl
| Download URL | everpod_ai-0.3.1-py3-none-any.whl |
|---|---|
| Size | 6.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
f5f244b824462b3cde44adf17906470b4d7b4945ce32be5a97f9e78f59478331
|
|
BLAKE2b-256 checksum How to use checksums |
a75186821b1f86699d1e7e322c731ce133521110bc44939f09d1ddec5f874504
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.11.2
|
Security for everpod-ai 0.3.1
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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
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.