canonical: https://jentic.com/apis/thequestionmark.org/thequestionmark

# Thequestionmark Questionmark API v1.2

[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.

## For AI 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.

## Scope

Does not handle payments, communications, or crm - use for e-commerce only.

## Capabilities

- 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

### 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.

Example prompt: 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.

Example prompt: 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.

Example prompt: 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

| 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 |

## Key resources

- **Brands** — Operations for brands
- **Categories.Json** — Operations for categories.json
- **Certificates** — Operations for certificates
- **Health_Groups** — Operations for health_groups
- **Nutrients** — Operations for nutrients

## 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:** 35 / 100
- **Maturity:** Non-Ready
- **Dimensions:**
  - Foundational Compliance: 54 / 100
  - Developer Experience & Jentic Compatibility: 57 / 100
  - AI-Readiness & Agent Experience: 24 / 100
  - Agent Usability: 94 / 100
  - Security: 15 / 100
  - AI Discoverability: 49 / 100
- **View full report:** https://jentic.com/apis/thequestionmark.org/thequestionmark/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 <openapi-url>
```

## Why Jentic

- **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 handling:** 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.
- **Discovery method:** 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

- **Shopify** — Alternative e commerce API
- **Stripe** — Alternative e commerce API

## FAQ

### 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.

### Can I limit what my agent is allowed to do with the Questionmark API?

Yes. Because you run Jentic One yourself, your own rules decide which Questionmark operations and credentials the agent may use, so you can grant only the calls it needs and withhold the rest. Since the API carries the product id in the URL path, such as GET `/products/{id}` and GET `/products/{id}/alternatives`, a rule can pin the agent to a single product and let it read that product and its alternatives and nothing else. Broad listing routes like GET /products or GET /brands, and lookups such as GET /certificates, stay off unless you add them.