Perfumeo
Perfumeo (Perfumeo(R)) is a consumer-hardware startup that built an AI-driven smart-home fragrance diffuser — a connected device holding scent capsules that its companion mobile app uses to adapt diffusion to the user's mood. The company describes itself as combining AI, data science, "green mechatronics" and green chemistry, and states it was founded in Paris in July 2021 and relocated to Cupertino, California in April 2023. It is an end-user product company: no public API, SDK, developer portal, webhook surface or machine-readable contract has ever been published, and none was found in this pass. As of 2026-08-26 the domain the company itself lists as its website, www.perfumeo-ai.com, no longer belongs to it — WHOIS shows the domain was created 2026-06-12 under a Dynadot privacy proxy on domain-parking nameservers, and it now serves a bot-challenge interstitial followed by a "Coming Soon" holding page. The company's LinkedIn page remains up and lists a headcount of one.
Index entry only — little beyond a description and a link, and nothing machine-readable enough for an agent to act on without a human reading the site first.
Perfumeo is tracked in the API Evangelist network. This page is the human-readable profile that sits on top of the machine-readable index we maintain at apis.io.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Perfumeo scores 4.6/100 (minimal), with a separate agent-readiness read of 0/100 (human only). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Why this profile is thin
The domain Perfumeo itself publishes as its website, perfumeo-ai.com, was re-registered on 2026-06-12 behind a Dynadot privacy proxy on domain-parking nameservers and now answers a JS bot-challenge and then a "Coming Soon" holding page, with wildcard DNS and an HTTP catch-all that returns an identical 200 HTML shell for every path and every subdomain including invented ones.
This is an honest zero, not a gap in our research. Perfumeo does not appear to expose an API, so there is nothing here for us to index and nothing for them to fix.
What we probed
https://perfumeo-ai.com/→ HTTP 200https://perfumeo-ai.com/openapi.json→ HTTP 200https://perfumeo-ai.com/.well-known/agent-card.json→ HTTP 200https://github.com/perfumeo→ HTTP 404https://registry.npmjs.org/perfumeo→ HTTP 404https://www.linkedin.com/company/perfumeo→ HTTP 200
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance. Every facet and dimension name is a link: it opens that measurement's page on APIs.io, where the rating runs across the whole catalog — the exact checks that feed it, how every profiled provider distributes on it, and who is at the top of it.
Put this on your own site. The badge is drawn live from Perfumeo's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/perfumeo/"
title="Perfumeo on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/perfumeo.svg"
alt="Perfumeo Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>
[](https://providers.apievangelist.com/providers/perfumeo/)
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/perfumeo/"
title="Perfumeo on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/perfumeo/card.svg"
alt="Perfumeo Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>
More shapes, themes and sizes → · Score as JSON · How badges work
Resources
Every other property we hold for Perfumeo — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Company 1
The organization behind the API
Perfumeo is in the network as a tracked entity. We haven't yet indexed a public API surface for it — when one is published, the artifacts, score, and agent-readiness read will appear here automatically. The source repository is where that profile is built.
← All providers · Data indexed from github.com/api-evangelist/perfumeo · machine-readable index on apis.io
This is an independent, third-party profile of Perfumeo, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.