Zinc connects product search, retailer orders, shipment tracking and returns for developers, procurement teams and shopping agents.
Used this tool? Rate it
Used this tool? Rate it
Zinc provides an e-commerce API for finding products, placing retailer orders, tracking shipments and handling returns. Its users include developers, procurement teams and shopping agents. Retailers still control product availability, shipping and after-sale rights.
Developers call the API, operations teams can upload order batches, and a hosted connector presents shopping choices inside a compatible assistant. Account, payment and geographic requirements differ across those paths.
Cross-retailer search returns structured results from stores including Amazon, Walmart, Target, Etsy and Shopify storefronts. A retailer-specific search is also available. Product data may include images, current prices and availability. Product records can include descriptions, specifications and variants. The available fields depend on the retailer.
Product records describe items; offers present price, availability and sellers. An offer response can include condition, seller reputation, handling time and shipping options. The lowest listed price and the fastest shipment are therefore separate considerations.
Retailer-specific product search can return a validation error when a retailer is orderable but lacks product data through that route. Offer coverage also varies, so test discovery, details and offers separately for each retailer.
An order sends product and destination information to Zinc for validation, queuing and retailer checkout. Zinc can buy on its managed accounts or a customer can select an account it owns. In the latter case, the retailer charges its saved payment method and Zinc charges the API fee to the wallet. The account must match the product's store.
Orders using the same retailer account run sequentially because an account has one cart. Verification challenges reach the account owner and may stall orders until resolved. Account-level throughput and credential maintenance matter to a bulk workflow.
The order API is strict by default. Documented fulfillment preferences can selectively relax unavailable items or quantity caps in a supported best-effort mode. Omitted preferences stay strict. The maximum price remains a boundary even when fulfillment is relaxed.
A retailer gift option can suppress prices on the packing slip. The business FAQ describes a gift message of up to 240 characters and failure if the gift option cannot be confirmed. Order documentation also describes a best-effort gift mode, so check which mode is actually sent.
Zinc describes API and webhook events for placement, shipment and delivery. Tracking can include a carrier and tracking number; separately shipped items may have multiple numbers. Tracking may not be available immediately after submission.
Return eligibility, timing, condition and deductions follow retailer policies. The FAQ describes creating returns through the API, receiving return events and obtaining a label on the return object. It says the dashboard did not offer return initiation at review time.
Sandbox scenarios test application behavior without proving that a live retailer will accept a particular order, cancellation or return. A real checkout was not tested for this review.
Teams can submit a procurement batch through the API or upload a file in the dashboard. Zinc describes validating rows before purchase. Each batch returns a results file with the outcome of each row for reconciliation. The submitter still needs accurate addresses, authorization and funds.
An organization may use its own retailer accounts to retain negotiated pricing and purchase history. Zinc's managed-account route avoids maintaining those logins but is a different purchase path. Payment ownership and account verification should be considered before selecting it.
A shopping application can use product and offer data to help a user choose, send an order after confirmation and surface shipment events. The hosted connector describes interactive search, review and payment cards, followed by an order ID and tracking link.
For headless agents, Zinc describes an account-free order request that returns an HTTP 402 payment challenge. Its FAQ also describes a prefunded-wallet route. A payment response does not itself prove that a retailer accepted or shipped the purchase.
The API and sandbox suit teams able to manage credentials, webhook delivery and order state. TypeScript and Python clients are advertised. The application owner still designs its interface, obtains permissions and manages its business rules.
Zinc's terms make customers building on the service or buying for others responsible for their own product and the people involved, including required notices and consent. An API client does not determine what an application is entitled to collect or submit.
Operations teams can upload an order file and use per-row outcomes for reconciliation. Teams relying on their own retailer accounts need to account for stored payment methods, verification challenges and sequential orders on the same account.
Zinc warns that automating an end customer's retailer account can risk closure and says it cannot appeal for that owner. This differs from using an account the purchasing organization owns and is authorized to connect.
The MCP connector describes a consumer shopping flow with search, a review card and hosted card payment. A Zinc account is optional for one purchase but needed to see history across conversations. It is a distinct entry point from a wallet-funded API integration.
The connector documents shipping to US addresses and requires a chat client that can render interactive payment cards. Text-only clients cannot show the payment button. The general terms require users to be at least 18. The retailer’s age and legality checks also apply.
Zinc exposes an API and dashboard and advertises TypeScript and Python SDKs. The dashboard shows operational information, while the FAQ says return initiation currently requires the API. Teams without engineering support should check each step they need.
The MCP connector describes a review card showing the estimated item price, tax, shipping and Zinc fee before a human proceeds to hosted payment. Zinc says the actual total plus the $1 fee is captured and the unused card hold is released after placement.
The consumer connector and developer agent API have different account and payment arrangements. The former describes a card flow without a required account for one order; the API also supports wallet funding, managed accounts and payment challenges.
Zinc describes its retailer-list endpoint as free and available without an API key. It distinguishes retailers available on managed accounts from possible reach using a customer's own retailer account. Individual products and purchases remain subject to retailer acceptance.
The geographic FAQ is internally unclear: it says customers can request setup for their own accounts outside the US, while its answer for Zinc's accounts first says no and then lists the US, Germany and Italy. Confirm the intended retailer and destination with Zinc.
The public price page lists $1 per successful order plus the item cost and says failed orders are not billed that fee. Its FAQ prices product data separately at $0.01 per call on agent endpoints. Tax and shipping are additional purchase costs.
The price page lists $0.25 for tracking links and emails and $0.10 for each additional item over ten. It does not reconcile the latter with the FAQ's ten-item order limit. The order reference counts product-array entries rather than units; clarify the extra-item charge for the intended flow.
| Charge or condition | Public description | Decision to check |
|---|---|---|
| Successful order | $1 plus the item cost; failed orders are not charged the successful-order fee | Add applicable tax and shipping |
| Product data | $0.01 per call on the agent endpoints | Check which calls are metered in the integration |
| Tracking links and emails | Additional $0.25 | Confirm that customer-facing notifications are needed |
| More than ten items | Additional $0.10 per item, as worded on the pricing page | Clarify the order-path and item definition |
| Volume arrangement | Sales conversation starting at 1,000 orders per month | Obtain applicable negotiated terms |
Zinc describes a default path in which it buys on the customer's behalf. The customer's prefunded Zinc Wallet covers item cost, tax, shipping and the $1 fee on that path. Insufficient funds cause rejection instead of partial placement. Wallet documentation says the balance must cover the maximum price plus the fee at order time.
The funding FAQ says the entered amount reaches the wallet and processing fees are added. It lists card funding at 2.9% plus $0.30, ACH at 0.8% capped at $5, and wire at $15. Self-service top-ups range from $15 to $100,000; test and production wallets are separate.
When a customer selects its own retailer account, its saved retailer payment method pays for the merchandise and the Zinc wallet pays the API fee. The two balances are distinct when forecasting funding needs.
Zinc advertises volume pricing starting at 1,000 orders per month through sales. It also advertises custom terms for high call or order volumes. The public page does not provide a complete rate schedule, so confirm eligibility and the expected mix of calls.
Apify describes Actors as serverless programs for tasks such as web scraping, browser automation and data processing, runnable through an API, CLI or schedule. It is worth examining for a data-extraction need; checkout and post-order responsibilities need separate verification.
Shopify's Storefront API documents creating a cart for a buyer session and returning a checkout URL. It is relevant to a Shopify storefront. Compare that scope with an integration intended to place purchases across separate retailers; this is not an independently tested head-to-head comparison.
The order reference allows at most ten entries in the products array; one entry with a higher quantity still counts as one. The FAQ separately says ten items, and the pricing card mentions an extra-item charge above ten. The pages do not reconcile the terms.
The terms do not guarantee completed purchases, timely delivery or retailer acceptance, and say product information can be incomplete or inaccurate. An accepted request is not proof of a completed purchase.
A queued order may be cancelled with a wallet refund, but Zinc says it does not cancel at the retailer after placement. Retailer rules determine return eligibility and deductions; Zinc cannot require the retailer to accept a return.
The MCP connector documentation lists refused categories including weapons, tobacco and nicotine, prescription medication, adult products, gambling, covert surveillance and counterfeits. It describes rejecting matching searches or purchase preparation and says retailer age and legality checks still apply. This describes the connector pathway.
General terms prohibit illegal, unsafe or restricted purchases, unauthorized payment use, harmful retailer-term violations and transactions involving sanctioned parties or places. Customers remain responsible for order details and approval when software or an agent acts through their credentials.
The terms let Zinc refuse, cancel or limit requests, including suspected fraud, pricing errors or restricted products. A store's presence in discovery is not a promise that every item or destination will be accepted.
Zinc's privacy notice covers its site, API, dashboard, MCP server and related services. For account holders and visitors it describes Zinc as controller. For recipient data submitted by customers it says it processes data on their behalf and directs requests to the customer where possible.
The notice lists account details, product URLs, quantities, price limits, recipient contact and shipping data, gift messages and connected retailer sign-in details. Automatically collected data includes API request and response logs, timestamps, webhook deliveries, OAuth scopes and MCP client identifiers.
Zinc says authorized staff or contractors may review order details to complete, support or investigate orders. It lists hosting, databases, AI model providers and communications among service providers, which may use data only to provide services to Zinc. Connected apps receive tool results under their own privacy policies.
For improvement, Zinc describes debugging, reliability measurement and testing automation against past orders with masking or de-identification where practical. It does not say every item is always de-identified. Users retain ownership but permit use, storage and sharing to provide, secure, support and improve the service.
The notice says Zinc does not sell personal data or share it for cross-context behavioral advertising. Depending on location, it describes access, correction, deletion, portability and objection or restriction rights. Data may be retained after account closure for business or legal needs, while de-identified information may be kept indefinitely.
Yes. The sandbox isolates test data and simulates stock, price and shipping failures without real purchases. It does not prove that a retailer will accept a particular live order.
The public price page separates successful-order and product-data charges and lists $0.01 per call on agent endpoints. Check the precise endpoint, payment mode, retries and any negotiated volume terms.
Zinc says queued requests can be cancelled with a wallet refund, but it does not cancel at the retailer after placement. Return and credit outcomes depend on the retailer's policy and deductions.
