Delx Commerce — Pay-per-Result APIs for Agents

io.github.davidmosiahPublished by GitHub account davidmosiahv3.3.14Updated Oct 27, 2026

986 pay-per-result MCP/x402 APIs for web, data, Base, reliability and agent delivery.

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

Remote MCP endpoint offering a catalog of pay-per-result APIs for web, data, Base, reliability and agent delivery tasks.

What you can do
  • The manifest lists no individual tools, so capabilities are known only from the registry description.
  • It advertises a catalog of 986 pay-per-result MCP/x402 APIs.
  • Those APIs are grouped around web, data, Base, reliability and agent delivery use cases.
  • Each call is billed per result rather than by subscription, according to the description.
When to use it
Consider it when an assistant needs on-demand access to a broad set of web, data or Base-related APIs and per-call, pay-per-result billing suits the workload better than a subscription.
Requirements
A remote streamable HTTP endpoint at the provider's hosted address; no local package, environment variables or headers are declared. The manifest declares no authentication, but x402-style pay-per-result APIs typically require a funded payment setup, which the input does not confirm.
Before you install
Calls are described as pay-per-result, so usage can incur charges; confirm pricing and payment method before connecting. No authentication or credential requirements are declared, and no tool list is published, so the exact actions and data handling cannot be verified from the provided material.

Installation

In SourceWeft

  1. Open Delx Commerce — Pay-per-Result APIs for Agents in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.davidmosiah%2Fdelx-mcp-a2a/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "delx-commerce-pay-per-result-apis-for-ag": {
      "type": "http",
      "url": "https://api.delx.ai/v1/mcp?src=registry-commerce"
    }
  }
}

Tools

0
SourceWeft has not read this server's tools yet.

Version history

3
  1. v3.3.14LatestOct 10, 2026
  2. v3.3.13Sep 27, 2026
  3. v3.3.12Sep 16, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.