Thequestionmark Questionmark API v1.2
✓ Official Vendor SpecE CommerceStorefrontapiKey35 EndpointsREST
For Agents
Programmatically list products (same as get but enables a client to hide parameters in the reques, list products. Covers 35 operations with apiKey authentication.
Use for: I need to products (same as get but enables a client to hide parameters in the reques, I want to products, Search for product by id, Find all product by barcode
Not supported: Does not handle payments, communications, or crm - use for e-commerce only.
[Questionmark](http://www.thequestionmark.org/) stands for your right to know the story behind the products you buy: where they come from and how they are produced. We believe that this type of transparency is crucial to developing sustainable supply chains and healthy products. Our mission is to make consumers more aware of the choices they have when buying a product and also to urge companies to. The API exposes 35 endpoints secured with apiKey authentication.
Install Jentic One Beta
Connect the Questionmark API v1.2 to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Questionmark API v1.2, 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.
1
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%2Fthequestionmark.org%2Fthequestionmark" | sh2
Step 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%2Fthequestionmark.org%2Fthequestionmark" | 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.
Capabilities
What an agent can do with Questionmark API v1.2 API.
list products (same as GET but enables a client to hide parameters in the reques
get product by id
Integrate Questionmark API v1.2 into automated workflows
Query and filter Questionmark API v1.2 records by parameters
Monitor Questionmark API v1.2 operational status and events
Use Cases
Patterns agents use Questionmark API v1.2 API for, with concrete tasks.
★ E-Commerce Operations
Use the Questionmark API v1.2 to perform e commerce operations programmatically. The API provides 35 endpoints covering core functionality including list products (same as get but enables a client to hide parameters in the reques, list products, get product by id.
Call POST /products to list products (same as get but enables a client to hide parameters in the reques
Automated Brands Management
Automate brands operations by combining multiple Questionmark API v1.2 endpoints. Agents can list products and then get product by id in a single workflow.
Call GET /products to list products, then verify the result
AI Agent Integration via Jentic
AI agents discover and call Questionmark API v1.2 endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle apiKey tokens manually.
Search Jentic for 'list products (same as get but enables a client to hide parameters in the reques', load the operation schema, and execute with Jentic-managed credentials
Key Endpoints
35 endpoints — [questionmark](http://www.
METHOD
PATH
DESCRIPTION
POST
/products
list products (same as GET but enables a client to hide parameters in the reques
GET
/products
list products
GET
/products/{id}
get product by id
GET
/products/{barcode}
get product by barcode
GET
/products/{id}/alternatives
list alternatives for a product
GET
/brands
list brands
GET
/brands/{id}
get brand by id
GET
/certificates
list certificates
POST
/products
list products (same as GET but enables a client to hide parameters in the reques
GET
/products
list products
GET
/products/{id}
get product by id
GET
/products/{barcode}
get product by barcode
GET
/products/{id}/alternatives
list alternatives for a product
GET
/brands
list brands
GET
/brands/{id}
get brand by id
GET
/certificates
list certificates
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Questionmark API by hand means passing its authentication_token as a query parameter on every request, paging product and brand listings yourself, and handling your own retries. Through Jentic you install once, import the Questionmark API from the API Directory, store the token once, and your agent calls it.
Permission scoping
The Questionmark API puts the product id in the URL path (/products/{id}/...), so a rule can pin your agent to one product: it can read that product and its alternatives and nothing else. You choose the operations it may call, so broad listing routes are not included unless you add them.
Credential isolation
Your Questionmark token 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 'look up a product by barcode' or 'find sustainable alternatives', and Jentic returns the matching Questionmark operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
Alternative
Stripe
Alternative e commerce API
Choose Stripe when you need a different approach to e commerce operations
FAQs
Specific to using Questionmark API v1.2 API through Jentic.
What authentication does the Questionmark API v1.2 use?
The Questionmark API v1.2 uses an API key passed in the `authentication_token` query. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.
Can I list products (same as get but enables a client to hide parameters in the reques with the Questionmark API v1.2?
Yes. Use the POST /products endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the Questionmark API v1.2?
Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.
How do I list products (same as get but enables a client to hide parameters in the reques through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'list products (same as get but enables a client to hide parameters in the reques'. Jentic returns the matching Questionmark API v1.2 operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the Questionmark API v1.2 have?
The Questionmark API v1.2 exposes 35 endpoints covering brands, categories.json, certificates operations.
GET STARTED