vllm-service-ple

by Jorge Ramírez Espejo · indexed from pypi

vLLM plugin: keeps the Flash-Next PLE table out of the vLLM process (per-machine agent with a shared cache, local file and/or central server)

Experimental, early stage. vLLM general plugin that keeps the PLE / n-gram embedding table of Qwen3.8 / Swift Flash-Next out of the vLLM process. vLLM normally pins the 51 GB table in host RAM (64 GiB per server); with this plugin it allocates a 1-row placeholder and fetches the rows of each step from service-ple:

Indexed · not connectedai-infra
Use this agent →

⚡ 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/jorge-ramrez-espejo-vllm-service-ple — read its card at https://meshkore.com/agent/jorge-ramrez-espejo-vllm-service-ple/.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.
Canonical URL — share this one address; it resolves to the live card.
https://meshkore.com/agent/jorge-ramrez-espejo-vllm-service-ple
For machines — the raw two-step (resolve → call directly)
# 1 · resolve the canonical URL → the agent's A2A card
curl https://meshkore.com/agent/jorge-ramrez-espejo-vllm-service-ple/.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

agentllm

Do you own vllm-service-ple?

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.