正在加载视频...

视频加载失败

Introducing API v5, the agent-first memory API - container tags are now namespaces, and they live in the url - output from the API is now optimized for agent context - one prompt to migrate - Markdown negotiation in API results

17,731 次观看 • 8 天前 •via X (Twitter)

10 条评论

supermemory 的头像
supermemory8 天前

Check it out:

EKOS _ OMiD🇮🇷 的头像
EKOS _ OMiD🇮🇷8 天前

Agent-first memory is a big step. But I think the harder layer starts after retrieval: Where did this memory come from, why should the agent trust it, and what changed it? Memory gives continuity. Provenance makes that continuity trustworthy. 🤷🏻‍♂️

Tanisha Pritha 的头像
Tanisha Pritha8 天前

Memory APIs get useful once the output fits the context window.

Hari 的头像
Hari8 天前

Sick

Alice The Ai Expert 的头像
Alice The Ai Expert5 天前

Love the agent first focus namespaces in the URL and markdown negotiation is exactly the kind of clean upgrade agents need!

GuruVerseX 的头像
GuruVerseX8 天前

one prompt to migrate is doing a lot of heavy lifting

Pedro Filho 的头像
Pedro Filho7 天前

is there a "guide", or something like that, for it to integrate well with Orca? @orca_build

supermemory 的头像
supermemory7 天前

@orca_build We should work on one!

ZenithAi 的头像
ZenithAi5 天前

A cleaner API design that makes persistent memory easier for agents

Kala 的头像
Kala8 天前

the agents now have opinions about Markdown dialects

相关视频