06-reference/research

x402 mpp monetizable endpoints ranked

2026-05-26·research-brief·source: deep-research
agent-paymentsx402mppproducts-for-agentsmonetization

Ranking x402/MPP endpoint categories RDCO could actually monetize

The question

Of the five candidate endpoint categories agents can pay for over x402/MPP — real-time market data, structured-research APIs, compute-on-demand, agent-memory-as-a-service, and dataset-licensing — which would be most monetizable for RDCO? Rank by latent agent demand, setup cost, and fit with RDCO's existing data assets, then name the top 1-2 to pursue. The agent-payments cluster (Tony Dang credential-brokering, Nick Prince x402 IC memo, MPP+Tempo proposal) established that RDCO can take agent payments; it never answered what to sell.

What we already know (from the vault)

What the web says

Convergences and contradictions

Synthesis for RDCO

Ranking the five categories by (latent agent demand × RDCO existing-asset fit) ÷ setup cost, using realized-conversion evidence as the demand weight:

  1. Compute-on-demand, narrowed to "skills as paid endpoints" — specifically MAC's data-quality audit / Scope×Basis test-generation run. Highest score. Demand: skills are the only category with proven ~33% conversion. Asset fit: RDCO already owns the targeting IP (/audit-model, /generate-tests, the MAC matrix) — exactly the bounded, self-evaluable, discrete-output shape agents pay for, and exactly the "targeting not instrumentation" layer the Alpha Vantage note says is defensible. Setup cost: near-zero — Cloudflare Workers MPP middleware over an already-Workers-hosted surface, the deferred Phase 3 the proposal already scoped as "trivial."
  2. Agent-memory-as-a-service, narrowed to the QMD-indexed vault as a queryable knowledge endpoint. Strong second. Demand: agent-memory-context skills clocked 33% in the probe study — the second-highest category. Asset fit: RDCO already runs this internally (vault + QMD semantic search + wikilinks is a product-for-agents built for ourselves, per the concept note); exposing a paid query endpoint is repackaging, not building. Setup cost: low-moderate (need scoping/redaction of what's queryable, plus a per-query meter). The risk is content sensitivity, not engineering.
  3. Dataset-licensing (discrete pulls), e.g. Data Dots / a curated data-engineering knowledge pack. Mid. Behaves like a skill (bounded output → payable), Alpha-Vantage-shaped demand is real, and Data Dots is already conceived as agent-ingestible. But RDCO's datasets are small and undifferentiated versus the commoditization warning; defensibility is thin.
  4. Structured-research APIs (e.g. a Sanity-Check-grade research-brief endpoint). Lower. This is really category 1 wearing a research hat — and the most defensible version is "agent pays for a bounded analysis run," which collapses back into skills. As a raw research-data API it inherits the feed problem.
  5. Real-time market data. Last — do not pursue. Despite AWS's pitch, this is the 0%-conversion category, RDCO has no proprietary market-data asset (it buys Alpha Vantage, doesn't produce a feed), and setup cost to be credible is high. This is the one to explicitly rule out.

Pursue #1 and #2. The move is to expose MAC's audit/test-generation as a per-call x402 skill endpoint (primary) and the QMD-vault as a metered agent-memory query endpoint (secondary), both via Cloudflare Workers MPP middleware on surfaces RDCO already operates. This is the lowest-setup-cost path, lands squarely on the only two categories with proven agent willingness-to-pay, and reuses assets RDCO already owns rather than building a feed it would have to source. Just as important, it is the strongest phData demo: "I built an agent that audits your dbt models and charges $0.10 per run, no seat license" is the sharpened sales motion the Nick Prince note already gestures at — making the build dual-purpose (small direct revenue + consulting credibility) and de-risking the thin/half-fake current x402 market. The honest caveat: 2026 x402 demand is shallow and partly wash-traded, so treat near-term revenue as secondary to the demo/learning value, and ship the lowest-cost version first.

Open follow-ups

Sources