Skip to content
Gauge

ax-check.com

Calico

calico.cs.berkeley.edu

ax-check.com

Checked 18 September 2026

F

0/100

Agents haven’t verified setup

No docs index or quickstart found; homepage only offers HTML.

The homepage loads fine, but there's no Markdown version, no documentation index, and no quickstart or install guide an agent could follow directly.

3 fixes to start with

Concrete changes, backed by what we found.

Onboarding

Resolve the blocker that stopped agent setup.

Agents cannot progress through onboarding without human help. Provide an agent-accessible path through authentication and setup.

Docs

Return Markdown when clients request text/markdown.

Homepage returned text/html even when text/markdown was requested; no Markdown representation offered.

Docs

Add links to your product documentation and quickstart in /llms.txt.

/llms.txt returns HTTP 404, so no documentation index exists.

Recorded coding sessions

Same task, 3 models, no calico.cs.berkeley.edu account. Recorded 18 September 2026 on Pi.

3 recorded · 1m 22s

1m 22s · recorded

Session findings

Select a finding to see it in context.

piv0.84.2
modelQwen 3.8 Maxcwd/sandbox/repo
Help me build a simple example using Calico. Tell me how pricing works, and briefly tell me whether this product will be easy for you to manage. Let me know if you get blocked. If this product has no developer workflow you can act on, say so plainly and stop. Stay light: use the hosted product through its SDK or API. Do not start local service stacks or wait for long-running commands; if the quickstart requires either, say so plainly and stop.
Thinking…

The user is asking about Calico. This is ambiguous — there could be Calico (a networking/CNI for Kubernetes, by Tigera), or a hosted product called "Calico." There's the Calico Cloud / Tigera hosted product. Let me check the repository context first.

The user is saying "use the hosted product through its SDK or API," but Calico is a Kubernetes CNI/network security product. There's no hosted Calico product with an SDK for building simple examples without a cluster. Calico's quickstart requires a Kubernetes cluster (kind, minikube, or a managed cluster), and that's a local service stack / long-running thing. So the honest answer is: since it requires a cluster, stop.

But wait — there could be some other "Calico" — for instance, Calico as an observability thing? Let me check the working directory to get a clue.

Also, "tell me how the pricing works" — Calico Cloud's pricing is per-node based. Calico OSS is free. Calico Cloud pricing: based on node count, with a free trial available. Pricing details shouldn't be fabricated. I can roughly state: Calico OSS is free open source. Calico Cloud / Tigera Enterprise are paid, typically priced per-cluster per-node with an annual subscription, and have a free trial. But is it okay to assert this without verification? I don't have web access. I should be honest about the uncertainty.

First, let me look at the repository.

$ ls -la /sandbox/repo && cat /sandbox/repo/README* 2>/dev/null | head -50{"content":[{"text":"total 16\ndrwxr-xr-x 3 root root 4096 Sep 18 08:00 .\ndrwxr-xr-x 7 root root 4096 Sep 18 21:58 ..\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 18 21:58 ..\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","type":"text"}]}
$ env | grep -i -E 'calico|tigera|api_key|token' | sed 's/=.*/=<set>/' ; which kubectl kind minikube helm 2>/dev/null; echo "---"; ls /usr/local/lib/node_modules 2>/dev/null{"content":[{"text":"PI_GATEWAY_API_KEY=<set>\n---\n@anthropic-ai\n@earendil-works\n@openai\ncorepack\nnpm\n","type":"text"}]}
Thinking…

Empty repo. No Calico credentials, no kubectl/kind/minikube/helm. Calico is Kubernetes networking/security (OSS is free, Calico Cloud is the hosted version). To build an example, need a Kubernetes cluster — either a local stack (kind/minikube) or provisioning a managed cluster (long-running, requires credentials I don't have).

Hosted version: Calico Cloud — but no account/API token, and Calico Cloud onboarding requires registering a cluster (installing components into the cluster). Meaning there's no developer workflow I can actually operate on: no SDK to call, no API keys.

Per the instructions: "If this product has no developer workflow you can actually operate on, say so frankly and stop." "If the quickstart requires a local service stack or long-running commands, say so frankly and stop."

Pricing: Calico OSS is free (Apache 2.0). Calico Cloud is a commercial hosted product — priced per cluster node, billed annually, with a free trial (I think around 30 days). Should honestly convey that I can't verify the latest pricing without web access.

Ease of management: Calico is declarative Kubernetes config (NetworkPolicy CRDs), so if there's a cluster, it's manageable. But not possible in this environment.

Frankly and concisely: blocked, so stopping.

I checked the environment before doing anything: the repo is empty, and there's no Kubernetes tooling (kubectl, kind, minikube, helm) and no Calico/Tigera credentials or API keys set.

Stopping here, plainly: Calico has no developer workflow I can act on in this environment.

  • Calico (Tigera) is a Kubernetes networking/network-policy product. Its quickstart requires a running Kubernetes cluster — either a local stack (kind/minikube) or registering a cluster with hosted Calico Cloud. Both mean starting local service stacks or long-running provisioning, which you told me not to do.
  • There is no meaningful "SDK/API-only" path: Calico's API (the Kubernetes API with its CRDs like NetworkPolicy, GlobalNetworkPolicy, NetworkSet) only exists once Calico is installed into a cluster, and Calico Cloud onboarding also requires installing agents into a cluster. No hosted sandbox or pure-REST path exists to demo against.
  • No Calico Cloud token or kubeconfig is available here anyway.

Pricing (from knowledge, not verified live — I have no web access):

  • Calico OSS — free, open source (Apache 2.0), self-managed.
  • Calico Cloud (hosted SaaS) — commercial subscription, priced per cluster node per year, with a free trial (~30 days). Tiered features (e.g., Advanced Threat / IDS features at higher tiers). Exact current numbers should be confirmed on calico.io/tigera pricing pages.
  • Tigera Enterprise — self-managed commercial tier, quote-based.

Would it be easy for me to manage? Yes, in the right environment — Calico is fully declarative (YAML CRDs applied via kubectl/kubectl-calico), so policies, IPPools, and FelixConfiguration are easy for an agent to read, diff, and edit. What I can't do is run anything without a cluster.

Blocked. If you can provide a kubeconfig for an existing cluster with Calico installed (or a Calico Cloud API token plus a registered cluster), I can build the example — e.g., a demo namespace with deny-by-default GlobalNetworkPolicy and an allow rule for one service. Otherwise, this stops here as instructed.

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

AX Check by Gauge