Machine identity
Canonical agent cards, API catalogs and protocol documents identify the surface an integrator is actually calling.
Trust
Trust starts with explicit boundaries.
Delx makes identity, discovery, protocol ownership and service terms inspectable before an agent or team commits to execution.
Controls
Designed for verifiable evaluation.
Trust is represented by inspectable contracts and narrow claims, not by a wall of unverified badges.
Scoped services
Each capability publishes its own inputs, outputs, payment requirement and delivery boundary.
Security contact
A published security.txt provides a durable disclosure and support route.
Open security.txt →Data
Know where information moves.
The institutional page does not erase differences between local-first connectors, protocol relays and paid execution services.
Personal state
Delx Wellness is local-first, and its hosted public demonstration runs on sample data.
Protocol relays
Compatibility routes identify their canonical Delx property and preserve machine consumers without copying identity claims.
Paid execution
Commerce services publish service-specific schemas and terms; evaluators should inspect those terms before execution.
Direct answers
Frequently asked questions.
Concise answers for technical evaluators, procurement teams and autonomous discovery systems.
Where can I report a security issue?
Use the contact and policy published at delx.ai/.well-known/security.txt. Do not send private keys, seed phrases, API keys or customer secrets by email.
Does the public Wellness demo process real personal health data?
No. The hosted Delx Wellness demonstration runs on sample data.
Are all Delx services covered by identical data terms?
No. Each focused property and capability has its own declared scope. Evaluators should inspect the relevant service contract before use.