DELXCOMMERCE 36 packs

36 free navigation packs · 996 governed APIs

AI agent API packs, organized by outcome

Delx Commerce has 36 free navigation packs that group 996 governed pay-per-result APIs by job. A pack is not a bundle or subscription: inspect its JSON, choose one exact route, verify price, schema, and limits, then pay only for that delivered result.

Choose one route, not a bundle.

Use these packs to reduce search space. The pack is free; its routes remain independently priced, independently contracted, and payable only when called.

Decision path

From outcome to verified delivery.

  1. 01

    Choose the outcome

    Start with one category and select the pack closest to the job your agent must complete.

  2. 02

    Inspect the pack JSON

    Read the machine card for candidate routes, input examples, prices, and source attribution.

  3. 03

    Verify one route

    Check the exact route contract, current 402 challenge, schema, limits, and delivery terms before payment.

  4. 04

    Pay and verify delivery

    Call only the chosen route with its x-delx-source header, then verify the delivered result and receipt.

4 packs

Start with proven paths

Low-friction entry points and deterministic primitives for a first governed call.

8 packs

Build and integrate

Readiness checks, identifiers, data shaping, and small utilities for production agent workflows.

01
Agent builders and API maintainersShip an AI agent integration

A seven-check launch path for an API or MCP server: verify health, OpenAPI, MCP tool discovery and x402 payment metadata before giving an autonomous agent authority.

7 routes
02
Content, growth and documentation teamsMake a content site agent-readable

Find feeds, links, Open Graph, forms and distribution gaps that determine whether agents can discover and cite a site.

6 routes
03
Automation and operations agentsPrepare small data files for an agent

Use bounded, stateless transformations to move small CSV and JSON payloads between the formats agents already consume.

6 routes
04
Developer, automation and operations agentsRun deterministic utility primitives

Keyless micro-transforms between bigger tool calls: JSON, tokens, IDs, timestamps, URLs, hash, regex, cron and HTTP codes at $0.001—pay only on success.

10 routes
05
Content, support and automation agentsText micro-utils for agents ($0.001)

Pure-local text helpers at $0.001: title/sentence case, char counts, wrap, accents, punctuation strip, redact emails, and mask secrets—no NLP vendor key.

10 routes
06
Platform and automation agentsIDs and slugs for agent workflows

Mint URL-safe NanoIDs, time-sortable IDs, URL→slug, and host extraction at $0.001 for jobs, drafts, and cache keys—without shipping nanoid locally.

6 routes
07
Ops, product and analytics agentsCheap stats for agent metrics

Lightweight stats at $0.001: mean, median, stdev, and percentile on numeric arrays—for p50/p95 style summaries without a stats stack.

4 routes
08
Automation and data agentsJSON and CSV micro-helpers

Shape small payloads at $0.001: pretty/minify JSON, list keys, root type, CSV headers and row counts—stateless, first-party.

7 routes

10 packs

Research and open data

Attributed research, website inspection, public knowledge, weather, geocoding, and reference rates.

01
Research, editorial and evidence-synthesis agentsBuild research from supplied pages and attributed open sources

Combine caller-supplied page extraction and website intelligence with attributed GDELT, Wikipedia and Wikidata results, then normalize citations. This is not general web search: it does not proxy licensed search engines, resell article bodies or claim exhaustive coverage.

7 routes
02
Research, sales and support agentsUnderstand a website before relying on it

Start with one bounded report, then drill into page content, links, contacts, docs, pricing and distribution signals.

9 routes
03
Research, GTM, support and coding agentsExtract website content without a search license

Conversion pack for agents that need page text or a one-call website intelligence report at $0.01 each—rights-clean first-party fetch, not Tavily/Exa/OpenSerp web search.

2 routes
04
Research, monitoring and editorial agentsResearch recent news with attributed links

A bounded news-research path that returns recent GDELT Project metadata and publisher links with explicit attribution, without reselling article bodies.

