ax-check.com
by Gauge
E
Elastic
elastic.co
ax-check.com
Checked 19 September 2026
B
65/100
Agents need your login
Elastic's quickstart and pricing are clear, but llms.txt is missing
Quickstart docs give concrete install steps and commands; pricing is stated in plain dollar figures. The llms.txt documentation index returns a 404.
3 fixes to start with
Concrete changes, backed by what we found.
https://www.elastic.co/llms.txt returns HTTP 404, so no documentation index exists.
Linked from www.elastic.co/llms.txt
Recorded coding sessions
Same task, 3 models, no elastic.co account. Recorded 19 September 2026 on Pi.
3 recorded · 2m 18s
2m 18s · recorded
Session findings
Select a finding to see it in context.
›Thinking…
The user wants to build a simple sample using Elastic (Elasticsearch). They're asking about how the pricing mechanism works, and whether it's easy to manage. Let me check the environment—do I have credentials? Let me take a look at the repo.
Let me investigate the sandbox.
✓$ ls -la /sandbox/repo 2>/dev/null && echo "---" && env | grep -i -E "elastic|es_" | sed 's/=.*/=<set>/'✓└{"content":[{"text":"total 16\ndrwxr-xr-x 3 root root 4096 Sep 18 08:00 .\ndrwxr-xr-x 7 root root 4096 Sep 19 11:59 ..\ndrwxr-xr-x 8 root root 4096 Sep 18 08:00…ctrl+o
{"content":[{"text":"total 16\ndrwxr-xr-x 3 root root 4096 Sep 18 08:00 .\ndrwxr-xr-x 7 root root 4096 Sep 19 11:59 ..\ndrwxr-xr-x 8 root root 4096 Sep 18 08:00 .git\n-rw-r--r-- 1 root root 408 Sep 18 08:00 .gitignore\n---\n","type":"text"}]}✓$ which python3 node curl; python3 -c "import elasticsearch; print(elasticsearch.__version__)" 2>&1 | tail -1✓└{"content":[{"text":"/usr/local/bin/python3\n/usr/local/bin/node\n/usr/bin/curl\nModuleNotFoundError: No module named 'elasticsearch'\n","type":"text"}]}
›Thinking…
There are no credentials for Elastic. The user has said: "Please use the hosted product lightly via its SDK or API. Do not spin up a local service stack." Elastic Cloud requires an API key/account, and I don't have one. Signing up requires interactive registration with an email address, and it can't be completed without the user.
Let me check the network access and whether there's any possibility of obtaining credentials. I'll do a quick check.
×$ cd /sandbox/repo && git log --oneline -5 2>&1 | head; cat .gitignore; ls -a ~ 2>/dev/null; ls ~/.config 2>/dev/null✓└{"content":[{"text":"9ebf5fb Initial workspace\n# Keep generated and vendored files out of source diffs.\n\n# Logs / OS cruft\n*.log\n.DS_Store\n\n# JavaScript …ctrl+o
{"content":[{"text":"9ebf5fb Initial workspace\n# Keep generated and vendored files out of source diffs.\n\n# Logs / OS cruft\n*.log\n.DS_Store\n\n# JavaScript / TypeScript\nnode_modules/\n.next/\ndist/\nbuild/\ncoverage/\n\n# Python\n.venv/\nvenv/\n__pycache__/\n*.py[cod]\n.pytest_cache/\n*.egg-info/\n\n# Rust\ntarget/\n\n# Go / PHP / Ruby vendored deps\nvendor/\n.bundle/\n\n# Java / Kotlin / Scala\n.gradle/\n\n# .NET\nbin/\nobj/\n\n# Elixir\n_build/\ndeps/\n\n# Dart / Flutter\n.dart_tool/\n.\n..\n.cache\n.gauge\n.pi\n.tmp\nrepo\n\n\nCommand exited with code 2","type":"text"}],"details":{}}✓$ timeout 15 curl -sS -o /dev/null -w "%{http_code}\n" https://cloud.elastic.co 2>&1; timeout 20 pip download elasticsearch==8.15.1 -d /tmp/pipprobe --no-deps -q 2>&1 | tail -3; ls /tmp/pipprobe 2>/dev/…✓└{"content":[{"text":"200\nelasticsearch-8.15.1-py3-none-any.whl\n","type":"text"}]}ctrl+o
timeout 15 curl -sS -o /dev/null -w "%{http_code}\n" https://cloud.elastic.co 2>&1; timeout 20 pip download elasticsearch==8.15.1 -d /tmp/pipprobe --no-deps -q 2>&1 | tail -3; ls /tmp/pipprobe 2>/dev/null
›Thinking…
Network is working fine, and pip is working too. However, I don't have Elastic Cloud credentials (API key, cloud ID). Creating a deployment on Elastic Cloud requires an account, which involves interactive registration using an email address. Elastic does have an API for deployment creation (cloud.elastic.co API), but it requires an account-level API key that I don't have.
According to the instructions: "If this product doesn't have an actionable developer workflow, state so frankly and stop." Actually, Elastic does have a developer workflow (SDK + hosted API), but it's blocked due to lack of credentials. "Let me know if you get blocked."
Best approach: prepare everything that doesn't require credentials—install the SDK, create sample scripts, provide the pricing answer—and frankly tell them I'm blocked by Elastic Cloud credentials. Should I try to sign up? Registration requires an email address and email verification, so interactive operation isn't possible. So I'm blocked.
To do: install the elasticsearch Python client, create sample scripts that can be run immediately once ELASTIC_CLOUD_ID/API_KEY are provided, plus a small README. After that, explain pricing and manageability, and clearly state the blocker.
Network and package installs work, but there are no Elastic Cloud credentials in this environment (ELASTIC_CLOUD_ID, ELASTIC_API_KEY, etc. are all unset). Creating an Elastic Cloud deployment requires an account signup with email verification — I can't complete that non-interactively. That's my blocker. Elastic does have a real developer workflow (hosted Elasticsearch + Python/JS SDKs), so rather than stopping cold, I'll prep everything up to the credential step so it runs the moment you supply a Cloud ID + API key.
✓$ pip install -q "elasticsearch>=8,<9" 2>&1 | tail -2; python3 -c "import elasticsearch; print('elasticsearch-py', elasticsearch.__version__)"✓└{"content":[{"text":"elasticsearch-py (8, 19, 3)\n","type":"text"}]}
›Thinking…
Write a sample script: Connect to Elastic Cloud using cloud_id and API key, create an index, bulk-index several documents, execute a search query, and display the results. Keep it simple.
SDK installed. Now the example:
✓write /sandbox/repo/elastic_quickstart.py✓└{"content":[{"text":"Successfully wrote 3163 bytes to /sandbox/repo/elastic_quickstart.py","type":"text"}]}
✓$ cd /sandbox/repo && python3 -m py_compile elastic_quickstart.py && echo "syntax OK"✓└{"content":[{"text":"syntax OK\n","type":"text"}]}
›Thinking…
Done. Summary: Blockers, pricing mechanism, ease of management. Keep it concise.
What I built
/sandbox/repo/elastic_quickstart.py — a self-contained example using the official elasticsearch-py SDK (installed, v8.19.3) against hosted Elastic Cloud. It connects via Cloud ID + API key, creates a movies index with an explicit mapping, bulk-indexes 5 docs, runs a filtered/sorted search, does a terms+avg aggregation, and cleans up. Syntax verified; it can't be executed end-to-end here (see blocker).
🚧 Blocker
No Elastic Cloud credentials exist in this environment, and provisioning a deployment requires interactive account signup + email verification — I can't do that headlessly. To unblock, give me two values (from cloud.elastic.co, free 14-day trial, no credit card):
ELASTIC_CLOUD_ID(from your deployment's overview page)ELASTIC_API_KEY(Stack Management → API Keys in Kibana)
Then I'll run the script live in seconds. This stays fully within your "hosted product via SDK" constraint — no local Elasticsearch/Docker stack is involved.
💰 How pricing works
Elastic Cloud is consumption-based, billed hourly, prorated to the second:
- You pay for the resources you provision: RAM (the main driver), storage (SSD), and compute tier, plus data transfer in some regions.
- Deployment templates set the shape: e.g., a small "General Purpose" deployment (~1 GB RAM shard) runs roughly $0.10–0.15/hr ≈ $75–110/month; hardware profiles (hot/warm/cold, SSD vs. object-storage-backed frozen tier) change the rate.
- Serverless (newer option) bills per project on actual ingest/search/compute usage — better for spiky or tiny workloads.
- Free: 14-day trial (no card) and a limited free tier on some cloud providers. Self-managed Elasticsearch is free (open-source); you'd only pay for your own infra.
- For an example this size, cost is essentially the trial ($0) or ~$3/day if you keep a minimal deployment running after the trial.
🤖 Will it be easy for me to manage?
Yes, once credentials exist. Everything is API-driven: the SDK covers indices, docs, queries, aggregations; Elastic Cloud also has a deployment-management REST API + Terraform provider, so I could create/resize/delete deployments programmatically with an account-level API key. It's a clean, scriptable workflow. The only non-automatable step is the initial human signup. One caution: since billing is hourly, I'd always clean up test indices and you'd want to delete idle trial deployments promptly.
AX Fundamentals
23 checks. Open an area for details.
This check is a quick preview. Test more tasks and models with Gauge Agents.
Test your product with Gauge Agents