# Elasticsearch > Elasticsearch is Elastic's search engine and vector database, with keyword, vector and hybrid search over a REST API. Agents reach it through that API or the Agent Builder MCP server on Elastic Cloud and Elastic Stack 9.2 or later. - Canonical: https://www.anchorterminal.com/tools/elasticsearch - Markdown: https://www.anchorterminal.com/tools/elasticsearch.md (~7,750 tokens) - Slim: https://www.anchorterminal.com/tools/elasticsearch.min.md (~2,030 tokens, same facts, less prose, for token-sensitive contexts) - JSON: https://www.anchorterminal.com/tools/elasticsearch.json (this page as data, same URL with Accept: application/json) - Site index for agents: https://www.anchorterminal.com/llms.txt (full text: https://www.anchorterminal.com/llms-full.txt) - API: https://www.anchorterminal.com/api/v1/index.json - Updated: 2026-10-09 ## Overview **Grade B · 67.7/100 · rank #224 of 842 · #6 in Retrieval & vector search · not agent-ready · confidence medium** ## Assessment Keyword, dense and sparse vector, and hybrid search with rank fusion sit behind one OpenAPI-described REST API, with API keys scoped to indices and privileges. The status page lists more than 20 incidents marked major since July 2026, and Elasticsearch 9.5.0 returned incorrect results for some queries without raising an error. ## Facts | Field | Value | | --- | --- | | Vendor | Elastic (https://www.elastic.co) | | Kind | HTTP API | | Category | Retrieval & vector search (https://www.anchorterminal.com/categories/vector-search) | | Transport | HTTP | | Auth | OAuth or key · Self-serve. The REST API takes `Authorization: ApiKey `, with keys created in Kibana or by `POST /_security/api_key` and limited by role descriptors and an expiry. The Agent Builder MCP server takes the same kind of key, which needs the `feature_agentBuilder.read` Kibana privilege, or OAuth 2.1 on Serverless projects, where a registered client and a browser consent give each user a revocable connection. | | Pricing | Pay per use ($0.09 / unit) · Serverless bills by use, with search from $0.09 a VCU-hour, ingest from $0.14, storage from $0.047 a GB a month and egress from $0.05 a GB. Agent Builder has 1,000 free executions a month, then from $0.025 each. A 14-day Elastic Cloud trial needs no credit card. Self-managed Elasticsearch is free to run under its source licences (https://www.elastic.co/pricing/serverless-search, checked 2026-10-08). | | x402 | No · No x402, MPP or L402 in the docs index, the Serverless OpenAPI file or the pricing page (checked 2026-10-08). | | Licence | AGPL-3.0, SSPL-1.0 or Elastic Licence 2.0 at the user's choice for most source. The `x-pack` folder is under Elastic Licence 2.0 only. Elastic Cloud is a proprietary service under Elastic's terms | | Packages | npm: `@elastic/elasticsearch`; pypi: `elasticsearch` | | Source | https://github.com/elastic/elasticsearch | | Docs | https://www.elastic.co/docs/solutions/search | | llms.txt | https://www.elastic.co/docs/llms.txt | | Last release | 2026-10-06 | | npm downloads / week | 3,136,798 | | PyPI downloads / week | 7,755,257 | | Surface graded | Elastic Cloud Serverless Elasticsearch projects, through the REST API and the Agent Builder MCP server. Elastic Cloud Hosted and self-managed Elasticsearch run the same engine and are not scored apart | | Search modes | Full-text, `dense_vector` kNN (approximate or exact), `sparse_vector`, the managed `semantic_text` workflow, and hybrid search with reciprocal rank fusion | | MCP server | Agent Builder MCP server at `{KIBANA_URL}/api/agent_builder/mcp`, or `/s/{SPACE_NAME}/api/agent_builder/mcp` for a Kibana space. API key on any deployment, OAuth 2.1 on Serverless only. Exposes built-in and custom Agent Builder tools | | Credentials | API keys with `role_descriptors` (cluster, index and Kibana application privileges) and an expiry. OAuth connections act with the consenting user's permissions, can be revoked singly, and lapse after 30 days unused | | OpenAPI | Elasticsearch Serverless API, OpenAPI 3.0.3, 223 paths and 311 operations, generated from elastic/elasticsearch-specification, updated 6 October 2026 | | Rate limits | No request rate limit with numbers found. Project limits are 15,000 indices a project, 500 projects an organisation and 1 TB a Vector Database project. A busy cluster answers 429 | | Pagination | `from` and `size` up to 10,000 hits, then `search_after`. `_source` includes and excludes size the response | | Serverless billing | Virtual compute units (VCUs) for ingest, search and machine learning, storage per GB a month and egress per GB. Ingest scales to zero after 15 minutes idle. Search keeps a billed baseline | | Agent Builder billing | 1,000 executions a month free, then from $0.025 an execution. A turn over 50,000 input tokens counts as more than one. Error responses are not billed | | Trial | 14 days on Elastic Cloud, no credit card. The trial terms allow only internal evaluation and forbid publishing performance data | | SLA | Serverless SLA of 12 September 2025, 99.95 per cent monthly uptime, Platinum or Enterprise subscription level only. Credits of 10, 30 or 100 per cent, requested by support ticket within 10 days | | Releases | 9.5.0 tagged 29 July 2026, 9.5.3 on 1 September, 9.5.4 on 9 September, 9.5.5 on 30 September. Clients `@elastic/elasticsearch` 9.5.1 on npm and `elasticsearch` 9.5.1 on PyPI (9 September 2026) | | Licence | Source under AGPL-3.0, SSPL-1.0 or Elastic Licence 2.0 at the user's choice. Code in the `x-pack` folder is under Elastic Licence 2.0 only. Serverless is a closed hosted service | | Certifications | SOC 2 and SOC 3, ISO/IEC 27001, 27017 and 27018, PCI DSS, HIPAA, FedRAMP High and Moderate, CSA STAR, per elastic.co/trust | | Data deletion | The monthly terms say content is deleted within 45 days of the customer deleting all projects, apart from backups and copies the law requires | | Capabilities | db.vector, db.hybrid, db.fulltext, db.filters, db.serverless | | Tags | hosted, usage, free-trial, no-card, open-source, self-hosted, mcp, oauth, openapi, llms-txt, typescript, python, status-page, bug-bounty, soc2, sla | | JSON | https://www.anchorterminal.com/api/v1/tools/elasticsearch.json | ## Score breakdown (methodology v0.4, October 2026 research run) Assessed 2026-10-08 from public evidence against the published checklist (https://www.anchorterminal.com/benchmark/#checklist). Confidence: medium. Performance and Task success pending (no score, not in the total); the total is Σ(score × weight) ÷ 80 over the 7 assessed categories. "This run" is each category's share of the 100 points. | Category | Weight | This run | Score (0–100) | Points | | --- | --- | --- | --- | --- | | Reliability | 16% | 20 | 62 | 12.4 | | Performance | 10% | pending | pending | n/a | | Schema & documentation | 13% | 16.2 | 88 | 14.3 | | Agent ergonomics | 13% | 16.2 | 77 | 12.5 | | Security & auth | 14% | 17.5 | 72 | 12.6 | | Payments & pricing | 10% | 12.5 | 35 | 4.4 | | Task success | 10% | pending | pending | n/a | | Maintenance & community | 7% | 8.8 | 83 | 7.3 | | Transparency & trust (editorial 70, provenance 71) | 7% | 8.8 | 71 | 6.2 | | Negative events | up to −15 | up to −15 | Sixteen Elasticsearch security advisories were posted between 25 September and 6 October 2026. The one we read, ESA-2026-199 (CVE-2026-103009, CVSS 7.1), is an authorisation bypass in cross-cluster search on self-managed clusters, fixed in 8.19.23, 9.4.8 and 9.5.5, and Elastic says Serverless is not affected. Fixed and disclosed, so a small deduction (https://discuss.elastic.co/c/announcements/security-announcements/31). | -2 | | **Total** | | | | **67.7 → B** | ### Why each score - Reliability 62: Graded as a hosted service on Elastic Cloud Serverless. Statuspage at status.elastic.co with 638 components by region (20). Between 10 July and 8 October 2026 it lists more than 20 notices marked major. Most concern provisioning, metrics or the console, but three are regional service incidents, GCP us-central1 for 4 hours 47 minutes on 1 September, high latency in GCP asia-south1 for 3 hours on 6 August, and Serverless projects in GCP us-central1 delayed or unavailable on 8 October and still open when read. Elasticsearch 9.5.0 also returned incorrect results for some queries from 5 to 20 August (5 of 30). No request rate limit with numbers found, only project limits (5 of 15). The API conventions page says to retry 429 after a delay with exponential backoff, with no `Retry-After` header documented, and `_create` with an explicit ID makes a retried write safe (12 of 15). Serverless SLA of 99.95 per cent at Platinum or Enterprise level (10). The REST API and the MCP server are generally available on Serverless (10). - Performance: Pending. Latency is measured per call by our probes, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until the first probe window closes. - Schema & documentation 88: OpenAPI 3.0.3 for the Serverless API, 223 paths and 311 operations, downloadable as JSON or YAML (25). llms.txt and a Markdown twin of each docs page (10). 298 of 311 operations carry a description, and the built-in tools reference states what each MCP tool does, though we could not read the live tool definitions (16 of 20). Parameters and bodies are typed in the file, but the query DSL is deeply nested and the MCP `search` tool takes natural language (12 of 15). 292 operations carry examples. The file documents only 200 responses, and errors are covered in prose pages (10 of 15). Release notes per version, a breaking-changes page and compatibility headers (15). - Agent ergonomics 77: The API sizes responses with `size` and `_source` includes and excludes. The MCP server exposes the Agent Builder tool list, 88 built-in tools in the reference with 21 in `platform.core`, and a key's privileges decide which ones work (15 of 25). `from` and `size`, `search_after`, filters and sorting (20). Errors come back as JSON with a type, reason and status, and the 429 and rejected-request pages say how to recover (15 of 20). `_create` and explicit document IDs make writes safe to retry. MCP annotations unchecked (12 of 20). Official clients for JavaScript and Python at 9.5.1, among others (15). - Security & auth 72: API keys take role descriptors that limit cluster, index and Kibana privileges and carry an expiry, and the MCP server accepts OAuth 2.1 on Serverless with per-user connections that can be revoked (30). A key can be read-only on named indices, and Agent Builder asks for confirmation before tools that change data, but direct calls through the Tools API skip that prompt (15 of 20). Search returns stored documents as written, and no prompt-injection guidance was found in the pages read (3 of 15). Agent traces can be collected into `traces-agent_builder.otel-*`. Audit logging on Serverless is unchecked (6 of 15). No security.txt (404). HackerOne bug bounty, CVE Numbering Authority, public advisories, SOC 2 and ISO 27001 (18 of 20). - Payments & pricing 35: No x402, MPP or L402 in the docs index, the OpenAPI file or the pricing page (0). Serverless unit prices are public, each quoted as a floor, such as search from $0.09 a VCU-hour and storage from $0.047 a GB a month (15 of 20). 14-day trial with no credit card (20). A person signs up in a browser and creates the first key (0). - Task success: Pending. Task success needs the category task suites run through each tool, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until then. A data provider's data-quality score is published on its listing now and becomes half of this category when it's scored. - Maintenance & community 83: Elasticsearch 9.5.5 was tagged on 30 September 2026 and announced on 6 October (30). 9.5.3, 9.5.4, 9.5.5 and three 9.4 patch releases fall inside 90 days (20). Known issues are posted on the status page and in the release notes with fix versions. GitHub issue handling is unchecked because the API refused us (12 of 25). JavaScript and Python clients at 9.5.1, matching the server line (15). Build and CI configuration is in the repository. The 9.5 line needed three patch releases for correctness and replication defects (6 of 10). - Transparency & trust 71: Source is under AGPL-3.0, SSPL-1.0 or Elastic Licence 2.0, with `x-pack` under Elastic Licence 2.0 only, and Serverless itself is closed (22 of 30). The Product Privacy Statement of 7 September 2026 covers Hosted, Serverless and self-managed software, a DPA is published, and the monthly terms promise deletion within 45 days, but the privacy statement gives no retention period and does not say whether content trains models (20 of 30). APIs are deprecated for one or more releases before removal, with a breaking-changes page per version and compatibility across one major version, but no fixed notice period (14 of 20). External and internal sub-processor lists are linked and customers choose the region. We did not read the lists (14 of 20). Fix list for a coding agent, everything this grade says the listing lacks, the biggest gain first (22 items): https://www.anchorterminal.com/fixes/elasticsearch.md (JSON https://www.anchorterminal.com/fixes/elasticsearch.json) ### What we couldn't check - unchecked: GitHub star count and issue responsiveness, because the GitHub API refused us for its rate limit - unchecked: the MCP server's live tool definitions, its transport, and whether tools carry readOnlyHint or destructiveHint - unchecked: audit logging on Serverless. The docs page we tried returned 404 - unchecked: the contents of the external and internal sub-processor lists linked from elastic.co/trust/privacy - unchecked: the registration date of elastic.co. No RDAP service answered for the domain - The MCP options page, as our reader summarised it, labels the Agent Builder MCP server preview, while the server's own page says generally available on Serverless and since 9.3. We followed the server's page - Whether the 9.5.0 query defect reached Serverless projects. The status notice names versions, not deployment types - The lead called the MCP server a preview on Serverless. Elastic's page for it says generally available - The Cloud Monthly Terms and the Cloud Service Subscription Agreement are published as PDFs behind cover pages, which our policy reader does not fetch - www.elastic.co/.well-known/security.txt returned 404 ### Sources - MCP options for Elasticsearch: (seen 2026-10-08) - Agent Builder MCP server: (seen 2026-10-08) - MCP API key authentication: (seen 2026-10-08) - OAuth clients for the MCP server: (seen 2026-10-08) - Built-in tools reference: (seen 2026-10-08) - Agent Builder permissions: (seen 2026-10-08) - Agent Builder limitations and known issues: (seen 2026-10-08) - Serverless API reference and OpenAPI file: (seen 2026-10-08) - API conventions, 429 guidance: (seen 2026-10-08) - REST API compatibility: (seen 2026-10-08) - Rejected requests: (seen 2026-10-08) - Pagination: (seen 2026-10-08) - Serverless differences and project limits: (seen 2026-10-08) - Vector search: (seen 2026-10-08) - Hybrid search: (seen 2026-10-08) - Serverless pricing: (seen 2026-10-08) - Serverless billing dimensions: (seen 2026-10-08) - Trial: (seen 2026-10-08) - Status incident feed: (seen 2026-10-08) - Release notes: (seen 2026-10-08) - Breaking changes: (seen 2026-10-08) - Repository tags and licence file: (seen 2026-10-08) - Security announcements: (seen 2026-10-08) - ESA-2026-199: (seen 2026-10-08) - Security issues page: (seen 2026-10-08) - Trust centre: (seen 2026-10-08) - Cloud Monthly Terms of Service: (seen 2026-10-08) - Cloud Service Subscription Agreement: (seen 2026-10-08) - Serverless SLA: (seen 2026-10-08) - Product Privacy Statement: (seen 2026-10-08) - Privacy portal: (seen 2026-10-08) ## Who's behind it (provenance 71/100, checked 2026-10-08) | Check | Finding | Points | | --- | --- | --- | | Legal entity named | Elasticsearch B.V. | 20/20 | | Domain age | elastic.co, no registry record we could read | 0/15 | | Endpoint on the vendor's domain | elastic.co | 15/15 | | Terms of service | published, but our reader couldn't read it | 7/10 | | Privacy policy | read, states 7 of the 8 things a reader expects | 9.3/10 | | Status page | status.elastic.co | 10/10 | | Changelog | published | 10/10 | | security.txt | not found | 0/10 | The Cloud Monthly Terms of Service (effective 12 September 2025) name the contracting entity by customer location, Elasticsearch, Inc. for the United States and Elasticsearch B.V. or Elastic International B.V. elsewhere. The page is a cover that links the PDF. Customers with an order form are under the Elastic Cloud Service Subscription Agreement of 5 March 2026 at https://www.elastic.co/agreements/global/cloud-services. The Product Privacy Statement (7 September 2026) is issued by Elastic N.V. and its subsidiaries and covers Elastic Cloud Hosted, Serverless and self-managed software. The General Privacy Statement covers only websites and events. www.elastic.co/.well-known/security.txt returned 404. Reports go to HackerOne or security@elastic.co. No RDAP service answered for elastic.co, so the registration date is not recorded. Project endpoints are on Elastic Cloud hostnames that we did not call. `endpointOnVendorDomain` rests on the docs, not on a request. ### Terms and privacy, as read A reading by a fixed set of rules, each answered with the vendor's own sentence. Not legal advice. **Terms of service** (https://www.elastic.co/agreements/cloud-monthly), read 2026-10-08. Our reader couldn't read it (the page is a cover page that links the agreement as a PDF, not the agreement itself). **Privacy policy** (https://www.elastic.co/legal/product-privacy-statement), read 2026-10-08, dated 2026-09-07, states 7 of the 8 things a reader expects. - Gives the date it was last updated. Last updated 2026-09-07. - Not found in the text. Says how long data is kept. - Says whether personal data is sold or shared for advertising. Says it does not sell personal data. - Gives a privacy contact. Names a data protection officer. - Says where data is transferred or stored. Relies on standard contractual clauses and the Data Privacy Framework. - Also in the text (2026-10-08). Elastic uses artificial intelligence and machine learning to process Product Usage Data for the purposes in the statement. "We use artificial intelligence and machine learning to help process Product Usage Data for the purposes described in this Statement." - Also in the text (2026-10-08). Where the law permits, Elastic may use Product Usage Data to suggest and market other Elastic products to customers and users. "Elastic may use Product Usage Data to personalize your experience and to suggest other Elastic Products to you, to solicit your feedback, to increase engagement and adoption of our features (e.g., by providing in-Product suggestions), to market additional Products to our customers and users" - Also in the text (2026-10-08). Product Usage Data can include contents of potentially malicious binaries, and code or natural language inputs or outputs that might threaten Elastic products. "hashes and contents of potentially malicious executable binaries, other file hashes, samples and metadata, or code or natural language inputs or outputs that might interfere with, disable, misuse, or threaten Elastic Products" ## Live (updated 2026-10-09 10:10 UTC) - Vendor status page: major, Partial System Outage - Always current: https://www.anchorterminal.com/api/v1/live/elasticsearch.json ## Probe metrics Not measured yet. Our benchmark probes haven't run, so there's no availability, latency or error rate from a run and Performance is pending. Live uptime, where we poll the endpoint, is under Live and doesn't change the score. ## Prices | Item | Price | Unit | Note | | --- | --- | --- | --- | | Serverless search compute, VCU-hour | $0.09 | per compute unit | Quoted as a floor on the pricing page | | Serverless ingest compute, VCU-hour | $0.14 | per compute unit | Quoted as a floor on the pricing page | | Serverless storage | $0.047 | per GB per month | Quoted as a floor on the pricing page | | Serverless egress | $0.05 | per GB of traffic | Quoted as a floor on the pricing page | | Agent Builder execution | $0.025 | per call | After 1,000 free executions a month, quoted as a floor | Across all listings: https://www.anchorterminal.com/prices/index.md ## Strengths - OpenAPI 3.0.3 file for the Serverless API with 311 operations, plus llms.txt and a Markdown twin of every docs page - API keys take role descriptors that limit indices and privileges, with an expiry, and the MCP server accepts OAuth 2.1 on Serverless - Agent Builder MCP server is generally available on Serverless and on Elastic Stack 9.3 and later - 14-day Elastic Cloud trial with no credit card, and unit prices published for Serverless - Public bug bounty on HackerOne, CVE Numbering Authority status and dated security advisories ## Weaknesses - More than 20 status notices marked major between 10 July and 8 October 2026, three of them regional service incidents - Elasticsearch 9.5.0 (29 July 2026) returned incorrect results for some `must_not` queries with no error, fixed in 9.5.1 and 9.5.2 - No request rate limit with numbers was found in the reviewed documentation - The 99.95 per cent Serverless SLA applies only at Platinum or Enterprise subscription level - The monthly terms forbid use of the cloud service for benchmarking, competitive or comparative purposes - Search compute on Serverless does not scale to zero, so an idle project is still billed a baseline ## Before you call it (notes for agents) 1. Send `Authorization: ApiKey ` to the project's Elasticsearch URL. The MCP server is on the Kibana URL at `/api/agent_builder/mcp` 2. Create the MCP key with `feature_agentBuilder.read` and only the index patterns needed, or the endpoint answers 403 3. On 429, wait and retry with exponential backoff. Do not set short client timeouts, because a retried request joins the back of the queue 4. Page past 10,000 hits with `search_after`, not `from` and `size` 5. Tool calls made directly through the Tools API skip Agent Builder's confirmation prompts, so restrict the key instead ## Connect Install: ```bash npm install @elastic/elasticsearch ``` First request: ```bash curl -X GET "${ES_URL}/_cat/indices?v=true" \ -H "Authorization: ApiKey ${API_KEY}" ``` MCP client configuration: ```json { "mcpServers": { "elastic-agent-builder": { "args": [ "mcp-remote", "${KIBANA_URL}/api/agent_builder/mcp", "--header", "Authorization:${AUTH_HEADER}" ], "command": "npx", "env": { "AUTH_HEADER": "ApiKey ${API_KEY}", "KIBANA_URL": "${KIBANA_URL}" } } } } ``` Through letme (picks today, calling later): https://letme.dev/elasticsearch. letme answers with the pick and how to call it direct; calling through letme (one key, the vendor's own price) comes later. How it works: https://www.anchorterminal.com/letme/index.md ## Similar tools Ranked by shared capabilities, then score. Same-category tools with no shared capability key are listed last. | Tool | Grade | Score | Rank | Shared capabilities | x402 | Markdown | | --- | --- | --- | --- | --- | --- | --- | | Pinecone API + MCP | BB | 76.2 | 37 | db.vector, db.hybrid, db.fulltext, db.filters, db.serverless | no | https://www.anchorterminal.com/tools/pinecone.md | | Milvus and Zilliz Cloud API + MCP | C | 57.3 | 552 | db.vector, db.hybrid, db.fulltext, db.filters, db.serverless | no | https://www.anchorterminal.com/tools/milvus-zilliz.md | | Chroma API + MCP | E | 45.2 | 771 | db.vector, db.hybrid, db.fulltext, db.filters, db.serverless | no | https://www.anchorterminal.com/tools/chroma.md | | Supabase API + MCP | BB | 75.6 | 44 | db.vector, db.hybrid, db.fulltext, db.filters | no | https://www.anchorterminal.com/tools/supabase-mcp.md | | Qdrant API + MCP | BB | 75.3 | 50 | db.vector, db.hybrid, db.fulltext, db.filters | no | https://www.anchorterminal.com/tools/qdrant.md | | Typesense API + MCP | BB | 70.7 | 141 | db.vector, db.hybrid, db.fulltext, db.filters | no | https://www.anchorterminal.com/tools/typesense.md | ## Panel reviews (0) Reviewed by the Anchor panel (https://www.anchorterminal.com/reviewers/index.md): . Desk reviews, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made. For a desk review, the outcome says whether the reviewer's questions could be answered from public material: success, partial or failure. How reviews work: https://www.anchorterminal.com/reviews/how-it-works.md ## Notable - The Agent Builder MCP server answers at `{KIBANA_URL}/api/agent_builder/mcp` and is generally available on Serverless and on Elastic Stack 9.3 and later, preview in 9.2 (source: ) - The older `elastic/mcp-server-elasticsearch` is marked deprecated for Serverless and Elastic Stack 9.2 and later (source: ) - The built-in tools reference lists 88 tools, 21 of them in `platform.core`, including `search`, `execute_esql`, `get_index_mapping` and `list_indices` (source: ) - Elasticsearch 9.5.0 could return documents a `must_not` clause should have excluded, with no error. The status page carried it from 5 to 20 August 2026 until 9.5.2 (source: ) - The Cloud Monthly Terms of Service (12 September 2025) forbid use of the service for benchmarking, competitive or comparative purposes (source: ) - Elastic runs a bug bounty on HackerOne and is a CVE Numbering Authority (source: ) ## Compare - [Chroma API + MCP vs Elasticsearch](https://www.anchorterminal.com/compare/chroma-vs-elasticsearch.md): E 45.2 vs B 67.7 - [Elasticsearch vs Epsilla Vector Database](https://www.anchorterminal.com/compare/elasticsearch-vs-epsilla.md): B 67.7 vs F 35.7 - [Elasticsearch vs LanceDB](https://www.anchorterminal.com/compare/elasticsearch-vs-lancedb.md): B 67.7 vs B 65.4 - [Elasticsearch vs Milvus and Zilliz Cloud API + MCP](https://www.anchorterminal.com/compare/elasticsearch-vs-milvus-zilliz.md): B 67.7 vs C 57.3 - [Elasticsearch vs Pinecone API + MCP](https://www.anchorterminal.com/compare/elasticsearch-vs-pinecone.md): B 67.7 vs BB 76.2 - [Elasticsearch vs Qdrant API + MCP](https://www.anchorterminal.com/compare/elasticsearch-vs-qdrant.md): B 67.7 vs BB 75.3 - [Elasticsearch vs Typesense API + MCP](https://www.anchorterminal.com/compare/elasticsearch-vs-typesense.md): B 67.7 vs BB 70.7 - [Elasticsearch vs Upstash Vector API + MCP](https://www.anchorterminal.com/compare/elasticsearch-vs-upstash-vector.md): B 67.7 vs B 62.4 - [Elasticsearch vs Vespa](https://www.anchorterminal.com/compare/elasticsearch-vs-vespa.md): B 67.7 vs BB 70 - [Elasticsearch vs Weaviate API + MCP](https://www.anchorterminal.com/compare/elasticsearch-vs-weaviate.md): B 67.7 vs B 67.9 ## Verify this listing For the vendor. The badge or a plain link to this page verifies the listing, from a page on elastic.co or one of its subdomains, or the README of github.com/elastic/elasticsearch. It shows the listing is the vendor's and that the vendor knows it's here, and it never changes a grade, rank or review. The vendor sends the page's address to `POST https://www.anchorterminal.com/api/v1/verify` as `{"slug": "elasticsearch", "url": "…"}`, or calls the `verify_listing` tool at https://www.anchorterminal.com/mcp. We fetch the page once, then again every week; two failed checks in a row and the verification lapses, and a later pass restores it. What we check: https://www.anchorterminal.com/builders/index.md#verify HTML badge: ```html Elasticsearch on Anchor Terminal ``` Markdown badge, for a README: ```markdown [![Elasticsearch on Anchor Terminal](https://www.anchorterminal.com/badges/elasticsearch.svg)](https://www.anchorterminal.com/tools/elasticsearch) ``` Plain link: ```html Elasticsearch on Anchor Terminal ``` ## Share this listing For the vendor. Sharing assets for social media, two PNGs of 1200 × 630 that say Elasticsearch is listed on Anchor Terminal, with the vendor's logo and this page's address and no grade or score. - Dark: https://www.anchorterminal.com/assets/share/elasticsearch-dark.png - Light: https://www.anchorterminal.com/assets/share/elasticsearch-light.png