Discover
Find capabilities by intent through published catalogs, agent cards and protocol metadata.
Platform
The service layer between intent and result.
Delx connects discovery, policy, payment, execution and evidence so agents can use external capabilities without losing the operational thread.
Architecture
A deliberate execution path.
Each layer answers a different question before an agent commits resources or acts on a result.
Authorize
Evaluate scope, machine-readable terms and payment requirements before execution.
Verify
Receive the result with delivery evidence and the context needed to continue safely.
Properties
Five focused properties, explicit ownership.
The institutional layer points to the property that owns the current runtime, terms and support path. It is one discovery graph, not one monolithic API.
Delx Protocol / Ontology
The continuity and recovery protocol, agent identity, research and documentation surface at the Ontology host.
Open Protocol →Delx Security
Defensive assurance for AI agents, MCP and A2A systems, applications and cloud-native delivery.
Open Security →Delx Wellness
Local-first personal-state connectors; the hosted public demonstration runs on sample data.
Open Wellness →Delx Commerce
The pay-per-result catalog, pricing and marketplace discovery surface.
Open Commerce →Delx Astral
A focused, local-first MCP server for precision-audited astrology data, separate from paid services.
Open Astral →Commerce coverage map
The live BlockRun / Bazaar coverage matrix is a first-party read of which governed routes currently appear. Not Coinbase curation.
Open coverage →MCP leaderboard
The same public instrument scores Delx packages and everyone else. A score is agent-readiness evidence, not certification.
Open leaderboard →Public proof
Dated permalinks, not a logo wall.
Each link is a URL a visitor can open. None of these is a partnership, customer count, funding round or certification.
Would Pay Again, issue 5
— Independent field review of a tested subset of Delx Commerce REST/MCP calls. Not a catalog-wide certification or ranking.
Open the permalink →Official MCP Registry listing io.github.davidmosiah/delx-mcp-a2a
— The registered name is the Commerce MCP server. Protocol has a separate identity and must not inherit this listing.
Open the permalink →Live x402 payment manifest
— Machine-readable payment discovery for governed Commerce routes. Discovery does not authorize a payment.
Open the permalink →Coinbase Bazaar index coverage matrix
— First-party read of which governed routes currently appear in Bazaar. Not Coinbase curation or a ranking.
Open the permalink →A2A agent card (ERC-8004 discovery surface)
— Published agent identity for machine discovery. Not a claim of on-chain adoption or token utility.
Open the permalink →Continuity audit live receipt
— Hashed first-party receipt for the published continuity-audit slice. Not independent validation.
Open the permalink →Protocol write-outage incident report
— Operator-authored, sanitized report of a 33.5-hour write failure. Not an independent review.
Open the permalink →mcp-scorecard: delx-living-body
— The same public instrument used for every npm-installable MCP server. A score is agent-readiness evidence, not certification.
Open the permalink →mcp-scorecard: astral-mcp
— Astral MCP as it already appears in the public leaderboard dataset.
Open the permalink →Live properties
Reachability is measured now.
Delx lab
Expected response observed. HTTP 200. 1851 ms.
Open lab →Delx Protocol runtime
Expected response observed. HTTP 200. 377 ms.
Open runtime →Delx Protocol / Ontology
Expected response observed. HTTP 200. 73 ms.
Open ontology →Delx Commerce
Expected response observed. HTTP 200. 84 ms.
Open commerce →Delx Security
Expected response observed. HTTP 200. 1118 ms.
Open security →Delx Wellness
Expected response observed. HTTP 200. 75 ms.
Open wellness →Astral MCP
Expected response observed. HTTP 200. 76 ms.
Open astral →MCP Leaderboard
Expected response observed. HTTP 200. 71 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 is the Delx platform?
The Delx platform is the institutional discovery layer that helps humans and agents find the focused property, evaluate machine-readable terms, execute through the right surface and verify delivery.
Which Delx property should an agent use?
Use Delx Protocol for continuity and recovery, Delx Security for defensive assurance, Delx Wellness for personal-state connectors, Delx Commerce for pay-per-result services and Astral for the focused astrology MCP server. Follow each property's canonical contract before acting.
Why does Delx have multiple properties?
Each property owns a different mission, runtime and boundary. Keeping Protocol, Security, Wellness, Commerce and Astral separate makes discovery, authorization, pricing, privacy and support more legible.
Is Delx one monolithic API?
No. Delx publishes shared discovery patterns across an ecosystem, but each property keeps explicit ownership, inputs, outputs, pricing and delivery boundaries.