Skip to main content

HYBRIQX Workout Assistant

A standalone, client-only Python buyer for HYBRIQX advisory workout adaptation. No server, exercise execution, model runner, coaching-app subscription or bundled backend engine. This is not medical advice or a guarantee of exercise safety, efficacy or latency. Consult an appropriately qualified professional when needed.

Install (Python 3.12+)

PyPI publication is pending authorization. Install from the public repository:

python -m pip install "git+https://github.com/LKennedyShare/hybriqx-workout-assistant.git"

From a checkout, with optional actual framework integrations and tests:

python -m venv .venv
.venv\Scripts\python -m pip install -e ".[test,langchain,openai,release]"
.venv\Scripts\python -m pytest -q

The base package does not import either framework. Optional extras are langchain (langchain-core >=1.6,<2) and openai (openai-agents >=0.24,<1). They provide real tools, not prompt templates or a hosted model. If your package mirror has not indexed openai-agents 0.24 yet, install its official upstream release tag first (never disable TLS verification):

python -m pip install "https://github.com/openai/openai-agents-python/archive/refs/tags/v0.24.0.zip"
python -m pip install -e ".[test,langchain,openai,release]"

Offline first

hybriqx-workout-assistant --demo
python -m hybriqx_workout_assistant --demo
python examples\standalone.py
python examples\framework_demo.py --framework langchain
python examples\framework_demo.py --framework openai

All of these are offline, use the labelled SYNTHETIC_ILLUSTRATION fixture, and need no wallet or model API key. The fixture’s rowing machine matches its rowing example; it is not personalized advice. execution_time_ms=0 is a placeholder, not measured performance. Framework demos invoke tools locally: no AgentRunner, Agents Runner, model requests or tracing setup.

Inspection and explicit payment

Prepare a private local JSON object using the public request schema:

{
  "original_wod": "SYNTHETIC_ILLUSTRATION: 3 rounds of 200 m rowing and 10 air squats.",
  "available_equipment": ["rowing machine"],
  "target_time_domain_mins": 15,
  "athlete_notes": null
}

original_wod is a nonblank string of 1..5000 characters. available_equipment is required, up to 50 nonblank strings; an empty list is allowed. Strings are trimmed. target_time_domain_mins is an integer 1..240 or null, default 15. athlete_notes is a string of at most 1000 characters or null, default null. Unknown fields and coercions are rejected.

Inspect payment terms without uploading the workout:

hybriqx-workout-assistant --request examples\synthetic_request.json

The request is validated locally first. Inspection POSTs only {}, even when a wallet is configured. It never signs, uploads your workout/notes, or pays. An ungated endpoint returning success to this empty probe is treated as an error, not as a workout result.

Only --pay permits one paid request with the validated normalized body:

# PowerShell: obtain the value privately; do not paste a key into shared logs.
$secure = Read-Host "Dedicated x402 wallet private key" -AsSecureString
$env:X402_CLIENT_PRIVATE_KEY = [System.Net.NetworkCredential]::new("", $secure).Password
try {
    hybriqx-workout-assistant --request examples\synthetic_request.json --pay --max-usdc 0.05
} finally {
    Remove-Item Env:X402_CLIENT_PRIVATE_KEY -ErrorAction SilentlyContinue
    Remove-Variable secure -ErrorAction SilentlyContinue
}

Use a dedicated low-balance wallet funded appropriately for the quoted network. Never commit its key. The client reads only X402_CLIENT_PRIVATE_KEY and only after explicit payment opt-in and quote validation. The x402 fee buys a single advisory adaptation; it is not a HYBRIQX app subscription and executes no exercise. Like the verification fee in an invoice or car-import buyer, a service fee does not execute the underlying real-world activity.

Service contract and payment guardrails

Canonical origin: https://www.hybriqx.com. The client uses POST /api/v1/scale-wod; the service alias is /v1/wod/scale. The service’s MCP endpoint is https://www.hybriqx.com/mcp/; this package uses REST, not MCP. --base-url can override only the origin. HTTPS is mandatory except for localhost/loopback HTTP. Credentials, queries, fragments, unsafe ports and every redirect (even same-origin) are refused. Apex and www are different origins: a quote advertising www against an apex request is rejected safely; use the canonical www origin rather than relying on a redirect.

The official x402 SDK decodes the v2 PAYMENT-REQUIRED header, including when the 402 body is {}. Exactly one exact quote is required, priced at precisely 50000 atomic USDC (0.05). Only these networks/tokens are accepted:

  • Base, eip155:8453: 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913

  • Base Sepolia, eip155:84532: 0x036CbD53842c5426634e7929541eC2318f3dCF7e

