Recall
Handwriting and screenshots become searchable cards, and the extension reaches Safari
A side-by-side editorial comparison of Perplexity and Semantic Kernel — release velocity, themes, recent moves, and the top alternatives to consider.
Perplexity is selling access to other people's models, and now repricing them weekly.
The Gateway API put Anthropic, OpenAI, Google, xAI, and Perplexity models behind one endpoint reachable with an existing Perplexity key, and the MCP server became a remote service hosted by Perplexity with no local installation. Since then the traffic has been commercial rather than structural: GPT-5.6 price cuts, a Sol Fast mode, and successive preset re-pointings — low and fast both now run openai/gpt-5.6-luna, with the fast preset carrying priority processing at twice standard token prices. Frozen configurations have to be updated by hand each time.
Semantic Kernel's releases are now dependency bumps and redirect READMEs pointing users elsewhere.
The .NET and Python packages ship on a steady cadence, but the contents are servicing: SDK and package version bumps, CVE-driven dependency updates, CodeQL suppressions, and HTTP hardening such as disabling automatic redirects in the web plugins. The genuinely functional changes are narrow — a Gemini connector now honoring the configured function choice behavior, an MCP tool approval callback for Azure AI agents shipped as a breaking change, and MCP tools with colliding normalized names being skipped. The latest .NET release removes migrated vector-store providers outright, leaving redirect READMEs behind.
The Gateway API put Anthropic, OpenAI, Google, xAI, and Perplexity models behind one endpoint reachable with an existing Perplexity key, and the MCP server became a remote service hosted by Perplexity with no local installation. Since then the traffic has been commercial rather than structural: GPT-5.6 price cuts, a Sol Fast mode, and successive preset re-pointings — low and fast both now run openai/gpt-5.6-luna, with the fast preset carrying priority processing at twice standard token prices. Frozen configurations have to be updated by hand each time.
Perplexity is behaving like an infrastructure vendor rather than an answer engine: the differentiator is the credential and the routing, not the model. The preset churn is the visible cost of that position — when the models underneath are someone else's, keeping a named tier meaningful means re-pointing it whenever the market moves, and passing the migration work to customers who pinned a configuration. Inline citations across the search-backed presets remain the one capability that is distinctly Perplexity's own.
Expect the preset re-pointings to keep arriving at this cadence and the priority-processing tier to spread beyond the fast preset, since a 2x price band is easier to extend than to justify on one preset alone.
The .NET and Python packages ship on a steady cadence, but the contents are servicing: SDK and package version bumps, CVE-driven dependency updates, CodeQL suppressions, and HTTP hardening such as disabling automatic redirects in the web plugins. The genuinely functional changes are narrow — a Gemini connector now honoring the configured function choice behavior, an MCP tool approval callback for Azure AI agents shipped as a breaking change, and MCP tools with colliding normalized names being skipped. The latest .NET release removes migrated vector-store providers outright, leaving redirect READMEs behind.
The centre of gravity is moving out of this repository. Vector store providers have migrated to CommunityToolkit packages and their originals are now deleted rather than deprecated, with samples following them across. What remains is maintenance plus the occasional MCP fix, which suggests the agent work that would once have landed here is happening in a different codebase. For teams with Semantic Kernel in production, the signal to read is the removals: each one is a dependency that now resolves somewhere else.
Expect the cadence to continue as security and dependency servicing with occasional MCP fixes, and for migration tooling or documentation pointing at Microsoft Agent Framework to grow faster than any new capability in Semantic Kernel itself.
Other ai-assistants products tracked by Sparkpulse, ranked by recent ship velocity. Each card links to a full editorial trajectory and lets you pivot into a head-to-head comparison with either Perplexity or Semantic Kernel.
Handwriting and screenshots become searchable cards, and the extension reaches Safari
Evaluation content dominates a feed whose real move was handing agents the admin panel
A release train of small runtime wins between model drops
ClearML is filling in the hyperdataset lifecycle while hardening the SDK against what it loads.
Baseten is selling to the labs that build models, not just the developers who call them.
Between a BTS tie-in and free student plans, Gemini quietly moves into a Waymo
See all Perplexity alternatives → · See all Semantic Kernel alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — mcp — within ai-assistants. Perplexity is currently shipping more aggressively (velocity 8.8 vs 5.0), with 1 editorial sparks in the last 30 days against 0. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Perplexity is currently shipping more aggressively (velocity 8.8 vs 5.0), with 1 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other ai-assistants products to evaluate alongside.
Top Perplexity alternatives in ai-assistants are ranked by recent ship velocity. Browse the "Perplexity alternatives" section above for the current picks, or visit /alternatives/perplexity for the full list with editorial commentary on each.
Top Semantic Kernel alternatives in ai-assistants are ranked by recent ship velocity. Browse the "Semantic Kernel alternatives" section above for the current picks, or visit /alternatives/semantic-kernel for the full list with editorial commentary on each.