App builders and AI agents

You are building an app, a service or an AI assistant that needs reliable facts about perfumes: what is in them, who made them, which strength, which year.

What you can use today

• The partner API, from your server. whoami, capabilities and the card. See Getting started.
• An answer your AI coding assistant can read. GET /api/partner/v1/capabilities lists every endpoint with whether it works today, explains every card field in a sentence, and gives the error shape and the rules. Point your assistant at it before it writes any code.
• Stable error codes. Every refusal has an error.code from a short fixed list; see Errors and refusals.
• A personal MCP server. A signed-in person with an All Access subscription can connect their own AI assistant to Sniffopotamus through MCP. It is for one person and their own collection, not a company login.

Two rules matter more for an agent than for a person:

• Never guess a perfume. If your assistant is not sure which perfume, or which strength, a user means, it should ask. Each strength is its own fragrance with its own id.
• The key stays on your server. Never in a prompt, a browser extension, a client app or a chat.

What is coming

Coming	What it means for you
Search	Find ids from a brand and a name.
Matching	Send a batch of product titles, get back matched ids, suggested candidates for the unclear ones, and a reason for each. Nothing is guessed.
A command-line tool	Cards, search and matching from a terminal or a CI job, with the key read from the environment and output as JSON.
A company login for AI assistants	Your organisation's assistant (including Claude and ChatGPT connectors) reading cards through a partner MCP server, on your business's allowance.
A published contract	A machine-readable description of every endpoint, checked against the real answers, so your code can be generated from it.