Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Place, list, and retrieve orders via the Zinc API (zinc.com). Use when the user wants to buy a product from an online retailer, check order status, list recent orders, or anything involving the Zinc e-commerce ordering API. Requires ZINC_API_KEY environment variable.
Place, list, and retrieve orders via the Zinc API (zinc.com). Use when the user wants to buy a product from an online retailer, check order status, list recent orders, or anything involving the Zinc e-commerce ordering API. Requires ZINC_API_KEY environment variable.
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Then review README.md for any prerequisites, environment setup, or post-install checks. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Then review README.md for any prerequisites, environment setup, or post-install checks. Summarize what changed and any follow-up checks I should run.
Place and manage orders on online retailers through the Zinc API (https://api.zinc.com).
ZINC_API_KEY env var must be set. Get one from https://app.zinc.com.
All requests use Bearer token auth: Authorization: Bearer $ZINC_API_KEY
Place a new order. Orders process asynchronously. Required fields: products โ array of { url, quantity?, variant? } objects url: direct product page URL on a supported retailer quantity: integer (default 1) variant: array of { label, value } for size/color/etc. shipping_address โ object with first_name, last_name, address_line1, address_line2, city, state (2-letter), postal_code, phone_number, country (ISO alpha-2, e.g. "US") max_price โ integer, maximum price in cents Optional fields: idempotency_key โ string (max 36 chars) to prevent duplicates retailer_credentials_id โ short ID like zn_acct_XXXXXXXX metadata โ arbitrary key-value object po_number โ purchase order number string Response: order object with id (UUID), status, items, shipping_address, created_at, tracking_numbers, etc. Order statuses: pending โ in_progress โ order_placed | order_failed | cancelled
Returns { orders: [...] } array of order objects.
Retrieve a single order by UUID.
curl -X POST https://api.zinc.com/orders \ -H "Authorization: Bearer $ZINC_API_KEY" \ -H "Content-Type: application/json" \ -d '{ "products": [{ "url": "https://example.com/product", "quantity": 1 }], "max_price": 5000, "shipping_address": { "first_name": "Jane", "last_name": "Doe", "address_line1": "123 Main St", "city": "San Francisco", "state": "CA", "postal_code": "94105", "phone_number": "5551234567", "country": "US" } }'
See references/errors.md for the full error code reference. Key points: HTTP errors return { code, message, details } Order processing failures appear in webhook/order response as error_type Common issues: max_price_exceeded, product_out_of_stock, invalid_shipping_address
Orders process asynchronously and typically take 5โ10 minutes. After placing an order: Schedule a cron job to check the order status ~7 minutes after creation. Use GET /orders/{id} to poll. Report the result back to the user in the same channel. If still pending/in_progress, schedule another check in 5 minutes. Terminal statuses: order_placed, order_failed, cancelled โ stop polling. Non-terminal: pending, in_progress โ schedule another check in 3โ5 minutes. Example cron job (isolated, announce back to the channel): { "name": "zinc-order-check-<short_id>", "schedule": { "kind": "at", "at": "<ISO-8601 ~7min from now>" }, "payload": { "kind": "agentTurn", "message": "Check Zinc order <order_id> via GET https://api.zinc.com/orders/<order_id>" }, "sessionTarget": "isolated", "delivery": { "mode": "announce", "channel": "<channel>", "to": "<channel_id>" } }
Always confirm with the user before placing an order (POST /orders). This spends real money. Reading orders (GET) is always safe. Validate that max_price is reasonable before submitting.
Code helpers, APIs, CLIs, browser automation, testing, and developer operations.
Largest current source with strong distribution and engagement signals.