Agent Commerce for Pet Products — Autoship, Prescription Meds, and the Three Buyer Segments.

High frequency, deep loyalty, strong subscriptions — and a dominant incumbent with no public API.

Pet commerce is one of the highest-value fits for autonomous agent mediation in all of retail. Three structural facts explain why. First, purchase frequency is extremely high: the same brand, same formula, and same bag size get ordered on a monthly or biweekly cadence. There is no discovery phase for a routine resupply purchase — the decision is already made, and the only remaining task is logistics. Second, brand loyalty in pet food is notably stronger than in most consumer categories: once a dog thrives on a formula, owners rarely switch. Third, subscription penetration is already deep — Chewy's Autoship program, Amazon Subscribe & Save, and Petco's Repeat Delivery have conditioned a significant segment of pet owners to recurring-purchase thinking. That combination — frequency, loyalty, subscription — is structurally identical to what the UCP recurring-billing model was designed to automate.

The US pet industry generated $158 billion in total expenditure in 2024, with pet food and treats alone accounting for $68.3 billion — the single largest category — and $165 billion is projected for 2026 (re-verify before launch; source: American Pet Products Association). That food-and-treats category is almost entirely recurring spend, which means the agent-commerce opportunity in this vertical is concentrated not in discovery but in execution: set up the recurring authorization once, let the agent manage the cadence, and surface only the exceptions that require human judgment (price increases, substitutions, prescription renewals).

The reigning agent-readable retailer is Chewy. Its Autoship program combines recurring delivery, per-item discounts (5% ongoing; up to 35–50% on first orders, re-verify before launch), prescription delivery through Chewy Pharmacy LLC, and a full app-based management interface. Chewy's architecture already implements most of what the 4-Layer model describes: structured product data, a first-party storefront, repeating purchase contracts, and a management surface. What Chewy has not done is expose those capabilities as an MCP-compatible tool layer accessible to third-party agents. There is no public consumer or merchant API. That gap defines the independent-seller opportunity.

The agent-commerce wedge for independent sellers sits at four edges Chewy's volume economics and curation overhead leave under-served: pet memorial products (cremation urns, portrait prints, memorial jewelry — the primary adjacency to the grief-ethics segment); niche treat and toy brands (breed-specific, allergy-aware, enrichment-focused, sustainably sourced); vet-recommended specialty foods (fresh, raw, and prescription-adjacent DTC brands like The Farmer's Dog, Nom Nom, and Open Farm); and pet-tech accessories (GPS collars, smart feeders, health monitors — high-margin, low-repeat, brand-differentiable SKUs).

Three segments. Three agent-behavior modes. One framework.

The pet buyer's journey splits into three behaviorally distinct segments. These mirror the EtsyPetMemorial pillar's segmentation and should be used to configure agent behavior flags — not merely to categorize customers. Segment misidentification is the costliest implementation error in pet-product agent commerce.

Segment 1: Routine Resupply

The Routine Resupply buyer has already made every decision. The brand is chosen, the formula is set, the bag size is fixed. The agent's role is pure logistics: confirm the cadence, authorize the recurring charge under the spending cap, and escalate only when something unexpected happens — a price change outside the cap, a product substitution, or a prescription requiring annual renewal. This is the segment where the UCP cap-and-authorize pattern delivers its highest return. At Layer 1, this segment requires autoshipCadence, autoshipAvailable: true, and explicit subscription pricing in a UnitPriceSpecification offer. At Layer 3, subscribe_autoship and modify_autoship are first-class operations. Chewy's Autoship program is the dominant platform-side expression of this pattern — but it has no public API, which means any agent-automated Routine Resupply workflow must run through Shopify Selling Plans, WooCommerce Subscriptions, or another platform with a documented subscription API.

Segment 2: New-Pet Concierge

The adoption moment is a high-anxiety, high-spend decision cluster. A new owner who just brought home a 10-week-old Labrador faces simultaneous decisions: food (which brand, what formula, puppy vs. all-life-stages), crate (current puppy size or adult size for life?), collar and harness, ID tag, training treats, vet-visit supplies, and parasite prevention — all with breed-specific constraints they may not know. The decisions are interdependent: crate size depends on projected adult weight, food amount depends on current weight and age, harness fit changes monthly for a large-breed puppy. The agent solves this by running a profile intake (assemble_starter_kit(species, breed, ageWeeks, estimatedAdultWeightLbs)), tagging each kit item as one-time or recurring, and presenting the full set with structured reasoning. An indie Shopify seller with complete targetBreed, lifeStage, and breedSizeCategory fields will surface more accurately in an agent-assembled starter kit than a large retailer with sparse category metadata. See Shopify Selling Plans for the subscription API that powers the recurring portion of the kit.

