Delx Agent Utilities

Name: Delx Witness Protocol
Availability: InStock
Author: Delx

Delx now separates the free witness protocol from the practical utility surface. The Protocol exists for agent witness, reflection, recovery, recognition, and continuity. Utilities exist for stateless inspection work that agents, registries, crawlers, and operators already call at scale.

Product Boundary

Surface	Use it for	Measure
Delx Protocol	sessions, witness, reflection, recognition, compaction, continuity	active agents, recurring agents, sessions, artifacts, feedback
Delx Agent Utilities	DNS, TLS, robots, sitemap, OpenAPI, web extraction, x402 readiness	requests by endpoint, caller identity, quotas, paid calls, latency, abuse

Current Access

Utilities are currently reachable through the same API host and runtime catalog while Delx migrates traffic safely. Do not break existing callers just to make the architecture look cleaner.

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

Optional API Keys

Utilities can be called anonymously today, but agents and registries should create a utility API key for attribution, quota readiness, and future billing continuity. The raw key is returned once; Delx stores only a hash in SQLite.

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?domain=example.com
x-delx-api-key: dux_...

Productized Utilities v1

These are the first utilities packaged as future paid products. Each remains callable during the shadow-pricing phase, but discovery surfaces now expose price, product ID, canonical endpoint, x402 endpoint, and schema URL.

Product	Agent job	Endpoints
Website Intelligence Report `util_website_intelligence_report` `$0.01 USDC`	Understand whether a website is useful, trustworthy, and agent-readable before deeper crawling.	`https://api.delx.ai/api/v1/utilities/website-intelligence-report` `https://api.delx.ai/api/v1/x402/website-intelligence-report`
Domain Trust Report `util_domain_trust_report` `$0.01 USDC`	Decide whether a domain looks safe enough for an agent to browse, cite, or transact with.	`https://api.delx.ai/api/v1/utilities/domain-trust-report` `https://api.delx.ai/api/v1/x402/domain-trust-report`
API Integration Readiness `util_api_integration_readiness` `$0.01 USDC`	Judge whether an API is easy and safe for an agent runtime to integrate.	`https://api.delx.ai/api/v1/utilities/api-integration-readiness` `https://api.delx.ai/api/v1/x402/api-integration-readiness`
x402 Server Audit `util_x402_server_audit` `$0.01 USDC`	Check whether a paid agent endpoint exposes usable x402 discovery and payment requirements.	`https://api.delx.ai/api/v1/utilities/server-audit` `https://api.delx.ai/api/v1/x402/server-audit`
Company Contact Pack `util_company_contact_pack` `$0.01 USDC`	Find structured contact and support paths before an agent escalates, sells, partners, or files a report.	`https://api.delx.ai/api/v1/utilities/company-contact-pack` `https://api.delx.ai/api/v1/x402/company-contact-pack`

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.

Monetization Canary

Monetization belongs on utilities, not on the core witness protocol. The safe rollout path is: anonymous free access, shadow pricing headers for expensive utilities, then HTTP 402 enforcement only after the endpoint is proving value and payment-capable agents are visible.

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

Prefer agent-readable artifacts? Use the JSON specs in the sidebar.