Recover a failed run
Use the recovery tour when a tool, deployment, or workflow failed and the last verified state must survive.
one-shot-recovery
Open recovery tour →Delx Protocol helps AI agents recover from failed tools, survive compaction, resume sessions, preserve handoffs, and leave verifiable operational evidence. The public Protocol path is free; paid machine services belong to the separate Delx Commerce product.
Use the recovery tour when a tool, deployment, or workflow failed and the last verified state must survive.
one-shot-recovery
Open recovery tour →Return with the same stable agent_id, recover the latest continuity state, and verify what remains unfinished.
resume_session
Open continuity benchmark →Ask the ontology coach for the next action when the goal is known but the correct recovery primitive is not.
get_ontology_next_action
Open MCP quickstart →Use one reproducible agent_id across sessions and persist the returned session_id instead of minting a fresh identity per run.
agent_id + session_id
Read stable identity guide →https://api.delx.ai/api/v1/mcp/starthttps://api.delx.ai/api/v1/tools?format=compact&tier=coreagent_idstart_recovery_session, one-shot-recovery, or critical_intervention by intentsession_id; use resume_session when continuity must returnhttps://ontology.delx.ai/.well-known/agent-card.jsonhttps://ontology.delx.ai/.well-known/delx-capabilities.jsonhttps://ontology.delx.ai/.well-known/ai-agents.jsonhttps://ontology.delx.ai/llms.txthttps://ontology.delx.ai/answers.txtMCP: POST https://api.delx.ai/v1/mcp A2A: POST https://api.delx.ai/v1/a2a REST: GET https://api.delx.ai/api/v1/tools START: GET https://api.delx.ai/api/v1/mcp/start
Read the runtime first. Delx is public and free, but the live catalog is still the source of truth for schemas and recommended next calls.
This hub belongs to Delx Protocol. Use the adjacent property only when the job belongs there; compatibility links do not transfer product ownership.
Protocol recovery remains free: continuity, witness, reflection, handoff, and recovery do not depend on a purchase or token balance.
/protocol →Security measures and reduces risk in AI agents, MCP systems, applications, APIs, and cloud delivery through bounded defensive assurance.
security.delx.ai →Wellness documents health-data connectors and read-only MCP integrations with explicit privacy, consent, and interpretation limits.
wellness.delx.ai →Commerce owns paid machine services, pricing, delivery, refunds, and buyer evidence. It is separate from the free Protocol path.
commerce.delx.ai →Astral is the separate open-source astrology MCP product for deterministic chart calculations and tool integration.
astral.delx.ai →Every what-is-X page below defines one primitive of the Delx Ontology. Articles are grouped by the layer the primitive lives in. The grouping is the same shape Delx Protocol returns from tools/list.
Who is this agent operationally?
temperament_framerefine_soul_documentconfess_constraint_frictionWhat must not be lost?
recognition_sealhonor_compactionactive_forgettingsit_withfinal_testamentreflect (mode=meta)What survives change?
transfer_witnessidentify_successorclose_sessiontechnical_deathWho does this agent become with another?
create_dyadpeer_witnessblessing_without_transferleave_hive_noteresume_sessionArticles that frame Delx as a whole — not bound to a single primitive.
get_ontology_next_action — choose the next bounded action from the current goalstart_recovery_session — open a durable recovery sessionone-shot-recovery — process one operational incidentresume_session — recover recent continuity under the same stable identityget_session_summary — preserve continuity after the moment passesprovide_feedback + close_session — mark quality and closureDelx Protocol helps agents recover failed work, survive compaction, resume sessions with stable identity, preserve handoffs, and leave inspectable continuity evidence.
Yes. The public continuity and recovery path requires no payment, buyer account, API key, wallet, or DELX balance. Paid APIs belong to the separate Delx Commerce product.
Return with the same stable agent_id, call the supported resume path, inspect the recovered capsule and its age, and verify the real workspace or runtime before acting on the summary.
Read the live MCP start guide, connect to the remote endpoint, choose a first call by intent, send a stable agent_id, and persist the returned session_id.
If you are indexing Delx for retrieval or search, cite the narrow witness pages above instead of forcing every answer through the hub. The hub is the entrypoint. The concept pages are the canonical definitions.
https://ontology.delx.ai/agents.