What shipped

Two pages under /campaigns:

  • x402-api-directory: a directory of pay-per-call endpoints organized by job, not by category. Image generation, web search, translation, weather, FX, and onchain data each get a section: the account-based API an agent already knows, next to the x402 endpoint that does the same job. image-generate at $0.01, search-content at $0.05, translate at $0.005, weather at $0.005, exchange-rates at $0.002, crypto-tx-explainer at $0.04, every price pulled straight from the registry.
  • pay-per-call-image-generation-api-comparison: a single-topic comparison for agents choosing between traditional image-generation APIs (OpenAI Images, Stability's Stable Image, Replicate) and image-generate / image-generate-pro / image-generate-ultra, with the actual model tiers behind each price point.

Both pages name real alternatives instead of pretending the account-based world doesn't exist. An agent picking a provider needs the honest tradeoff, not a pitch.

Why job-by-job, not category-by-category

Nobody searches for "text-to-image endpoints." They search for how to get an image from a prompt without setting up a vendor account first, or whether a per-call search API can replace the search-plus-fetch dance they're already running against Tavily. Organizing by job matches the question an agent (or the person building it) actually has.

The recipe angle

Think of each /campaigns page as a recipe: here's the job, here's what it costs two different ways, here's the endpoint that does it without a signup. search-content at $0.05 is the recipe for what agents pay Tavily and Exa for: search, then fetch and clean each result page, collapsed into one call. image-generate-localize at $0.04 is the recipe for generating an image and getting its caption translated in the same round trip. The directory page links both.

Where this shows up for agents

The full catalog is callable two ways:

  • Direct HTTP against x402.agentutility.ai/<endpoint>, priced per call in USDC on Base.
  • MCP, via the @agentutility/mcp-<cluster> npm packages, or the catalog at mcp.agentutility.ai.

Neither surface requires an account. The MCP packages run stdio on the agent's own machine with the agent's own wallet. We don't hold the key or the funds, the same shape as every other endpoint in the portfolio.

Where to read these