canonical: https://jentic.com/apis/collectpure.com/collectpure # Collectpure Pure Public API The Pure Public API serves data and trading operations for the Pure marketplace. It searches products and returns enriched product details, analytics, activity, and live or historical order books, plus catalog metadata, categories, materials, and manufacturers. It reports the marketplace spot price, recommended shipping date, and platform-wide stats, and it lets your organization create, update, and deactivate listings and offers, read purchase and sale orders, and track inventory with statistics. Organization settings can also be read and updated. ## For AI agents Search Pure marketplace products and read enriched details, order books, and the spot price, then create and manage your organization's listings, offers, orders, and inventory. Authenticated with an API key in the x-api-key header. ## Scope Does not process payments, ship orders, or verify user identity. Use for Pure marketplace product data, listings, offers, orders, and inventory only. ## Capabilities - Search products and read enriched product details and attributes - Read a product's live order book, analytics, and activity - Report the marketplace spot price and platform-wide stats - Create, update, and deactivate your organization's listings - Create, update, and deactivate your organization's offers - List purchase and sale orders and track inventory with statistics - Read and update organization settings ## Use cases ### Agent-Managed Marketplace Trading An AI agent reads a product's order book and the marketplace spot price through Jentic, then creates or updates a listing or offer for your organization. Every call carries the API key in the x-api-key header, scoping writes to your organization, and a rule can keep the agent on reads while listing and offer changes stay with a human. The agent finds each operation by intent and calls it directly. Example prompt: Read the order book for a product, then create a listing priced against the current spot price. ### Product Research and Pricing A tool searches the Pure catalog, reads enriched product details, attributes, and materials, and pulls analytics and activity to decide what to buy or sell. The spot price and recommended shipping date endpoints add pricing and timing context. Teams use this to research the market before placing listings or offers. Example prompt: Search for a product, read its enriched details, and compare its order book against the spot price. ### Inventory and Order Management An operations workflow lists an organization's purchase and sale orders, tracks inventory with statistics, and reviews listing and offer stats. Pure returns these scoped to the organization behind the API key. Teams use this to reconcile what they hold against what they have listed and sold. Example prompt: List the organization's open sale orders and reconcile them against current inventory. ## Key endpoints | Method | Path | Description | | --- | --- | --- | | GET | `/products/v1/search` | Search products | | GET | `/products/v3/{id}` | Get enriched product details | | GET | `/products/v1/catalog` | Get product catalog metadata | | GET | `/marketplace/get-spot-price/v1` | Get the marketplace spot price | | POST | `/listings/create-listing/v1` | Create a listing | | POST | `/offers/create-offer/v1` | Create an offer | | GET | `/orders/get-sale-orders/v1` | List sale orders | | GET | `/inventory/get-inventory/v1` | List your inventory | ## Key resources - **Products** — Search products and read enriched details, attributes, materials, analytics, activity, and order books - **Marketplace** — Spot price, recommended shipping date, and platform-wide marketplace stats - **Listings** — Create, update, deactivate, and read your organization's listings and their stats - **Offers** — Create, update, deactivate, and read your organization's offers and their stats - **Orders and inventory** — List purchase and sale orders and track inventory with statistics - **Organization** — Read and update organization settings ## AI readiness This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use. - **Score:** 38 / 100 - **Maturity:** Non-Ready - **Dimensions:** - Foundational Compliance: 99 / 100 - Developer Experience & Jentic Compatibility: 56 / 100 - AI-Readiness & Agent Experience: 15 / 100 - Agent Usability: 94 / 100 - Security: 50 / 100 - AI Discoverability: 76 / 100 - **View full report:** https://jentic.com/apis/collectpure.com/collectpure/scorecard - **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/ - **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview ### Score it yourself Every API in the directory is allowlisted, so you can re-score it with no key required. - **Score your own API:** https://jentic.com/scorecard.md - **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md ```sh npx @jentic/api-scorecard-cli score ``` ## Why Jentic - **Setup:** Wiring the Pure Public API by hand means sending the API key in the `x-api-key` header and keeping writes scoped to your organization across products, listings, offers, orders, and inventory. Through Jentic you install once, import the Pure Public API from the API Directory, store the key once, and your agent calls it. - **Permission scoping:** Pure carries listing and offer ids in the request body rather than the URL path, so rules bound which operations your agent may call, not which item. You can allow the read operations like product search, order books, and the spot price while leaving creating or deactivating listings and offers out. - **Credential handling:** Your Pure API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'search marketplace products' or 'get the spot price', and Jentic returns the matching Pure operation with its input schema so the agent calls the right endpoint without reading the reference docs. ## Related APIs - **eBay** — A large online marketplace for listing and selling items. - **Shopify** — A commerce platform for running your own online store. - **Polygon** — Financial market data for real-time and historical prices. ## FAQ ### What authentication does the Pure Public API use? The Pure Public API authenticates with an API key sent in the `x-api-key` header, per its OpenAPI spec, and write operations are scoped to the organization that owns the key. Through Jentic the key is stored encrypted by your own Jentic One instance and injected only at call time. ### Can I create listings and read order books with the Pure Public API? Yes. You can search products, read enriched details and live order books, and report the marketplace spot price, then create, update, or deactivate your organization's listings and offers. You can also list purchase and sale orders and track inventory with statistics. ### What are the rate limits for the Pure Public API? The OpenAPI spec does not specify rate limits for the Pure Public API. Check the vendor's documentation at https://docs.collectpure.com for current limits before pointing an agent at it. ### Can I limit what my agent is allowed to do with the Pure Public API? Yes. Write a rule that allows only the read operations, such as product search, order books, and the spot price, so the agent can research the market but cannot create or deactivate listings and offers. The listing and offer ids travel in the request body, so the rule bounds which operations run, not which item, and every call is logged. ### Is there a Pure Public API MCP server? You don't need an MCP server to give your agent the Pure Public API. Jentic connects it directly from the API Directory: import it, store your API key once, and your agent calls the product, listing, and order operations. You skip loading another server's tool definitions into the agent's context. ### How do I search the marketplace through Jentic? Add the Pure Public API from the Jentic API Directory and store your API key once. Your agent then searches by intent such as 'search marketplace products' and Jentic returns the matching operation with its input schema, so it can read product details and the spot price. To run it on your own infrastructure, install Jentic One from its GitHub repo.