LLMSwaps

Which model each app runs today, and when it last changed

Aggregator: one subscription, several calendars

An aggregator sells access to models from several makers. One entry in this register names six, which means six retirement schedules and authority over none of them. Nothing on its page describes how such a decision would be passed on to a subscriber. As of 2026-09-22.

What has been announced, entry by entryFilled where the vendor has announced something in that column, hollow where it has not.What has been announced, entry by entryFor the aggregatorOne bill and one interfaceOne bill and one interface — For the aggregator: Several suppliers, each with its own termsSeveral makers' schedules, unseenSeveral makers' schedules, unseen — For the aggregator: No authority over any retirementA working product when one line goesA working product when one line goes — For the aggregator: A menu that has to be editedA broken series, if it used that li…A broken series, if it used that lineA broken series, if it used that line — For the aggregator: No published route for passing the news on
Fig. 1 Filled where the vendor has announced something in that column, hollow where it has not.
What aggregation changes about who decides and who is told. Recorded 2026-09-22.
For the subscriberFor the aggregator
One bill and one interfaceSeveral suppliers, each with its own terms
Several makers' schedules, unseenNo authority over any retirement
A working product when one line goesA menu that has to be edited
A broken series, if it used that lineNo published route for passing the news on

Inclusion rule. Distinctions drawn from the entries in this register that name models from more than one maker on their own pages. Order. The subscriber's position first, then the seller's.

1Aggregation helps the product and not the production

Losing one of six models leaves a functioning subscription and a broken series, if the series was established on the line that went. The consolation is real for the customer as a customer and worthless to them as a producer.

That distinction is why this register tracks model lines rather than product features. A feature list says what an app can do this month; a model list says whose roadmap somebody has quietly signed up to.

2Menus lag, and that is normal

A model list is a marketing page, so it changes when somebody updates it rather than when a maker publishes a date. One entry here still names a model whose maker has announced its interface closes.

Both statements are current and the register keeps them side by side. Resolving the tension would mean predicting what the application does next.

A menu that lags, and why that is normalA model list is a marketing page, so it changes when somebody updates it rather than when a maker publishes a date. One entry here still names a model whose maker has announced that its interface closes.A maker decidesPublishes a date fora model it built, onits own page.Not repeatedThe menuStill names themodel, because nobodyhas edited the page.Both true atonceThe subscriberReads a current menuand a currentannouncement thatdisagree.Six makers means six changelogs, in six formatsTwo entries here make their own models and resell others, which is aggregation with a floorunder it.
Fig. 2 Resolving that tension would mean predicting what the application does next, which this register declines to do.

3Where the same thing happens at the maker layer

Two entries here make their own models and resell others on the same plan table. That is aggregation with a floor under it: if every licensed row went, they would still have something to sell.

The two layers read against each other set out what difference the floor makes and what it does not.

A definition rather than a dated entry: no line above is a vendor statement. Where this word turns up in a real notice, the wording and the date are on the reading on six makers. Nearby terms: Credit conversion, Output unit, Tier gating.