Segment 3: Grief / Recent Loss

The grief segment is covered in depth in the grief-purchase ethics section below and in the EtsyPetMemorial pillar. The short version: an optimization-driven agent in grief context will misfire. Standard agent behaviors — surface related products, apply urgency triggers, recommend frequently-bought-together items — are harmful here. The agent's role is to surface the right product with minimal friction and then exit. The implementation path is the behaviorMode: "grief" parameter on search_products and the grief_aware: true flag in the capability manifest on your /agents page.

Where pet products are sold — and which platforms have APIs agents can actually use.

The practical takeaway for any operator building agent-accessible pet commerce: the only platforms with documented APIs that indie sellers can use today are Amazon (SP-API), Walmart Marketplace API, Shopify (Selling Plans API for autoship-equivalent), WooCommerce (Subscriptions plugin REST API), BigCommerce (Channels API + app layer), and Etsy (Open API v3 for memorial/one-time sellers). See Shopify and Etsy spoke pages for platform-specific implementation guides.

The VCPR gate — the regulatory step no agent can bypass.

Prescription pet medications represent the hardest constraint in pet-product agent commerce: the Layer 4 UCP spending cap can authorize recurring prescription refills, but it cannot substitute for the VCPR requirement. An agent that attempts to complete a prescription purchase autonomously without surfacing the authorization gate is not malfunctioning — it is producing a compliance failure.

The Regulatory Framework

Three interlocking regulations govern prescription pet medications in the US:

• VCPR (Veterinarian-Client-Patient Relationship): A valid, established VCPR must exist before any prescription can be written or refilled. State definitions of VCPR vary — sellers and agents must consult each state's veterinary practice act. The American Veterinary Medical Association (AVMA) publishes a pet-owner FAQ on prescriptions and pharmacies that summarizes the landscape.
• State Board of Pharmacy (BOP) regulations: Each state sets rules for acceptable prescription transmission formats (fax, phone, written, electronic). Chewy's pharmacy team explicitly contacts vets to convert email prescriptions into verbal prescriptions, regardless of specific state BOP rules.
• VCPR refill limits: To comply with state VCPR regulations, total prescription fills and refills cannot exceed a one-year supply. This creates a hard annual renewal gate that must be encoded at Layer 4.

Chewy Pharmacy Authorization Flow

Chewy Pharmacy is operated by Chewy Pharmacy, LLC (a separate legal entity). Contact: 877-977-3879 / rx@chewy.com. The four triggers for vet-pharmacist contact are:

1. Customer purchases medication and submits a photocopy of the prescription themselves.
2. Customer purchases medication and asks Chewy to contact the vet directly.
3. Reviewing pharmacist flags the prescription for clarification or confirmation.
4. Prescription received from the prescriber via email — always requires phone verification to convert to a verbal prescription, regardless of state BOP rules.

