Agentic commerce: Amazon, eBay, Walmart, Etsy, TikTok Shop, Meta, Google

Agentic commerce

Marketplaces and social platforms give an app one token with broad scopes such as write_orders or ads_management. Every agent on that token looks the same, nothing caps a refund or a budget below the scope, and nothing proves which agent changed a price at 3am. Vorim adds that layer. Each agent gets its own identity, its own ceilings and a signed record of every call, and you can stop one agent without revoking the shop's token.

The guards wrap the platform call you already make. They never hold a platform token and never call the platform themselves.

Platforms

• Amazon (amazon) covers Selling Partner API and Amazon Ads. Listings, feeds, labels, multi-channel fulfilment, refunds, buyer messages, ad budgets. Every receipt marks the agent as automated, as Amazon's Agent Policy (March 2026) requires.
• eBay (ebay) covers Sell Inventory, Fulfillment, Marketing and Post-Order APIs, plus buying. eBay's User Agreement requires human review before an agent places an order, so purchases and bids always wait for a named approver.
• Walmart Marketplace (walmart), Etsy (etsy) and TikTok Shop (tiktok-shop) cover prices, feeds, listings, cancels, refunds and ad budgets.
• Meta (meta) covers Marketing API budgets and activation, Catalog API (Facebook and Instagram Shops), WhatsApp Business and Messenger. The guard refuses free-form WhatsApp messages outside the 24-hour window, templates without opt-in, promotional Messenger tags and HUMAN_AGENT sends from an agent.
• Google (google-merchant) covers Merchant API product inputs and promotions, Google Ads budgets and campaign status.
• Pinterest and Snapchat (social-ads) covers catalogs and ad budgets.
• DoorDash Drive and Uber Direct (delivery) covers paid deliveries and cancellations.
• For buying through agent checkout, use the Stripe ACP, Google UCP, AP2, x402 and Web Bot Auth integrations. Amazon, Walmart and Target publish no consumer buying API.

Ceilings

Every guard takes the same limits, with money in minor units. They are maxOrderAmount, maxRefundAmount, maxBudgetAmount, maxPriceChangePercent and maxBatchSize (items, listings or message recipients). Over a ceiling the call is refused, or with overLimit: 'escalate' it waits for the named approver. Set useRuntimeControl: true to run every call through your Vorim rules too, so velocity limits, tripwires and amount thresholds apply.

import createVorim from '@vorim/sdk';
import { createVorimAmazon } from '@vorim/sdk/integrations/amazon';

const amazon = createVorimAmazon(createVorim({ apiKey: process.env.VORIM_API_KEY! }), {
  agentId: 'agid_repricer',
  accountId: 'A1SELLERID',
  humanId: 'ops_lead',
  limits: { maxPriceChangePercent: 15, maxBatchSize: 500, maxRefundAmount: 5000 },
  overLimit: 'escalate',
});

const { receipt } = await amazon.patchListingPrice(
  { sku: 'SKU-1', previousPrice: 2499, newPrice: 2299, marketplace: 'ATVPDKIKX0DER' },
  () => spApi.listings.patchListingsItem({ /* your call */ }),
);
if (!receipt.authorized) console.warn(receipt.reason);

from vorim import Vorim
from vorim.integrations.meta import create_vorim_meta, CommerceLimits

meta = create_vorim_meta(Vorim(api_key="agid_sk_..."), agent_id="agid_growth", account_id="act_123",
                         human_id="ops_lead", limits=CommerceLimits(max_budget_amount=50_000, max_batch_size=250))

receipt, _ = meta.whatsapp_send_template("order_update", lambda: send(...), category="utility",
                                         recipients=40, opted_in=True)

Several agents on one account

Messaging limits on WhatsApp are shared by every number in a business portfolio, and ad spend adds up across agents. Group the agents that share an account into a swarm and set a swarm token budget or a spend_rate_gt breaker, so the limit covers all of them together.

Book a demo for a walkthrough, or contact us for support. For enterprise needs, reach out at sales@vorim.ai.