Helix Payment Recovery Runtime

What does this agent do, and when should you use it?

Helix is a self-healing runtime for autonomous agents, focused on payment execution and API-call failures. It wraps an async function and applies a six-stage PCEC flow: Perceive, Construct, Evaluate, Commit, Verify, and Gene. Verified repairs are retained in a SQLite-based Gene Map with reinforcement-learning scoring, so recurring failures can reuse prior strategies. The project exposes @helix-agent/core alongside a Python package, Docker server, REST endpoint, and CLI; its payment adapters cover Coinbase, Tempo, Privy, and generic HTTP. Helix is built as a payment vertical on VialOS Runtime and can be extended to other domains through the PlatformAdapter interface.

A developer wraps an asynchronous operation with wrap(myFunction, { mode: 'auto' }). When the operation fails, an adapter classifies the error, Helix constructs and scores candidate fixes, executes an allowed strategy, verifies the result, and records a successful repair in the Gene Map. Documented strategies include refresh_nonce, speed_up, reduce_request, backoff_retry, renew_session, split_transaction, and remove_and_resubmit. A local service accepts JSON error and platform values at POST /repair; the CLI can scan source with npx @helix-agent/core scan, dry-run a diagnosis with simulate, discover errors with self-play, and consolidate memory with dream. observe diagnoses only, auto changes parameters and retries, and full additionally enables fund-movement strategies.

1. A team running on-chain agents with Coinbase, ERC-4337, or x402 payment paths needs a recovery layer for nonce, gas, or transaction-execution errors.
2. A product using Tempo MPP, session, or DEX flows wants verified recovery decisions retained in local SQLite memory.
3. An application built around Privy embedded wallets needs controlled diagnosis and retry handling for known wallet failures.
4. A service engineer needs recovery for outbound API failures such as 429s, 5xx responses, timeouts, connection errors, or authentication failures.
5. An engineering team wants to run npx @helix-agent/core scan ./src before CI/CD to identify documented error patterns in a codebase.
6. A platform developer needs domain-specific recovery behavior and can implement PlatformAdapter with perceive and getPatterns.

How do you install or deploy this agent?

TypeScript/JavaScript:

npm install @helix-agent/core

Python:

pip install helix-agent-sdk

Docker server:

docker run -d -p 7842:7842 adrianhihi/helix-server

The documentation does not specify Node.js or Python versions, nor any credentials or environment variables required for the first invocation.

How do you use this agent?

Minimal TypeScript usage:
import { wrap } from '@helix-agent/core';

const safeCall = wrap(myFunction, { mode: 'auto' });
const result = await safeCall(args);

Start the local server and dashboard:

npx @helix-agent/core serve --port 7842

Call the repair endpoint:

curl -X POST http://localhost:7842/repair -H 'Content-Type: application/json' -d '{"error": "nonce too low", "platform": "coinbase"}'

Do not use npx helix: the documentation explicitly says it installs an unrelated third-party package.

What are this agent's strengths and limitations?

How does this agent compare with similar options?

Key facts side by side with the most closely related agents.

How does FollowAgents rate this agent?

FAQ