Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Pure Public API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fcollectpure.com%2Fcollectpure" | shStep 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fcollectpure.com%2Fcollectpure" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
What an agent can do with Pure Public API.
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
GET STARTED
List purchase and sale orders and track inventory with statistics
Read and update organization settings
Patterns agents use Pure Public API for, with concrete tasks.
★ 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.
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.
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.
List the organization's open sale orders and reconcile them against current inventory.
42 endpoints — the pure public api serves data and trading operations for the pure marketplace.
METHOD
PATH
DESCRIPTION
/products/v1/search
Search products
/products/v3/{id}
Get enriched product details
/products/v1/catalog
Get product catalog metadata
/marketplace/get-spot-price/v1
Get the marketplace spot price
/listings/create-listing/v1
Create a listing
/offers/create-offer/v1
Create an offer
/orders/get-sale-orders/v1
List sale orders
/inventory/get-inventory/v1
List your inventory
/products/v1/search
Search products
/products/v3/{id}
Get enriched product details
/products/v1/catalog
Get product catalog metadata
/marketplace/get-spot-price/v1
Get the marketplace spot price
/listings/create-listing/v1
Create a listing
/offers/create-offer/v1
Create an offer
/orders/get-sale-orders/v1
List sale orders
/inventory/get-inventory/v1
List your inventory
What agents get from Jentic-routed access to this vendor.
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 isolation
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.
Intent-based discovery
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.
Alternatives and complements available in the Jentic catalogue.
Specific to using Pure Public API through Jentic.
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.
For 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.
Use for: Search the marketplace for a product, Get the live order book for a product, Check the current spot price, Create a listing for an item I want to sell
Not supported: Does not process payments, ship orders, or verify user identity. Use for Pure marketplace product data, listings, offers, orders, and inventory only.
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.
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.
Base layer of spec validity and structural soundness.
Aggregated quality score from linter diagnostics, weighted by severity.
Percentage of `$ref` references that resolve successfully.
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
Structural correctness score based on schema issues using logarithmic dampening.
Clarity, completeness, and ingestion readiness for developers and tooling.
How richly the API is illustrated with examples.
Percentage of examples that conform to their schemas.
Percentage of operations with complete response definitions (success, client error, server error).
Health of API ingestion, bundling, and resolution within Jentic pipelines.
Semantic breadth, depth, and agent comprehension for AI systems.
Coverage of descriptions across API elements.
Coverage of RFC 9457 Problem Details for error responses.
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
Coverage of summaries across operations/tags/info.
Functional utility, complexity comfort, and AI orchestration readiness.
Agent comfort level based on API operational and structural complexity.
Trust, risk posture, and security compliance.
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
Findability, semantic richness, and reasoning readiness.
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>