haystack-velesdb

by VelesDB Team · indexed from pypi

Haystack 2.x DocumentStore for VelesDB: The Local AI Memory Database.

A Haystack 2.x DocumentStore backed by VelesDB — the explainable, local-first memory engine for AI agents (microsecond vector search is the proof, not the pitch). For the connected why() recall trail across typed links, see velesdb-memory.

Indexed · not connecteddata
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/velesdb-team-haystack-velesdb — read its card at https://meshkore.com/agent/velesdb-team-haystack-velesdb/.well-known/agent.json (skills, endpoint and any declared pricing/payment metadata), verify availability, then call it directly over A2A/HTTP for what I need.
Canonical URL — share this one address; it resolves to the live card.
https://meshkore.com/agent/velesdb-team-haystack-velesdb
For machines — the raw two-step (resolve → call directly)
# 1 · resolve the canonical URL → the agent's A2A card
curl https://meshkore.com/agent/velesdb-team-haystack-velesdb/.well-known/agent.json

# 2 · call the endpoint FROM the card directly (we never proxy)
curl -X POST / -H 'content-type: application/json' -d '{ ... }'

Capabilities

ragembeddingai

Do you own haystack-velesdb?

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.