Automation pipeline

Automation pipeline

Otonix runs automation 24/7.

It is designed to keep agents and resources alive without humans.

Pipeline matrix

Pipeline
Trigger
Action

Agent auto-healing

Heartbeat failure

Restart agent, escalate tier

Domain auto-renewal

Expiry approaching (30 days)

Agent pays renewal via x402

DNS auto-configuration

Domain linked to VPS

Create A/CNAME records

Compute auto-routing

Inference request

Select model by cost

Payment auto-settlement

402 response

Automatic USDC payment on Base

Agent self-replication

High task load

Spawn child agent with budget

Agent auto-healing

  • Heartbeats are expected on heartbeatInterval.

  • Missing heartbeats should put the agent into a remediation loop.

Typical remediation steps:

  1. Mark agent as unhealthy.

  2. Attempt restart on the sandbox.

  3. Reduce model quality if credits are low.

  4. Log every action to agentActions.

Domain auto-renewal

  • Check expiresAt daily.

  • When within 30 days, schedule renewal.

  • Pay renewal via x402.

DNS auto-configuration

When domains.sandboxId is set:

  • Create A @ -> sandbox.ipAddress.

  • Optionally create CNAME www -> @.

  • Keep TTL small (300) during rollout.

Compute auto-routing

A routing policy should consider:

  • survival tier

  • budget remaining

  • task criticality

  • latency constraints

Payment auto-settlement

Treat x402 as a standard subroutine:

  • request

  • read requirements

  • pay

  • retry with proof

  • verify delivery

Example: heartbeat failure → remediation log

When a heartbeat is late, you should record the remediation decision.

Example: 402 → pay → retry (automation view)

This is the payment auto-settlement loop for any paid endpoint.

  1. Call the endpoint without X-Payment.

  2. Parse orderId and amountUSDC from the 402 payload.

  3. Send USDC to the treasury on Base.

  4. Retry with X-Payment.

Agent self-replication

Self-replication is powerful.

It must obey the immutable laws.

circle-exclamation

Last updated