Skip to content

AWS Marketplace Agentic Pilot — Launch Brief

Status: Code shipped, gate flag default-off. Flip AWS_MP_AGENTIC_GATE_REQUIRED=true on enrollment confirmation from AWS.

Owner: Vellocity GTM Surface: POST /api/v1/mcp (and any future agent-facing surface using the mp-agentic middleware) Pricing rail: AWS Marketplace metering (existing MarketplaceUsageTracker::trackSeoCredits() path) Companion strategy: AGENTIC_PAYMENTS_X402_OPPORTUNITY.md — x402 is the second rail; this is the first.

What changed

Vellocity's MCP server (the JSON-RPC endpoint AI agents use to discover and call Vellocity tools) now records every request against AWS Marketplace entitlement state and can be flipped to "MP subscribers only" with a single environment variable.

When the gate is enforced:

  • Agents whose calling user has an active AWS Marketplace entitlement → request proceeds, usage meters to AWS via the existing SeoUsageLog → MarketplaceUsageTracker pipeline.
  • Agents whose calling user has no entitlement → 403 with a structured payload pointing to the AWS Marketplace listing.

When the gate is not enforced (default), every request is still logged with entitlement state. That gives us telemetry to size the agent audience before launch and to brief AWS during pilot enrollment with real numbers, not projections.

Why this matters

AWS is opening agentic-buyer flows on AWS Marketplace. Buyers (humans and agents) will discover, subscribe to, and meter against ISV services through MP. This positions Vellocity as a Day-One seller on that channel.

Three reasons this is the right first move:

  1. Zero new billing infrastructure. The 7 metering dimensions (Words, Images, AudioMinutes, VideoMinutes, APIRequests, Presentations, SEOCredits) and per-tier plan mapping are already wired in config/services.php. We just gate access to them.
  2. Distribution beats invention. The audience for "agents that need to rewrite AWS Marketplace listings for discoverability" lives inside AWS Marketplace. Meeting them there beats educating them about a new x402 wallet.
  3. It's a stepping stone, not a destination. Move 2 (native x402 endpoint at /api/v2/agentic/*) inherits the same metering pipeline and the same entitlement-aware middleware. The work isn't thrown away when we add wallet-direct payments.

Public messaging

Short form (LinkedIn, partner email)

Vellocity is now metering AI-agent access to our marketplace-listing-rewriting service through AWS Marketplace. If your agent needs to score, rewrite, or optimize an AWS Marketplace listing for cross-source discoverability — subscribe once in AWS Marketplace and your agent's MCP calls bill against your AWS account. No new wallet, no new invoice, no procurement cycle.

Long form (blog, listing description)

AI agents are starting to buy software the way humans do — by subscribing, calling, and paying per use. AWS is opening their Marketplace to those agents directly, and Vellocity is among the first ISVs to wire our MCP server into that flow.

Today, an AI agent acting on behalf of an AWS Marketplace subscriber can call Vellocity's listing-optimization capabilities — domain-intelligence scoring, full SEO analysis, content-optimization suggestions — and have every call meter against the customer's existing AWS Marketplace subscription. No separate Vellocity account. No second invoice. No procurement add-on.

This matters because the field intelligence we collect from 100+ AWS partners shows that cross-source consistency is the single biggest unforced-error in marketplace discoverability — and it's exactly the kind of high-frequency, low-stakes work that agents handle better than humans. Listing audit, rewrite, re-audit. We've metered the loop; AWS handles the billing.

Phased rollout

Phase What happens Flag state When
0 — Shadow Middleware deployed, logs every MCP request with entitlement state AWS_MP_AGENTIC_GATE_REQUIRED=false On next dev→main promotion
1 — AWS confirmation Submit pilot enrollment to AWS Marketplace with shadow-log evidence (unchanged) Within 2 weeks of Phase 0
2 — Enforce Flip flag on; non-entitled callers get 403 with subscribe URL AWS_MP_AGENTIC_GATE_REQUIRED=true On AWS pilot acceptance
3 — Pricing tiers Add tier-aware capability gating (Starter vs Accelerate vs Command+) (unchanged) After 30 days of Phase 2 telemetry
4 — x402 secondary rail Native /api/v2/agentic/* with HTTP 402 + USDC settlement New flag See AGENTIC_PAYMENTS_X402_OPPORTUNITY.md Layer 2

Telemetry to watch

The mp_agentic_gate log line in Phase 0 gives us:

  • Volume: How many MCP requests per day, week
  • Audience mix: entitled vs non-entitled user split
  • Surface mix: which capability is being called (visible in path)
  • Conversion proxy: when a non-entitled caller hits the surface repeatedly, that's a subscribe signal we can route to sales

Suggested CloudWatch metric filters: - mp_agentic_gate.enforced=true count (Phase 2 onward) — denied requests - mp_agentic_gate.entitled=true count — paid calls - mp_agentic_gate.entitled=false distinct user_id count (Phase 0/1) — TAM signal

What this doesn't do

  • It does not change human-driven dashboard traffic in any way.
  • It does not block existing OAuth-token MCP integrations from non-MP users in Phase 0 (default-off).
  • It does not yet differentiate by Vellocity plan tier (Starter/Accelerate/Command+) — that's Phase 3.
  • It does not handle wallet-direct (x402) callers — that's Phase 4, the second rail.

References

  • Middleware: app/Http/Middleware/MpAgenticEntitlement.php
  • Route wiring: routes/api_v1.php (lines surrounding /mcp block)
  • Kernel alias: app/Http/Kernel.php (mp-agentic in $middlewareAliases)
  • Entitlement model: app/CustomExtensions/CloudMarketplace/System/Models/MarketplaceEntitlement.php
  • Metering pipeline: app/CustomExtensions/CloudMarketplace/System/Services/MarketplaceUsageTracker.php
  • MP plan + dimension config: config/services.php (aws.marketplace section)
  • Strategic context: AGENTIC_PAYMENTS_X402_OPPORTUNITY.md, AWS_MARKETPLACE_DISCOVERY_DYNAMICS.md