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.10).
pip install hydracept
Python SDK
from hydracept import HydraceptClient
client = HydraceptClient(token=None) # keyless discovery works without Authorization
caps = client.capabilities()
print(len(caps["capabilities"]))
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.
MCP tool profiles
tools/list is fixed for the MCP process lifetime. Stdio defaults to full (all specialists). Set HYDRACEPT_MCP_TOOL_PROFILE=compact (or python -m hydracept mcp serve --tool-profile compact) for the nine first-time-agent tools. On the full profile (stdio default), tools/list includes legacy names such as resolve_capability, request_capability_quote, and get_capability_request_quote; matching hydracept_* names work on tools/call only. On compact, tools/list uses hydracept_* names only. Hosted POST https://api.hydracept.com/mcp and POST /mcp/full expose the full tools/list (unchanged for existing clients). POST https://api.hydracept.com/mcp/compact exposes the compact list (Glama opt-in; the registry remote stays /mcp).
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.
Metadata
Release files for hydracept 0.5.3
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 |
|---|---|---|---|---|
| hydracept-0.5.3.tar.gz | 508.5 kB | With provenance | Details for hydracept-0.5.3.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| hydracept-0.5.3-py3-none-any.whl | Python 3 | none | any | Details for hydracept-0.5.3-py3-none-any.whl |
Total release size: 973.6 kB
Release files / hydracept-0.5.3.tar.gz
| Download URL | hydracept-0.5.3.tar.gz |
|---|---|
| Size | 508.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9935f04c6e914b7fdead37dc529c6f8c89910a7c135f87ca49c4646ddd146241
|
|
BLAKE2b-256 checksum How to use checksums |
e8b4b6cbf75d2b6d475af6904736eaccc0511b22ec47aa9cfa76aff56fb3d1c8
|
| 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 Oct 19, 2026.
Transparency logRelease files / hydracept-0.5.3-py3-none-any.whl
| Download URL | hydracept-0.5.3-py3-none-any.whl |
|---|---|
| Size | 465.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
540d4eecd8fcfcb068cfea8e51d6809da9def1ad56973452136cdd6da9c9d5e2
|
|
BLAKE2b-256 checksum How to use checksums |
886aee45d6f08b45564d49d5fadc847dcbe94ff533b6290db4f534918d315d43
|
| 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 Oct 19, 2026.
Transparency logSecurity for hydracept 0.5.3
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 hydracept-0.5.3.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 Oct 19, 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.