Skip to content

docs: correct openclaw plugin api reference endpoints#202

Closed
CZH-THU wants to merge 668 commits into
EverMind-AI:mainfrom
CZH-THU:openclaw_plugin_readme
Closed

docs: correct openclaw plugin api reference endpoints#202
CZH-THU wants to merge 668 commits into
EverMind-AI:mainfrom
CZH-THU:openclaw_plugin_readme

Conversation

@CZH-THU
Copy link
Copy Markdown

@CZH-THU CZH-THU commented Apr 27, 2026

Update SKILL.md API reference to match the backend routes for search and delete operations.

Description

This PR updates the API reference in openclaw-plugin's SKILL.md so the documented endpoints match the actual EverCore backend routes and HTTP methods.

Type of Change

  • Bug fix (non-breaking change that fixes an issue)
  • New feature (non-breaking change that adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • Documentation update
  • Refactoring (no functional changes)
  • Performance improvement
  • Test improvements
  • Build/CI/CD changes

Related Issues

Fixes #
Relates to #

Changes Made

  • Changed GET /api/v1/memories/search to POST /api/v1/memories/search
  • Changed DELETE /api/v1/memories to POST /api/v1/memories/delete
  • Kept all other API reference entries unchanged

Testing

  • Tested locally with manual verification
  • Added/updated unit tests
  • Added/updated integration tests
  • All existing tests pass

Test Configuration:

  • OS: Windows 10
  • Python version: N/A (documentation-only change)
  • Database versions (if relevant): N/A

Test Results:

Manual verification:
- Checked EverCore backend controller routes:
  - /api/v1/memories/search is implemented as POST
  - delete endpoint is /api/v1/memories/delete (POST)
- Confirmed SKILL.md now matches backend routing.

Checklist

  • My code follows the project's code style guidelines
  • I have performed a self-review of my code
  • I have commented my code where necessary, particularly in complex areas
  • I have updated the documentation accordingly
  • My changes generate no new warnings or errors
  • I have added tests that prove my fix is effective or that my feature works
  • New and existing unit tests pass locally with my changes
  • I have used Gitmoji in my commit messages
  • Any dependent changes have been merged and published

Screenshots (if applicable)

N/A (documentation-only change)

Additional Notes

This PR only changes documentation. No backend logic or API implementation was modified.

Breaking Changes

None.


By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
closes #191

libin.zhang and others added 30 commits December 31, 2025 18:23
Use self-deployed embedding and rerank APIs by default

See merge request npc-work/aic/ai/evermemos-opensource!64
vLLM Rerank API adopts an instruction-tuned approach

See merge request npc-work/aic/ai/evermemos-opensource!65
feat: metrics client and rerank/vectorize/retrieve metrics

See merge request npc-work/aic/ai/evermemos-opensource!66
fix:update episode prompt

See merge request npc-work/aic/ai/evermemos-opensource!68
feat: add rerank metrics

See merge request npc-work/aic/ai/evermemos-opensource!69
cyfyifanchen and others added 2 commits April 27, 2026 03:42
* chore: rename project from evermemos to EverCore

This commit renames the project directory and updates all internal references from "evermemos" to "EverCore". The changes include:
- Renaming the main directory from `methods/evermemos` to `methods/EverCore`
- Updating all import paths and module references
- Maintaining the same code structure and functionality
- Adding new configuration files (.vscode/settings.json, .pylintrc, pyrightconfig.json)
- Updating Dockerfile and project metadata

* docs: update references from evermemos to EverCore

Update documentation files to reflect the renaming of the 'evermemos' directory to 'EverCore'. This includes fixing clone commands, directory paths, and documentation links across multiple files to ensure consistency and correct navigation for users.

* chore: rename EverMemOS to EverCore across codebase

This is a project-wide rebranding from EverMemOS to EverCore. The changes include:
- Update project name in source files, documentation, and configuration
- Rename API references, environment variables, and service names
- Modify demo descriptions and benchmark configurations
- Update URLs and citations to reflect new project identity

All functionality remains identical; only naming has changed to align with the new project branding.

* docs: update README with EverCore focus and restructured TOC

- Add line break before Table of Contents for better visual separation
- Rewrite project description to highlight EverCore as the central component
- Reorder directory tree to prioritize benchmarks and methods over use-cases
- Update use-cases list with more examples and clarify they are templates
- Improve flow from Quick Start to use-cases to benchmarks

* docs: update README with clearer methods description and benchmarks

Add benchmark numbers directly in the method summaries for better visibility.
Clarify introductory text to emphasize choice and composition of methods.

* docs: fix markdown formatting in README table of contents

Adjust whitespace and line breaks to ensure proper rendering of the collapsible table of contents section.
Update SKILL.md API reference to match the backend routes for search and delete operations.
cyfyifanchen and others added 23 commits April 30, 2026 07:01
…d-AI#204)

- Replace specific EverMemBench-Dynamic badge with general EverMind-AI HuggingFace badge
- Remove redundant License badge
- Change "Methods" section heading to "Architecture Methods"
- Update sub-section headings from h4 (####) to h3 (###) for better hierarchy
…rMind-AI#208)

* docs: restructure README and add AGENTS.md for better navigation

- Reorder sections to emphasize architecture methods and use cases
- Move use cases section before quick start for better flow
- Rename "Methods" to "Architecture Methods" for clarity
- Add AGENTS.md with quick commands and key entry points
- Update section headers to improve document hierarchy
- Maintain all existing content while improving organization

* docs: add community and contribution files

* docs: reorder README directory tree for logical grouping

* docs: move community files to .github/ and update references

* ci: change deploy workflow trigger from feature branch to main
* docs: restructure README and add subdirectory guides

Move the directory tree from the main README to new dedicated README files for each top-level folder (use-cases, methods, benchmarks). Add detailed introductions and tables to guide users to the appropriate subprojects. This improves navigation and provides clear entry points for different use cases.

* docs: expand showcase section with new projects and links

Add six new project entries to the README showcase, each with a banner image, description, and code/plugin link. Also update an existing benchmark entry to include a dataset link. This enhances the repository's demonstration of real-world applications and available resources.
* docs(readme): update project links and formatting

* docs(use-cases): enhance README with visual catalogue of demos

Expand the use cases section from a simple table to a detailed visual catalogue with project banners, descriptions, and links. This improves user engagement and provides a better showcase of community integrations and demos.

* docs: update READMEs and add validation for use-case links
* docs: update plugin repository link in README

* docs(readme): update banner gif link
)

* docs(readme): update code example link to pinned commit

pin the reference to the voice assistant example code to a specific commit hash and fix folder name capitalization

* docs: update voice assistant demo link in README
* docs(readme): add four new use case entries

* docs(readme): update outdated banner links to correct github repos
…e-demo-content-payload

Fix EverCore demo memory payload
…actions-hygiene

Harden GitHub Actions workflows
…adme-quickstart

docs: verify EverCore quickstart path
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

README memory search API example is outdated