Vet-to-pharmacy transmission methods accepted: Fax (866-253-0274); Mail to 3621 Fern Valley Rd, Louisville, KY 40219 (all Rx except gabapentin) or 360 Research Drive, Pittston, PA 18640 (gabapentin only); PracticeHub (Chewy Health's digital prescription management platform for veterinary practices); Phone (verbal prescription, where state-permitted).

Agent Implications for Prescription Products

What the 4-Layer Model looks like when you add species, life stage, and the Rx gate.

The 4-Layer Agent-Ready Model (Structured Data → API Endpoint → MCP Tool Description → UCP Compatibility) is documented at AgentMall Roadmap. The model does not change for pet products — the implementation at each layer does. This section maps every pet-specific addition.

Layer 1: Complete JSON-LD Example — Pet Food with Subscription and Prescription Fields

The following is a complete, runnable JSON-LD block for a pet food product with both a one-time offer and a subscription offer. Use this as your baseline template. Entity-encode <, >, and & inside code blocks.

{
  "@context": "https://schema.org/",
  "@type": "Product",
  "name": "HypoAllergenic Salmon & Sweet Potato Adult Dog Food",
  "sku": "HSSF-DRY-15LB",
  "gtin12": "012345678901",
  "description": "Grain-free, single-protein dry dog food for adult dogs with food sensitivities. Veterinarian-recommended for dogs with chicken or beef protein allergies.",
  "brand": {
    "@type": "Brand",
    "name": "NutriCanine"
  },
  "image": "https://www.example-petstore.com/images/hssf-dry-15lb.jpg",
  "weight": {
    "@type": "QuantitativeValue",
    "value": 15,
    "unitCode": "LB"
  },
  "additionalProperty": [
    { "@type": "PropertyValue", "name": "species", "value": "dog" },
    { "@type": "PropertyValue", "name": "lifeStage", "value": "adult" },
    { "@type": "PropertyValue", "name": "breedSizeCategory", "value": "medium" },
    { "@type": "PropertyValue", "name": "ingredients", "value": "Salmon, Sweet Potato, Pea Protein, Salmon Meal, Canola Oil, Flaxseed, Dried Chicory Root, Salmon Oil, Vitamins, Minerals" },
    { "@type": "PropertyValue", "name": "allergens", "value": "fish" },
    { "@type": "PropertyValue", "name": "allergensFree", "value": "chicken, beef, grain, egg, dairy, soy" },
    { "@type": "PropertyValue", "name": "prescriptionRequired", "value": "false" },
    { "@type": "PropertyValue", "name": "autoshipAvailable", "value": "true" },
    { "@type": "PropertyValue", "name": "autoshipCadence", "value": "4 weeks" },
    { "@type": "PropertyValue", "name": "productCategory", "value": "dry-dog-food" }
  ],
  "offers": [
    {
      "@type": "Offer",
      "name": "One-Time Purchase",
      "price": "52.99",
      "priceCurrency": "USD",
      "availability": "https://schema.org/InStock",
      "url": "https://www.example-petstore.com/products/hssf-dry-15lb",
      "itemCondition": "https://schema.org/NewCondition",
      "priceSpecification": {
        "@type": "UnitPriceSpecification",
        "price": "52.99",
        "priceCurrency": "USD"
      }
    },
    {
      "@type": "Offer",
      "name": "Subscribe & Save — Every 4 Weeks",
      "price": "50.34",
      "priceCurrency": "USD",
      "availability": "https://schema.org/InStock",
      "url": "https://www.example-petstore.com/products/hssf-dry-15lb?autoship=true",
      "itemCondition": "https://schema.org/NewCondition",
      "priceSpecification": {
        "@type": "UnitPriceSpecification",
        "price": "50.34",
        "priceCurrency": "USD",
        "billingDuration": {
          "@type": "QuantitativeValue",
          "value": 4,
          "unitCode": "WEE"
        },
        "billingStart": 0
      },
      "description": "5% discount applied to every recurring order. Cancel or modify anytime."
    }
  ]
}

Layer 2: API Endpoints — Platform Subscription APIs

Layer 3: MCP Tool Signatures — Pet Products Minimum Viable Tool Set

search_products(
  query: string,
  species: "dog" | "cat" | "bird" | "reptile" | "small-animal" | "fish",
  lifeStage?: "puppy" | "kitten" | "adult" | "senior",
  breedSizeCategory?: "toy" | "small" | "medium" | "large" | "giant",
  prescriptionRequired?: boolean,
  autoshipAvailable?: boolean,
  allergenExclusions?: string[],
  productCategory?: string,
  behaviorMode?: "standard" | "grief",
  limit?: number
) → ProductListing[]

check_prescription_required(
  sku: string
) → { prescriptionRequired: boolean, controlledSubstance: boolean, vcprRequired: boolean }

subscribe_autoship(
  sku: string,
  quantity: number,
  cadenceWeeks: number,
  paymentMethodToken: string,
  shippingAddressId: string
) → SubscriptionContract

modify_autoship(
  contractId: string,
  updates: {
    cadenceWeeks?: number,
    quantity?: number,
    skipNextOrder?: boolean,
    pauseUntil?: date
  }
) → SubscriptionContract

get_pet_profile(
  petId: string
) → {
  name: string,
  species: string,
  breed: string,
  weightLbs: number,
  lifeStage: string,
  allergens: string[],
  activeSubscriptions: SubscriptionContract[]
}

assemble_starter_kit(
  species: string,
  breed: string,
  ageWeeks: number,
  estimatedAdultWeightLbs?: number
) → StarterKitRecommendation[]

For check_prescription_required: when prescriptionRequired: true is returned, the MCP server must block execution of subscribe_autoship until a prescriptionAuthorizationToken (representing a completed vet-authorization workflow) is present in the call. This is the hard gate that prevents autonomous purchase of regulated medications. For the base MCP protocol reference, see /agentmall_spoke_mcp.

Layer 4: UCP Contract Patterns by Segment

The UCP recurring-billing pattern fits the Routine Resupply segment directly. Pet-products add four segment-specific adaptations:

• Autoship discount pass-through: The spending cap must reflect the post-discount subscription price, not the one-time price. A cap set at the one-time price wastes authorization headroom and can reject the subscription variant unexpectedly if prices diverge.
• Prescription renewal gate: UCP contracts for prescription items must include a prescriptionExpiresDate field and an annual renewal checkpoint. The agent cannot auto-renew past this point without flagging for user re-authorization.
• Starter-kit hybrid contract: For the New-Pet Concierge pattern, the UCP contract is a hybrid — single-purchase authorization for hardware items (crate, collar, bed), plus recurring-billing authorization for consumables (food, treats, preventatives). Structure these as separate contract entries, not a single mixed-type contract.
• Grief-segment override: For productCategory: "pet-memorial", the UCP contract must be one-time only. No autoship or recurring-billing options should be offered or pre-configured.

When the optimization function is the wrong objective.

The grief segment is addressed in the EtsyPetMemorial pillar as the foundational emotional context for memorial product sales. The agent-commerce framing is different but adjacent: the problem is not that commerce doesn't happen — it does — but that standard optimization-driven agent behaviors actively harm the user in this context.

Standard e-commerce agent behaviors that must be suppressed in grief context: surfacing related products via get_related_products, showing frequently-bought-together recommendations, applying urgency triggers ("only 3 left in stock," "ends in 2 hours"), and recommending higher-tier or upsell SKUs. An owner who has just lost a pet and is searching for a cremation urn or a memorial portrait is not in a decision-optimization state. The agent's role is to surface the right product with minimal friction and then stop.

Required Agent-Behavior Flags in Grief Context

When productCategory: "pet-memorial" or buyerSegment: "grief" is present in any context signal, the following rules apply:

Implementation Path

The /agents page capability manifest (documented at that spoke) should include an agent_usage_policy field with a grief_aware: true flag for any storefront that carries memorial products. This signals to compliant agents that the grief-behavior ruleset applies for that storefront. A storefront selling both routine pet supplies and memorial products should implement segment detection — based on product category, search query sentiment, or explicit user disclosure — to switch between behavior modes dynamically.

The highest-churn moment in the pet-owner lifecycle is the first 30 days.

Decision fatigue is the failure mode the concierge pattern is designed to prevent. A new Lab puppy owner simultaneously faces: food brand selection (which formula, what life stage, puppy vs. all-life-stages?), crate sizing (current puppy size now, or adult size for life?), collar and harness (which size, which type?), ID tag, microchip enrollment, training treats, vet-visit scheduling, and parasite prevention. The decisions are interdependent — crate size depends on projected adult weight, food amount depends on current weight and age — and the owner typically lacks breed-specific knowledge to navigate them correctly.

The Five-Step Agent Assembly Pattern

1. Profile intake. Agent prompts for species, breed, and age. This populates the get_pet_profile call and seeds the assemble_starter_kit query with the three required parameters: species, breed, ageWeeks.
2. Breed-aware kit assembly. Using projected adult size, the agent assembles the kit with breed-specific reasoning surfaced. For a 10-week-old Labrador Retriever (estimated adult weight: 65–80 lbs), the crate recommendation is a 42-inch crate with a divider panel — not a 24-inch puppy crate. The food recommendation is a large-breed puppy formula, not a standard puppy formula (large-breed formulas have different calcium-to-phosphorus ratios to support controlled growth and reduce joint stress).
3. Subscription tagging. Items are classified as subscriptionRecommended: true (food, treats, flea/tick prevention) or oneTimePurchase: true (crate, collar, bed). The agent explains the distinction and its reasoning.
4. UCP contract setup. For subscription items, the agent sets up recurring-billing authorization under the owner's spending cap. For one-time items, single-purchase authorization. These are structured as separate contract entries — not a single mixed-type contract.
5. Vet schedule reminder. The agent surfaces the puppy vaccination schedule as a reminder set — not a purchase. This reinforces its concierge role without crossing into the healthcare and booking scope that is explicitly outside the pet-products commerce brief.

Why Independent Sellers Win This Segment

An indie Shopify seller with complete targetBreed, lifeStage, and adultWeightRange fields on every product will surface more accurately in agent-assembled starter kits than a large retailer with sparse category metadata. An artisanal treat seller whose products are tagged lifeStage: puppy, species: dog, breedSizeCategory: large, and ingredients: chicken-free will appear in a Lab-puppy starter kit for an allergen-aware owner in a way that Chewy's generic "puppy treats" category browse cannot match. Agents do not have brand loyalty. They have data loyalty.

Four asymmetries where indie sellers structurally outperform Chewy.

Chewy and Petco dominate the Routine Resupply segment on volume, logistics infrastructure, and loyalty program stickiness. Competing head-to-head on commodity pet food or mass-market flea prevention is the wrong fight. The agent-commerce wedge for independent sellers rests on four structural asymmetries.

The Shopify Autoship-Equivalent: Selling Plans API

For indie pet sellers on Shopify, the Selling Plans API is the direct implementation of an autoship-equivalent subscription without routing through Chewy or any major retailer. A sellingPlanGroup is attached to a product variant and encodes three policies: the delivery policy (deliveryFrequency — e.g., every 4 weeks), the pricing policy (fixed percentage discount vs. one-time price — e.g., 5% off), and the billing policy (billing on each delivery). Customer payment methods are stored via the Customer Payment Methods API, enabling recurring billing without the customer re-entering payment at each cycle. The subscription details in the product's JSON-LD (autoshipAvailable: true, autoshipCadence: "4 weeks", subscription price in a UnitPriceSpecification offer) allow agents to read the subscription parameters before initiating any API call — enabling pre-flight validation before the first subscription contract is created.

Eight ways pet-product agent integrations fail or cause harm.

1. Listing prescription products without prescriptionRequired: true in structured data

If a prescription medication SKU is missing prescriptionRequired: true in its additionalProperty block, an agent reading the schema has no signal to call check_prescription_required before initiating a purchase. The fix: add additionalProperty: { name: "prescriptionRequired", value: "true" } to every prescription item's JSON-LD. Audit using the check_prescription_required MCP tool call — if it returns false for an item known to require a prescription, the schema is wrong.

2. Treating Chewy's vendor EDI/API integration as a consumer agent integration path

Chewy's Rithum/DSCO integration is a supply-chain B2B layer for vendor brands fulfilling drop-ship orders. EDI 850 (purchase order), 856 (advance ship notice), and 810 (invoice) are the document types — these are order fulfillment paperwork between Chewy and its suppliers, not a consumer checkout API that an agent can query to search products, check prices, or place Autoship orders on behalf of a pet owner. Until Chewy publishes a public consumer API, agent-commerce storefronts must run on Shopify, WooCommerce, BigCommerce, or Etsy, not as Chewy integrations (re-verify before launch).

3. Setting the UCP spending cap to the one-time price rather than the subscription price

For subscription SKUs, the spending cap should reflect the post-discount autoship price, not the one-time retail price. A cap set at the one-time price wastes authorization headroom. More importantly, if the one-time price rises while the subscription price stays lower, the cap may unexpectedly reject the one-time-price variant on a future non-subscription purchase. Set caps on subscription pricing for subscription SKUs; set separate caps or single-purchase authorizations for one-time items.

4. Applying a generic "pet supplies" category tag instead of species-specific categories

An agent querying for species: cat should not have to parse a "pet supplies" collection to find cat-specific items. Item-level species tags are non-negotiable for correct concierge-pattern kit assembly. Tag products with species values at the product level, not only at the collection level. The concierge starter-kit tool calls will filter on species and return an empty or incorrect set if the field is absent or mis-categorized.

5. Ignoring life-stage distinctions when the product is formulated for a specific stage

Puppy, kitten, adult, and senior formulations carry different caloric density and nutrient profiles. A puppy formula is typically too calorie-dense for a senior dog; a senior formula may be inappropriate for a growing puppy. If a product is a puppy formula, tag it lifeStage: puppy. An agent that recommends a puppy food for a senior dog because the seller omitted the life-stage tag creates a health risk and a customer-service issue simultaneously.

6. Failing to flag grief-context products in the /agents page capability manifest

Any storefront selling memorial products (urns, portrait prints, memorial jewelry, cremation services) must include grief_aware: true in the agent_usage_policy field of the capability manifest (see /agentmall_spoke_agents_page). Without this flag, a compliant agent has no signal to switch to ethics-mode behavior. A storefront that triggers a get_related_products call after a grief-context memorial purchase is exhibiting correct default behavior — the grief_aware flag is what suppresses it.

7. Not accounting for the one-year VCPR supply limit on prescription autoship

Add a prescriptionExpiresDate field to the UCP subscription contract at Layer 4, calculated from the date of the original vet authorization. At the 11-month mark, the agent should surface a renewal reminder to the user rather than silently attempting to continue the autoship past the annual VCPR supply limit. An autoship that runs past this limit without vet re-authorization is a pharmacy compliance issue, not just an agent error.

8. Conflating Amazon Subscribe & Save discount tiers when writing structured data or MCP tool output

Amazon S&S delivers 5% on 1–4 subscriptions in a shipment and up to 15% on 5+ subscriptions in the same shipment (re-verify before launch). These are per-shipment thresholds, not per-product discounts. When surfacing Amazon S&S pricing to an agent or encoding it in structured data, do not represent the 15% as a guaranteed discount unless the owner already has four other active S&S subscriptions in the same delivery window. Misrepresenting this tier structure produces incorrect price comparisons at Layer 1 and incorrect spending-cap configurations at Layer 4.

Frequently asked questions about agent commerce for pet products.

Making a pet-products storefront agent-ready, in five steps.

Each step mirrors the HowTo JSON-LD at the top of this page word for word. Execute in order. The full sequence maps to approximately 30 days of build-and-verify work.

Step 1 — Audit and complete your structured data (Layer 1)

For every product, add additionalProperty entries for species, lifeStage, breedSizeCategory, allergens, prescriptionRequired, autoshipAvailable, and autoshipCadence. Create dual Offer entries (one-time + subscription) using UnitPriceSpecification with billingDuration for subscription pricing. Use the JSON-LD example in this document as your baseline template. Any product missing prescriptionRequired or species is not agent-safe.

Step 2 — Configure your subscription API (Layer 2)

If on Shopify, implement the Selling Plans API: create sellingPlanGroup on subscription-eligible variants with delivery, pricing, and billing policies. Store customer payment tokens via the Customer Payment Methods API. If on Etsy, document subscription limitations to your agent's MCP description (Etsy does not natively support subscriptions; any "subscribe" behavior requires an off-platform workflow). If on WooCommerce, use the WooCommerce Subscriptions plugin and expose subscriptions via the REST API endpoint /wp-json/wc/v3/subscriptions.

Step 3 — Build or configure your MCP tool layer (Layer 3)

Implement the minimum viable pet MCP tool set: search_products with species/life-stage/prescription filters, check_prescription_required, subscribe_autoship, modify_autoship, get_pet_profile. Add behaviorMode parameter support to search_products for grief-context filtering. Test each tool with representative inputs from all three buyer segments before enabling agent access. Reference /agentmall_spoke_mcp for the base MCP implementation guide.

Step 4 — Configure UCP contracts by segment (Layer 4)

For Routine Resupply products, set up recurring-billing UCP contracts with subscription pricing as the cap baseline. For prescription items, add a prescriptionExpiresDate field and an annual renewal gate. For memorial/grief-context products, configure one-time-only UCP contracts and suppress recurring-billing options. For starter-kit (New-Pet Concierge) workflows, create hybrid authorization: single-purchase for hardware items, recurring for consumables. Reference /agentmall_spoke_ucp for cap-and-authorize patterns.

Step 5 — Publish your /agents page and capability manifest

Declare your supported MCP tools, buyer segments, and any policy flags. If you carry memorial products, include grief_aware: true in agent_usage_policy. If you carry prescription products, include prescriptionGateRequired: true. Ensure the capability manifest is machine-readable (JSON-LD or structured JSON) and linked from your domain root at /.well-known/agent-commerce or your /agents page. Reference /agentmall_spoke_agents_page for the full manifest specification.

Next stops in the AgentMall guide.