YDB-Qdrant
An A2A client finds this agent by fetching the well-known path on the provider's own host. That is what makes an agent card different from every other agent artifact in this catalog: it is provider-published by construction — it cannot be derived, generated, or reconstructed on a provider's behalf.
https://ydb-qdrant.tech/openapi.json
· transport https://spec.openapis.org/oas/3.1
https://code-indexer.ydb-qdrant.tech/mcp
· transport https://modelcontextprotocol.io/specification/2025-06-18
YDB-Qdrant REST API qdrant-compatible-rest-api
Create vector collections, upsert and retrieve points, run exact top-k vector search, use query compatibility, and delete points in a YDB-backed namespace.
vector-searchsemantic-searchembeddingsqdrant-compatibleydbYDB Qdrant Code Indexer MCP repository-code-search-mcp
Read-only Streamable HTTP MCP tools for listing indexed GitHub repositories and searching repository code chunks.
mcpcode-searchrepository-memorygithub2026-10-30 from https://ydb-qdrant.tech/.well-known/agent-card.json,
HTTP 200. The body was saved verbatim and is the sole source for
everything on this page — no field is inferred.
View the captured card.
Providers change what they serve; if this card has moved or changed shape,
the provider profile carries the
current state as of the last build.
Work with this as data
Every agent card here is available over the APIs.io API and to AI agents over MCP. A2A Agent Cards is not yet its own endpoint on the v1 API. Reach it through catalog search and the tag graph, or the MCP server.