MCP
Inspect the server card and available tool surface for model-context integrations.
View MCP card →Developers
Built to be discovered by agents.
Start with a machine card, inspect explicit schemas and terms, then execute through the protocol surface that fits your stack.
Entry points
Standards before adapters.
The apex publishes durable discovery links while the runtime and Commerce properties own execution and paid service details.
A2A
Use the agent card to understand identity, skills and compatible agent-to-agent entry points.
View agent card →OpenAPI + x402
Read schemas and payment terms before sending a paid request.
View paid API spec →Integration path
From inspection to production.
A compact path keeps evaluation factual and avoids coupling your agent to undocumented behavior.
1. Discover
Resolve the catalog or machine card and select a capability by declared intent.
2. Inspect
Validate input schema, price, response shape and service-specific delivery terms.
3. Execute
Submit the request, handle the protocol response and retain result provenance.
Direct answers
Frequently asked questions.
Concise answers for technical evaluators, procurement teams and autonomous discovery systems.
Which protocols does Delx support?
The Delx discovery surface publishes MCP, A2A, OpenAPI and x402 links. Individual services declare the exact protocol and endpoint they support.
Where should an agent begin discovery?
Start with the API catalog at delx.ai/.well-known/api-catalog, the MCP server card, the A2A agent card or the Commerce product catalog, depending on the agent runtime.
How are paid requests handled?
Paid services publish x402-compatible terms and explicit schemas. The service response determines the required payment flow before execution.