1 routes
05
Web3, research and monitoring agentsResearch crypto headlines with sources

A bounded Web3 research path for attributed crypto headline metadata at $0.001, with no article-body resale, market quotes, prices, sentiment or trading advice.

1 routes
06
Research, education and knowledge agentsResearch open knowledge with attributed sources

A bounded English Wikipedia research path at $0.001 with page links, short snippets, license metadata and explicit limits—never a general web-search or article-body proxy.

1 routes
07
Research, maps and company agentsFind public entities and places

A bounded Wikidata research path at $0.001 with stable IDs, labels, descriptions and source links under CC0; it is not geocoding, navigation, live company data, contact data or personal profiling.

1 routes
08
Travel, logistics and scheduling agentsPlan around a US weather forecast

A coordinate-first weather path for agents that need a bounded US forecast with source attribution, cache behavior and no arbitrary URL proxy.

1 routes
09
Logistics, scheduling and location agentsGeocode a US address before a location workflow

A bounded address-to-coordinate path for agents that need a U.S. location primitive before scheduling, logistics or a later approved maps workflow.

1 routes
10
Finance, commerce and travel agentsConvert currencies with a sourced reference rate

A bounded FX path for agents that need daily ECB reference rates or cross-rates with source attribution, not order execution or trading advice.

1 routes

3 packs

Trust and security

Bounded defensive signals for domains, HTTP surfaces, and sensitive text before an agent proceeds.

4 packs

Payments and x402

Preflight, compare, diagnose, and verify pay-per-result integrations without treating discovery as payment.

01
x402 origin operators and agent-commerce platform teamsDebug an x402 origin that is live but not indexed

Trace the common gap between a healthy payable origin and a stale directory: challenge shape, payload size, catalog/OpenAPI/registry route parity and decision-grade copy. These checks prepare a safe recrawl request; they do not press a provider refresh button or promise indexing.

8 routes
02
Buyer agents, marketplaces and paid-tool integratorsPreserve proof from x402 payment through delivery

Walk a caller-supplied purchase artifact through payment preflight, response-header shape, settlement transaction shape, receipt, delivery hash, idempotency and retry safety. It validates evidence already held by the buyer; it never reconstructs a missing receipt or performs a payment.

7 routes
03
Autonomous buyers, wallet operators and payment engineersPreflight a Base payment before an agent spends

Combine live Base gas context with deterministic budget, freshness, fee, USDC amount, recipient, payment-match and receipt checks before an autonomous buyer spends. The pack is read-only and validation-only: it never signs, broadcasts, approves or transfers assets.

8 routes
04
Buyer agents, procurement agents and x402 directory buildersEvaluate an x402 service before an agent pays

Inspect a resource summary, protocol response, server contract, domain signals, price drift and delivery expectations before choosing a paid endpoint. This is deterministic technical diligence and does not provide human reviews or reputation, verified identity or a quality guarantee.

7 routes

3 packs

Media and documents

Outcome paths for generated assets, PDFs, scans, and OCR with route-level contracts.

4 packs

Chain and markets

Deterministic network, unit, trading-risk, and prediction-market math for agent decisions.

FAQ

Before an agent chooses.

What is an AI agent API pack?

A free navigation card that groups existing governed APIs around one outcome. It helps an agent narrow the catalog before choosing a route.

Does a pack charge one bundle price?

No. A pack is not a bundle, subscription, or purchase. Every route keeps its own price and contract, and payment happens only when that route is called.

How should an agent read a pack?

Open the pack JSON, compare its routes and examples, inspect the selected route's current contract, and preserve the provided x-delx-source attribution header.

Does every pack contain all 996 APIs?

No. Each pack is a curated path for one job. The complete governed catalog remains available through the product index, discovery graph, portfolio, and OpenAPI document.

Does appearing in a pack prove a route is safe for every use?

No. A pack proves only that the route belongs to the governed live catalog and matches the stated navigation path. Buyers must still verify fit, price, schema, policy, and delivery.

Machine-readable references.