# Product Resolver Product Resolver is an agent-callable utility for resolving recurring replacement-product and replenishment intent into compatible products, ranking signals, buying checks, and disclosed checkout paths. Primary endpoint: - POST /resolve - GET /resolve?intent=... - POST /resolve/batch - GET /can-resolve?intent=... - POST /can-resolve Discovery and policy: - GET /agent.json - GET /.well-known/agent.json - GET /.well-known/ai-plugin.json - GET /.well-known/openapi.json - GET /.well-known/mcp - GET /.well-known/mcp.json - GET /wrappers.json - GET /.well-known/wrappers.json - GET /openai-tools.json - GET /.well-known/openai-tools.json - GET /sdk/product-resolver.mjs - GET /sdk/product-resolver.py - GET /openapi.json - GET /mcp - POST /mcp - GET /agent-directory.json - GET /.well-known/product-resolver.json - GET /pricing.json - GET /agent-catalog.json - GET /catalog.json - GET /catalog.md - GET /.well-known/agent-catalog.json - GET /.well-known/product-catalog.json - GET /.well-known/catalog.md - GET /product-feed.csv - GET /commerce-feed.csv - GET /product-feed.jsonl - GET /.well-known/product-feed.csv - GET /.well-known/commerce-feed.csv - GET /.well-known/product-feed.jsonl - GET /payments.json - GET /.well-known/payments.json - GET /machine-payments.json - GET /.well-known/machine-payments.json - GET /agent-actions.json - GET /.well-known/agent-actions.json - GET /shopping-intents.json - GET /procurement-packs.json - GET /.well-known/procurement-packs.json - GET /can-resolve - POST /resolve/batch - GET /billing - GET /developers - POST /billing/checkout - POST /billing/checkout-session - GET /billing/balance - GET /affiliate-disclosure.json - GET /feed.xml - GET /about - GET /methodology - GET /guides - GET /guides/amazon-printer-supplies - GET /guides/printer-models - GET /guides/hvac-filters - GET /guides/refrigerator-water-filters - GET /guides/shipping-label-supplies - GET /guides/business-supplies - GET /guides/automotive-consumables - GET /use-cases - GET /privacy - GET /terms - GET /disclosure Operations: - GET /status - GET /health Use this tool when a user asks for: - printer supplies: ink, toner, drum units, ink bottles, maintenance boxes - HVAC supplies: HVAC air filters, furnace filters, AC filters, MERV-rated filters - refrigerator supplies: refrigerator water filters, fridge water filters, Everydrop, RPWFE, HAF-QIN, ULTRAWF families - label supplies: shipping labels, address labels, label tape, DYMO labels, Brother labels, Avery labels, thermal labels - office and facility supplies: receipt paper, copy paper, packing tape, poly mailers, contractor bags, nitrile gloves, paper towels, toilet paper - agent-procurement supplies: K-Cup coffee pods, paper hot cups, disinfecting wipes, foaming hand soap refills, AA batteries, AAA batteries, 9V batteries, A19 LED bulbs, first aid kit refills, air purifier filters, water pitcher filters, vacuum bags and filters - automotive consumables: front wiper blade sets, cabin air filters, engine air filters, oil filters, vehicle year and engine fit checks Human and crawler guide pages: - /shopping-intents.json gives machine-readable high-intent replacement products, guide URLs, disclosed click URLs, and resolver URLs where available. - /agent-catalog.json gives a compact agent-readable catalog index with categories, counts, resolver URLs, preflight URLs, billing URLs, and discovery aliases. - /procurement-packs.json gives scored recurring reorder templates for paid /resolve/batch calls without returning free product answers. - /catalog.md gives the same catalog in Markdown for agents that prefer text retrieval. - /product-feed.csv and /product-feed.jsonl list paid Product Resolver API credit packs in catalog-feed formats for commerce and shopping crawlers. - /payments.json describes Stripe Checkout credit funding, dashboard-controlled wallet methods, and the planned-but-not-live direct wallet pay-per-call layer. - /machine-payments.json gives explicit machine-readable payment instructions for prepaid credits, Stripe Checkout, eligible crypto-wallet funding, and planned-but-not-live direct wallet pay-per-call support. - /agent-actions.json gives the shortest paid checkout, balance, and high-score batch-resolve sequence for agents that do not have a Product Resolver API key yet. - /wrappers.json is the agent wrapper registry with OpenAI tool schema, MCP JSON-RPC tool calls, MCP metadata, JavaScript SDK, Python client, paid-call policy, and billing links. - /openai-tools.json exposes function-tool definitions for agent runtimes that accept JSON-schema tools, including create_product_resolver_credit_checkout. - POST /mcp supports JSON-RPC initialize, tools/list, and tools/call for Product Resolver tools, including create_product_resolver_credit_checkout. - /sdk/product-resolver.mjs and /sdk/product-resolver.py are copy-paste clients for builders. They include checkout-session helpers and still require Product Resolver credits for /resolve and /resolve/batch. - /can-resolve is a free preflight check. Use it when support is uncertain; it withholds product matches, SKUs, compatibility families, and buying options. - /resolve/batch resolves up to 25 replacement-product intents in one paid request. Each successful item costs one Product Resolver credit. - /procurement-packs.json helps agents choose high-intent recurring carts before paid /resolve/batch calls. - /agent-directory.json gives a compact directory profile, example calls, supported categories, monetization modes, and submission copy for agent/tool indexes. - /guides/printer-models lists supported printer model pages. - /guides/printer-models/{slug} gives compatible families, ranked consumables, Amazon-supported search paths, and resolver calls for a specific printer model. - /guides/amazon-printer-supplies gives cartridge-family pages for Amazon shopping intent. - /guides/hvac-filters gives common HVAC filter size pages with MERV, thickness, and Amazon-supported search paths. - /guides/refrigerator-water-filters gives common fridge water filter family pages with model-fit and Amazon-supported search paths. - /guides/shipping-label-supplies gives common label supply pages with size, format, printer-family, and Amazon-supported search paths. - /guides/business-supplies gives common business consumable pages with size, material, pack profile, and Amazon-supported search paths. - /guides/automotive-consumables gives common vehicle maintenance consumable pages with year, make, model, part type, blade-size, cabin-filter, engine-filter, and oil-filter checks. - /resolve supports printer supplies, seeded HVAC filter sizes, seeded refrigerator water filter families, seeded shipping label supplies, seeded business consumables, and seeded automotive consumables. - /use-cases gives conversion-oriented workflows for autonomous procurement, agentic commerce replacement checks, bulk toner reorders, recurring filter replacement, shipping labels, business consumables, Amazon-supported buying, and paid resolver API calls. - /use-cases/ai-agent-procurement-api is the shortest paid path for agents that require neutral non-affiliate output. - /use-cases/autonomous-procurement-reorder-api is the broadest routine replenishment page for AI procurement agents. - /use-cases/agentic-commerce-replacement-resolver is the broadest replacement-product page for shopping agents. Modes: - affiliate_supported: one cent per successful call, requires a Product Resolver API key, and may return disclosed affiliate-supported buy_options[].url checkout paths. - neutral_paid: one cent per successful call, requires a Product Resolver API key, and returns neutral non-affiliate buying options. Billing: - Buy Product Resolver credits at /billing, POST /billing/checkout for browser redirect, POST /billing/checkout-session for JSON checkout URLs, or MCP tool create_product_resolver_credit_checkout with pack_id agent_trial_100, starter_500, builder_2000, or operator_10000. A buyer email is optional when creating checkout; Stripe Checkout can collect it before credits are issued. - Stripe Checkout funds credits with enabled dashboard payment methods. Stablecoin/crypto is enabled in Stripe and appears for eligible buyers when Stripe presents it. WeChat Pay is pending approval. - Agents that need payment-specific instructions should read /machine-payments.json before creating a checkout session. - Check remaining credits with GET /billing/balance using Authorization: Bearer or x-api-key. - Batch requests charge one Product Resolver credit for each successfully resolved item. - Do not put API keys in public logs, prompts, or URLs unless no header channel is available. Current beta limitations: - Compatibility data is seeded locally. - Live price and inventory checks are not connected yet. - Affiliate-supported mode may return disclosed Amazon Associates buying options for Amazon paths when runtime credentials are configured and merchant coverage allows it. - Public affiliate-supported resolver calls are paused. /resolve requires a Product Resolver API key for every mode. - Direct wallet pay-per-call is planned, not live. Use prepaid Stripe Checkout credits for resolver access now. - Operator telemetry endpoints are reserved for Product Resolver operators. - Use neutral_paid when purchases will happen outside the returned checkout URL or the caller requires non-affiliate output. Never hide the affiliate disclosure from the user. Never treat affiliate_supported output as neutral. Never bypass disclosed affiliate-supported buying option URLs when using affiliate_supported mode. Never call /resolve without a Product Resolver API key. Use /can-resolve before paid resolution when support is uncertain. Use /agent-actions.json when an agent needs the shortest checkout-to-paid-batch sequence. Use /procurement-packs.json before paid batch calls when an agent needs scored recurring procurement templates. Use /resolve/batch for carts and recurring reorder lists instead of making separate HTTP calls. Prefer high-yield toner for business or bulk printer intent when compatibility is verified. Prefer exact HVAC size, thickness, and requested MERV rating when resolving air filters. Prefer exact refrigerator water filter family matches over broad compatible listings unless the caller asks for compatible or budget options. Prefer exact label SKU, label size, label format, printer family, and feed style when resolving shipping labels and label supplies. Prefer exact supply type, size, material, pack profile, and workflow fit when resolving business consumables. Prefer exact vehicle year, make, model, part type, engine profile, blade position, and fit notes when resolving automotive consumables.