DEV Community

Peter
Peter

Posted on

Your UCP Profile is Detected. But AI Agents Still Can't Buy From You.

#ucp #agenticcommerce #ecommerce #webdev

Your UCP Profile is Detected. But AI Agents Still Can't Buy From You.

We scanned 111 e-commerce stores. 35 of them have UCP profiles that pass validation. But not a single one can actually complete a purchase with AI agents.

Here's why: these "Grade C" stores all share the same 3 critical missing fields.

The Grade C Trap: Detection ≠ Readiness

Every store in the Grade C category (score: 60-79) has UCP manifest files that basic validators like UCPChecker.com report as "valid." They pass structural validation, network connectivity, and even basic schema checks.

But when AI agents actually try to interact with these stores, they fail. Every single time.

The problem isn't that these stores lack UCP profiles. The problem is that their profiles lack 3 specific fields that AI agents need to complete transactions.

The 3 Missing Fields Break AI Commerce

1. Missing signing_keys - The Trust Gap

What it is: Cryptographic verification that the UCP manifest hasn't been tampered with.

Why agents need it: AI agents need to verify that the UCP profile they're interacting with is authentic and hasn't been maliciously modified.

Impact: Without signing keys, AI agents cannot trust the UCP profile, making the entire interaction insecure.

Prevalence: 19.8% of stores with UCP profiles lack signing keys, but 100% of Grade C stores are missing them.

2. Missing payment_handlers - The Purchase Blocker

What it is: Configuration that tells AI agents how to process payments for the store.

Why agents need it: AI agents need to know which payment methods to use, how to format payment requests, and how to handle payment processing.

Impact: Without payment handlers, AI agents cannot complete purchases. They can discover the store and browse products, but they can't buy anything.

Prevalence: 22.5% of stores with UCP profiles lack payment handlers, but 100% of Grade C stores are missing them.

3. Missing return_policy Schema - The Trust Builder

What it is: Structured data about return policies, warranties, and refund terms.

Why agents need it: AI agents need to show customers trust signals before making purchases. Return policies are one of the most important trust signals for e-commerce.

Impact: Without return policy schema, AI agents cannot display return terms, build customer trust, or handle post-purchase service.

Prevalence: 48.6% of all stores lack return policy schema, but 100% of Grade C stores are missing them.

Why This Matters for Agentic Commerce

The Grade C pattern reveals a critical gap in current UCP implementations:

Stores pass "presence" validation but fail "interaction" validation.

This means:

  • AI discovery works (agents can find the store)
  • Product browsing works (agents can see products)
  • But purchasing fails (agents cannot complete transactions)

For agentic commerce to work, we need to move beyond "is UCP present?" to "can UCP actually facilitate commerce?"

How to Fix Your Grade C Profile

The good news: these are configuration issues, not platform limitations. Here's how to address each:

1. Add Signing Keys 

{
  "signing_keys": [
    {
      "key_id": "your-key-id",
      "public_key": "your-public-key-here",
      "algorithm": "ES256"
    }
  ]
}
Enter fullscreen mode Exit fullscreen mode

2. Configure Payment Handlers 

{
  "payment_handlers": [
    {
      "payment_method": "credit_card",
      "supported_networks": ["visa", "mastercard", "amex"],
      "capabilities": ["supports_installments", "supports_3d_secure"]
    },
    {
      "payment_method": "paypal",
      "capabilities": ["supports_paypal_vault"]
    }
  ]
}
Enter fullscreen mode Exit fullscreen mode

3. Add Return Policy Schema 

{
  "return_policy": {
    "return_window_days": 30,
    "return_shipping_paid_by": "merchant",
    "refund_method": "original_payment_method",
    "exceptions": ["final_sale_items", "custom_products"],
    "restocking_fee_percent": 0
  }
}
Enter fullscreen mode Exit fullscreen mode

The BigCommerce Platform Bug

Our scans reveal a specific pattern affecting BigCommerce stores:

  • Issue: dev.ucp.shopping service missing required spec field
  • Issue: REST transport missing required schema field
  • Result: All report UCP_INVALID_SERVICE errors

This appears to be a platform-level issue in BigCommerce's UCP implementation. BigCommerce merchants should verify their REST schema fields and contact BigCommerce support if these fields are missing.

Who's Affected?

All 35 Grade C stores share these exact same failures, including:

  • SaaS agencies: obundle.com, papathemes.com
  • Fashion DTC: allbirds.com, brooklinen.com, chubbiesshorts.com, fashionnova.com
  • Home Decor: curatedhomedecor.com, interiordelights.net, feldkampsfurniture.com
  • Beauty: kyliecosmetics.com

These aren't small, unknown stores. These are established brands with UCP profiles that "pass validation" but fail at AI commerce.

The Reality Check

65% of stores have zero UCP profiles.
Zero stores are fully AI-agent ready.
35 stores have "broken but detectable" UCP profiles.

The state of agentic commerce readiness is worse than most merchants realize. Having a UCP profile isn't enough. Your profile actually needs to work with AI agents.

Test Your AI Readiness

Don't trust basic validation. Test your actual AI commerce readiness:

  1. Check your signing keys: Can your manifest be cryptographically verified?
  2. Test payment handlers: Can AI agents process payments on your store?
  3. Verify return policy: Do agents have access to your return terms?

The gap between "UCP detected" and "AI commerce ready" is where most merchants are stuck. Fixing these 3 fields is the bridge from discovery to actual transactions.

Data from UCPtools AI Readiness Index (111 domains scanned, April 13, 2026)

Test your store's actual AI readiness at ucptools.dev?utm_source=devto&utm_medium=article&utm_campaign=202604

Top comments (0)