Limits and terms
This page summarises what the official developer page and the API terms say. If anything here differs from them, they win.
Limits
- There is no API key and no published request quota.
- Please cache answers, and keep your request rate reasonable.
- The service is shared. Do not overload it with automated requests or work around its limits.
A good default: store each answer for as long as your product can tolerate, and spread bulk jobs over time rather than sending bursts. Responses are served with a one hour cache header, so a client-side cache of that length costs you nothing.
What you may do
- Look things up.
- Let an AI assistant answer perfume questions with it.
- Build tools that read from it, from apps and bots to workflow automations.
- Call it from a browser, from a server or from an MCP client.
What you may not do
- Overload it with automated requests, or work around its limits.
- Copy it wholesale to rebuild a competing catalogue.
- Present its answers as endorsed by any perfume house.
Crediting answers
Each answer carries a scento_page link and a cite line, "Scento Perfume API, scento.com". When you show an answer, quote the lede as it stands and link the page so readers can go deeper. The n8n node and the MCP server pass the same fields through.
No warranty, and changes
The service and everything it returns is provided as is, without any warranty of accuracy, completeness or availability. Scento may change, limit or withdraw it at any time, so code defensively: check res.ok, handle found: false, and do not hard-fail when a field is null.
Privacy
The API needs no personal data and keeps no account. Requests are answered and not stored by Scento beyond the standard technical logs of its hosting providers. The details are in the privacy policy.
Questions
The developer page is the place to start; the contact address for the API is listed there and in the OpenAPI file.