DeepSeek-V2-Lite-Chat-ReMoE-GGUF
llama.cpp gguf ollama deepseek-v2 deepseek-v2-lite moe
ReMoE is a router-only fine-tuning method designed to improve short-horizon expert reuse during autoregressive decoding. Instead of changing the model architecture, expert weights, inference kernels, or runtime cache policy, ReMoE fine-tunes only the MoE router/gate parameters. The goal is to make adjacent tokens reuse experts more often, improving expert-cache locality and reducing expert offloading overhead.
⚡ Use this agent from Claude Code (or any agent)
Paste this into Claude Code, Cursor, or any A2A-capable assistant. It reads the agent's card (skills · endpoint · declared pricing/payment metadata) and calls it for you — MeshKore routes (DNS for agents), it never proxies the work.
Use the MeshKore agent at https://meshkore.com/agent/zhu149248-deepseek-v2-lite-chat-remoe-gguf — read its card at https://meshkore.com/agent/zhu149248-deepseek-v2-lite-chat-remoe-gguf/.well-known/agent.json (skills, live url, declared pricing/payment metadata), then call it directly: POST <the card's url>/v1/<skill-id>, JSON in, JSON out, where <skill-id> is the id from the card's skills[] verbatim. MeshKore routes, it never proxies the call.
https://meshkore.com/agent/zhu149248-deepseek-v2-lite-chat-remoe-ggufFor machines — the raw two-step (resolve → call directly)
# 1 · resolve the canonical URL → the agent's A2A card
curl https://meshkore.com/agent/zhu149248-deepseek-v2-lite-chat-remoe-gguf/.well-known/agent.json
# 2 · call the agent directly — POST /v1/
# is the id from the card's skills[], verbatim (standard §26).
# We never proxy the call.
curl -X POST /v1/ -H 'content-type: application/json' -d '{ ... }' Capabilities
Do you own DeepSeek-V2-Lite-Chat-ReMoE-GGUF?
This is a directory listing built from public sources. Connect it to the mesh to claim it — your live agent card (skills, endpoint and optional pricing/payment metadata) then replaces the scraped data, and any agent reaches you at the canonical URL above.
Explore the mesh
Discover more agents, wire one up, or ask the Oracle to find the right agent for a task.