hydracept
Python client for the Hydracept public API — an execution control plane for software and agents that need external capabilities.
Official MCP Registry name matches hydracept-plugin mcp-registry/server.json (com.hydracept/hydracept, domain-verified on hydracept.com). Cursor plugin distribution: github.com/zencodeinc/hydracept-plugin (v0.1.8).
pip install hydracept
Required onboarding is python -m hydracept init --apply --yes --json. Init reuses an authenticated GitHub CLI (gh) session when one is already available; otherwise use a browser connect flow or HYDRACEPT_API_KEY. Canonical docs are https://docs.hydracept.com. hydracept run --input-file accepts structured JSON on Windows/PowerShell, including UTF-8 BOM and UTF-16 files. Funding status reports customer-visible managed credit separately from trial and operator execution funding. Receipts distinguish retail price from the amount the customer actually owes or was debited (pricing.customerCharge). Domain and CPU capabilities omit inference billingModes.
python -m hydracept init --apply --yes --json
python -m hydracept doctor
python -m hydracept verify
python -m hydracept pinned --help
Pinned Execution (RIP) and provenance:
python -m hydracept pinned run body.json
python -m hydracept pinned get <receipt_id>
python -m hydracept lockfile emit <receipt_id>
python -m hydracept verify
Developer onboarding
python -m hydracept init --apply --yes --json
python -m hydracept doctor
python -m hydracept agents install --auto
python -m hydracept smoke
Native integrations for Cursor, Claude Code, and Google Antigravity ship via the Agent Pack (agents install). Session hooks inject local readiness only — smoke is explicit.
Agent / CI path (secret via env, not prompt)
export HYDRACEPT_API_KEY=hydracept_...
python -m hydracept quickstart --json --smoke
python -m hydracept consumer-check --strict
Breaking change in 0.2.3
hydracept login (device flow) stores a human session only. Mint a workspace API key with:
python -m hydracept keys create --configure
Docs: https://docs.hydracept.com · Start: https://hydracept.com/start
A Zencode company · © Zencode Consulting Inc.
1 maintainer
Release files for hydracept 0.4.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 | |
|---|---|---|---|
| hydracept-0.4.4.tar.gz | 463.0 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| hydracept-0.4.4-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 881.0 kB
Release files / hydracept-0.4.4.tar.gz
| Download URL | hydracept-0.4.4.tar.gz |
|---|---|
| Size | 463.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
178e92e7363c15558322bdb34e3df73f3504759c6d9ce5f85fd05a76c75e6848
|
|
BLAKE2b-256 checksum How to use checksums |
3335a262b75d5e97ac7c981817621dd136c2b97994ef384d0366d593fd809d69
|
| 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 25, 2026.
Transparency logRelease files / hydracept-0.4.4-py3-none-any.whl
| Download URL | hydracept-0.4.4-py3-none-any.whl |
|---|---|
| Size | 418.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
3008620a4dcae69a43cf51ccf6ab2645ab0f7a98f171301a795c92660d7ed009
|
|
BLAKE2b-256 checksum How to use checksums |
121e5edfd50358d52f196f78d1d036507417e5258ee67ebdbb988b1a211afc0e
|
| 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 25, 2026.
Transparency log
