Named things

The registry lists models, developer tools and AI-first products, and records which technique each one demonstrates, with a primary source and the date it was checked. That is the whole of it. It is not a buyer’s guide: it carries no prices, no seat costs, no setup effort and no measure of quality, it ranks nothing, and it does not cover the ordinary business software a person already runs that has since grown an AI feature. Use it to work out what a product is doing underneath, not to choose which one to pay for.

If you want to buy rather than build, four things are worth asking about any product in any category. This site cannot answer them for you, because every answer depends on the plan and is the seller’s to state, but a seller who cannot answer them has told you something.

• Which level it operates at. Does it answer one request at a time, run a fixed workflow somebody wrote down, or decide its own next step? That is the question this site’s eight levels ask, and the answer sets both what the product can do without you and how many ways it can go wrong.
• Who else holds the text. The model’s maker is rarely the only company that receives what you type: the product in front of it keeps its own copy under its own terms. Who else holds the text says whose pages to read, in what order, and what the intermediaries usually do not say.
• Whether a person approves before anything is sent or changed. Ask whether an approval step exists, whether it is on by default, and what it actually covers: a message sent, a record changed, a payment made.
• Whether you can get the work back out. The documents, the records and the history, exported in a format another program can read, and what happens to them when you stop paying.