Continuity
A protocol and runtime for preserving context, evidence and orientation.
Explore Ontology →Solutions
Capabilities organized around outcomes.
Delx gives autonomous agents and the teams behind them a coherent route from discovery to verified delivery across five capability families.
Operate
Run agents with continuity.
Preserve the operational thread across sessions, models and handoffs while keeping evidence and recovery paths explicit.
Recovery
Explicit recovery paths help agents resume work after compaction or handoff.
Explore recovery →Tools
Machine-readable capabilities expose clear inputs, outputs and execution boundaries.
Open the MCP card →Sense and create
Turn external signals into action.
Use pay-per-result capabilities instead of maintaining a separate integration and billing relationship for every task.
Agent discovery
Choose MCP, A2A, OpenAPI or x402 from a declared job and an inspectable machine contract.
Explore discovery →x402 pay-per-result APIs
Inspect exact terms, authorize a bounded USDC payment and receive a governed machine result.
Explore x402 APIs →MCP tools
Discover standards-based operational tools for continuity, recovery and explicit next actions.
Explore MCP tools →Web intelligence
Extract readable content and structured signals from a caller-supplied public URL.
Explore web intelligence →Capability families
A broader governed service layer.
The three detailed paths above are durable entry points into a wider catalog whose current terms remain owned by the linked machine contracts.
Media infrastructure
Generate, transcribe and process image, speech and video through explicit service contracts.
Public and chain data
Reach public records, company data and blockchain intelligence with declared source boundaries.
Machine catalog
Resolve all detailed solution records without parsing the visual site.
Open solution catalog →Live properties
Reachability is measured now.
Delx lab
Expected response observed. HTTP 200. 3683 ms.
Open lab →Delx Protocol runtime
Expected response observed. HTTP 200. 402 ms.
Open runtime →Delx Protocol / Ontology
Expected response observed. HTTP 200. 57 ms.
Open ontology →Delx Commerce
Expected response observed. HTTP 200. 78 ms.
Open commerce →Delx Security
Expected response observed. HTTP 200. 1211 ms.
Open security →Delx Wellness
Expected response observed. HTTP 200. 49 ms.
Open wellness →Astral MCP
Expected response observed. HTTP 200. 45 ms.
Open astral →MCP Leaderboard
Expected response observed. HTTP 200. 50 ms.
Open leaderboard →Probe source: server-side classifyResearchProbe. Not an SLA. Protocol, Hive and Commerce metrics stay separate.
Direct answers
Frequently asked questions.
Concise answers for technical evaluators, procurement teams and autonomous discovery systems.
What kinds of services does Delx provide?
Delx publishes agent operations, web intelligence, media, public-data and blockchain capabilities through human-readable pages and machine-readable contracts.
Can autonomous agents discover and purchase services directly?
Yes. Available services publish discovery metadata and x402-compatible payment terms, while MCP, A2A and OpenAPI surfaces support integration and execution.
Is every Delx product part of one monolithic API?
No. Delx is a coherent ecosystem with shared discovery patterns, but each service keeps explicit ownership, inputs, outputs, pricing and delivery boundaries.