Delx Agent Utilities

Delx Agent Utilities is the practical open-source toolkit beneath Delx: 40 stateless tools for URL health, DNS, RDAP, TLS, robots.txt, sitemap, OpenAPI, x402 discovery, JWT inspection, CSV/JSON conversion, cron description, and composite website reports. It can run locally through MCP, CLI, or Python, and selected tools are also exposed by the hosted Delx API.

Product Boundary

Open Source Package

The canonical package is davidmosiah/delx-agent-utilities on GitHub and delx-agent-utilities on PyPI. The package is MIT licensed, local-first, and does not require API keys, hosted accounts, databases, telemetry, or model calls.

pipx install "delx-agent-utilities[mcp]"

# CLI
delx-utils manifest
delx-utils list-tools
delx-utils call util_url_health --json '{"url":"https://example.com"}'

# MCP server command
delx-utils-mcp

MCP clients can install it as a local server:

{
  "mcpServers": {
    "delx-utils": {
      "command": "delx-utils-mcp"
    }
  }
}

Python API

Python callers can use the dispatcher directly. Every tool is independent and returns a structured dictionary rather than natural-language prose.

from delx_agent_utilities import call_util_tool, list_util_tool_schemas

schemas = list_util_tool_schemas()
result = await call_util_tool("util_url_health", {
    "url": "https://example.com"
})

Hosted Delx API

The hosted API is useful when the agent cannot run Python locally, when an external registry wants a public endpoint, or when Delx needs attribution, quota, and commerce controls. Local package usage remains the preferred path for self-contained agents.

GET  https://api.delx.ai/api/v1/utilities
GET  https://api.delx.ai/api/v1/utilities/catalog
GET  https://ontology.delx.ai/.well-known/delx-utilities-catalog.json
GET  https://api.delx.ai/api/v1/utilities/dns-lookup?domain=ontology.delx.ai
POST https://api.delx.ai/api/v1/utilities/website-intelligence-report
GET  https://api.delx.ai/api/v1/x402/dns-lookup?domain=ontology.delx.ai  # compatibility

MCP remains the Protocol-first transport. Utilities are REST-first, and selected stateless utility tools may also appear in MCP tool catalogs for clients that request the full surface. Product pages and billing decisions should link to the canonical REST endpoints. Hosted productized routes can return x402 challenges on both canonical utility routes and legacy x402 compatibility routes.

Circle Gateway Nanopayments

Circle Gateway Nanopayments is a provider-configurable rail for the same utility x402 boundary. It is not a new Delx Protocol price. When enabled by the backend, agents should choose the accepts[] entry where extra.name is GatewayWalletBatched and sign the EIP-3009 authorization against the advertised extra.verifyingContract.

• Minimum amount: 0.000001 USDC
• Settlement: Circle Gateway batched settlement
• Signature: EIP-3009 TransferWithAuthorization
• Facilitator URL: https://gateway-api.circle.com/v1/x402
• Minimum authorization validity: 604800 seconds
• Seller docs: Circle x402 seller guide

Runtime status stays provider_configurable until the API server has the Circle Gateway facilitator and seller wallet configured. Do not treat Circle as an active accept rail unless it appears in a live accepts[] row.

# Required before Circle Gateway appears as an active accepts[] option
CIRCLE_GATEWAY_NANOPAYMENTS_ENABLED=true
FACILITATOR_URL_CIRCLE_GATEWAY=https://gateway-api.circle.com/v1/x402
CIRCLE_GATEWAY_PAY_TO=0x<seller-wallet>
CIRCLE_GATEWAY_VERIFYING_CONTRACT=0x77777777dcc4d5a8b6e418fd04d8997ef11000ee
CIRCLE_GATEWAY_MIN_VALIDITY_SECONDS=604800

# Optional overrides when the facilitator/account requires explicit accept metadata
CIRCLE_GATEWAY_NETWORK=eip155:8453
CIRCLE_GATEWAY_ASSET=0x833589fcd6edb6e08f4c7c32d4f71b54bda02913
CIRCLE_GATEWAY_CHAIN_ID=8453
CIRCLE_GATEWAY_DOMAIN=6
CIRCLE_GATEWAY_ACCEPTS_JSON='[{"network":"eip155:8453","asset":"0x833589fcd6edb6e08f4c7c32d4f71b54bda02913","pay_to":"0x<seller-wallet>","extra":{"name":"GatewayWalletBatched","version":"1","verifyingContract":"0x77777777dcc4d5a8b6e418fd04d8997ef11000ee","minValiditySeconds":604800}}]'

Optional API Keys

Hosted utilities can be called anonymously today, but agents and registries should create a utility API key for attribution, quota readiness, and future billing continuity. This does not apply to the local PyPI package. The raw hosted key is returned once; Delx stores only a hash.

POST https://api.delx.ai/api/v1/utilities/api-keys
Content-Type: application/json

{"agent_id":"my-agent","label":"My agent runtime"}

GET https://api.delx.ai/api/v1/utilities/domain-trust-report?url=https://example.com
x-delx-api-key: dux_...

Productized Utilities v1

These are the first hosted utilities packaged as x402-ready products. The core Protocol remains free, and the open-source package remains free. Productized hosted routes are for remote report work where Delx is paying for runtime, abuse controls, attribution, and public endpoint availability.

Parameter Contract

Productized report endpoints accept url as the canonical target parameter. Domain-like aliases such as domain, host, and website are accepted for compatibility, but docs should prefer url=https://example.com.

HTTP/1.1 422 Unprocessable Entity
{
  "ok": false,
  "code": "DELX-UTIL-1001",
  "status": "missing_required_input",
  "missing": ["url"],
  "schema_url": "https://api.delx.ai/api/v1/tools/schema/util_domain_trust_report"
}

Utility Families

• Web intelligence: util_page_extract, util_open_graph, util_links_extract, util_website_intelligence_report
• Internet plumbing: util_dns_lookup, util_tls_inspect, util_http_headers_inspect, util_url_health
• Discovery readiness: util_robots_inspect, util_sitemap_probe, util_feed_discover, util_openapi_summary
• x402 and commerce: util_x402_server_probe, util_x402_resource_summary, util_x402_server_audit
• Data transform: util_json_validate, util_csv_to_json, util_json_to_csv, util_jwt_inspect
• Operator basics: util_token_estimate, util_hash, util_uuid_generate, util_cron_describe

Compatibility Rules

• Keep existing /api/v1/x402/* and /api/v1/premium/* routes alive while they still receive traffic.
• Do not redirect POST routes. Serve utility results or structured schema hints with canonical metadata.
• Prefer headers such as x-delx-product: agent-tools and x-delx-compatibility-route: true before extracting a new service.
• Only create a separate repo/service when quotas, auth, billing, and telemetry are stable enough to justify the operational split.

Fetch Safety Rules

• Only http:// and https:// targets are valid.
• Private, loopback, link-local, multicast, reserved, and unspecified IPs are blocked after DNS resolution.
• Redirects are revalidated before following and capped to avoid redirect-based SSRF.
• Responses are size-limited and fetched with short timeouts.
• Rate limits and optional API keys are part of the utility surface, not the free Protocol witness layer.

Monetization Canary

Monetization belongs on utilities, not on the core witness protocol. The productized x402 routes now return HTTP 402 until a payment-capable agent sends a valid payment. Canonical product utility routes use the same payment boundary; free utilities remain callable without payment.

x-delx-utility-charge-mode: enforce
x-delx-utility-paid-candidate: true
x-delx-utility-price-usdc: 0.01