【v1.1.0】开放接口讨论 /api/v1/memories/search

[guguTang]

1、是否考虑将GET =》 POST，（请求传了body）
2、可否将返回的score归一化，以便应用层使用。（目前根据retrieve_method的方式是直接返回的hit或vector的得分，建议统一归一化。使score安全可用）

[freshpomelo]

1. We support both GET and POST, and we recommend POST.
2. We need to discuss this issue.

[guguTang]

1、测试发现只支持GET的

[freshpomelo]

1、测试发现只支持GET的

I need to re-explain the current status. Using GET for search is more RESTful, as POST suggests data modification. We've opted to support a request body in GET because it handles complex, nested data better and avoids the character limits of query strings. Don't worry about compatibility—virtually all clients support this pattern. For flexibility, we still support query_params as an alternative.

[cyfyifanchen]

Closing this as part of the EverOS 1.0 issue triage. This issue references the pre-1.0 API or retired infrastructure such as /api/v1/memories, /api/v3/agentic/*, MongoDB, Elasticsearch, Milvus, Redis, Kafka, longjob, or old memory type names. EverOS 1.0 uses POST /api/v1/memory/{add,flush,search,get} with Markdown + SQLite + LanceDB. Migration notes are tracked in PR #258: #258. If the same behavior still occurs on current main with the 1.0 API, please open a fresh issue with a 1.0 repro.

[cyfyifanchen]

Post-triage verification: keeping this closed because the 1.0 API already moved memory search to POST under /api/v1/memory/search. The remaining score-normalization discussion is still preserved in open issue #45, so this older combined pre-1.0 API discussion does not need to stay open separately.