The resource must exactly match the requested endpoint, payTo must be a nonzero address, and authorization timeout must be 1..300 seconds. The cap defaults to 0.05 and must be a positive finite exact string/Decimal <=0.05; Python bools and floats are rejected. The quote is checked against it before wallet loading or signing, using integer-ratio arithmetic, not floating-point rounding. The SDK registers only the validated network, never a wildcard.

Each invocation makes one initial empty quote and at most one paid POST. No fresh-quote loop, hidden retries or automatic payment after 400/422/429/502/504, redirects or a repeated 402. Numeric Retry-After is retained in error reports. The authorization counter is reserved before signing and is not cleared on failure. A successful SDK settlement response must match network, any reported amount and a nonzero transaction hash. The SDK permits an omitted amount; in that case reported spending uses the authorized quote. Missing/malformed/mismatched PAYMENT-RESPONSE means unconfirmed payment: STOP and reconcile manually; do not automatically pay again. confirmed_by_sdk_response means what the SDK response reports, not independent chain verification. Settlement state is retained if result validation or HTTP processing subsequently fails.

The result has scaled_wod, movement_substitutions (list of strings), target_stimulus and finite nonnegative execution_time_ms. No medical safety validation or live performance claim is made.

Python API and privacy

import json
from hybriqx_workout_assistant import adapt_workout, BuyerError

with open("private_request.json", encoding="utf-8") as handle:
    request = json.load(handle)
try:
    report = adapt_workout("https://www.hybriqx.com", request)
    # Inspection only. Explicit operator opt-in:
    # report = adapt_workout("https://www.hybriqx.com", request,
    #                        pay=True, max_usdc="0.05")
except BuyerError as error:
    report = error.report  # Safe financial state; no raw request/SDK error.

run_workout is an alias with the same signature. Both accept a test-only transport=httpx.MockTransport(...) parameter. pay must be a literal bool. Invalid input makes no HTTP requests. Success CLI output is exactly one JSON object on stdout; errors are one JSON object on stderr with nonzero status. --help provides ordinary CLI help. Error reports omit raw workouts, notes, wallets and server/SDK error bodies. Successful result JSON intentionally contains private workout content for the same caller: do not publish it, send it to public telemetry, or capture it in shared logs. Inspection reports do not echo input.

Notes may contain health data. Obtain informed consent before sharing workout or notes with HYBRIQX. If a model is involved, separately assess and consent to the chosen model provider’s data handling, tool inputs/outputs, logs and tracing. This package cannot enforce a host application’s telemetry/tracing policy.

Development

Tests use only mock transport; actual framework tools are invoked locally. No service, model, wallet signing, chain settlement or exercise efficacy is tested live:

python -m pytest -q
python -m build
python -m twine check dist\*

MIT licensed, copyright 2026 LKennedyShare. No claim of PyPI publication.

Metadata

Release files for hybriqx-workout-assistant 0.1.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for hybriqx-workout-assistant 0.1.0
File Size Uploaded
hybriqx_workout_assistant-0.1.0.tar.gz 32.8 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for hybriqx-workout-assistant 0.1.0
File Interpreter ABI Platform
hybriqx_workout_assistant-0.1.0-py3-none-any.whl Python 3 none any Details

Total release size: 49.8 kB

Release files / hybriqx_workout_assistant-0.1.0.tar.gz

Download URL hybriqx_workout_assistant-0.1.0.tar.gz
Size 32.8 kB
Tags Source
SHA-256 checksum
How to use checksums
0af66c3681d2e5d1665571fa9909357f6df0eb301d87cc7b875e0ee495fc4fb6
BLAKE2b-256 checksum
How to use checksums
1ef0f9da552b46dd421d43956b7caec98c11b6da8fbac5721e787b88291d2a94
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 16, 2026.

Transparency log

Release files / hybriqx_workout_assistant-0.1.0-py3-none-any.whl

Download URL hybriqx_workout_assistant-0.1.0-py3-none-any.whl
Size 17.1 kB
Tags Python 3
SHA-256 checksum
How to use checksums
e79999e3d3217da16558b0f782a58550fc4dec11f1e79a2f6aedb2188d33df4f
BLAKE2b-256 checksum
How to use checksums
4921b22e46d1629a1b8a8b65544707e05cbdbda35510ad59912e7988e9844a32
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 16, 2026.

Transparency log

Release history Release notifications | RSS feed

This release

0.1.0 This release

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page