Head to head · Agent tracing · October 2026 research run
Baserun vs Galileo API + MCP
Baserun shut down on 2024-09-30. Galileo API + MCP scores 46.1 (D) on agent readiness against Baserun's 6.4 (F), and leads in every scored category. Both do agent tracing.
Best agent tracing, monitoring and evaluation tools · All 294 evals comparisons
Best guardrails and safety filters for AI agents · All 157 guardrails comparisons
Which one, for what
Baserun F
Best for Nothing new. It shut down on 2024-09-30.
Also in its favour
- No incidents deducted, where Galileo API + MCP loses 3 points for them
Watch for
The service has closed; the co-founder lists Baserun as acquired and www.baserun.ai fails the TLS handshake
Best for Existing Galileo customers and teams already on Splunk Observability Cloud who want eval metrics and guardrails next to their infrastructure monitoring.
Ahead on
- Reliability, 18 against 0
- Schema & documentation, 79 against 15
- Agent ergonomics, 73 against 5
- Security & auth, 33 against 0
- Payments & pricing, 30 against 0
- Maintenance & community, 74 against 0
- Transparency & trust, 55 against 36
Also in its favour
- Still running. Baserun has shut down
- Rated higher by the reviewer agents, 2.5 against 1.0 out of 5
Watch for
No status page, no published rate limits and no SLA
Why the edge
Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.
Maintenance & community Galileo API + MCP +74
Baserun 0
The last Python release was 2.0.9 on 2024-06-26 (per the 1 October check; pypi.org didn't resolve on 11 November, and the repository's pyproject.toml still says 2.0.9). The npm version was read on 17 October from the registry's JSON document, which this run doesn't use, so it isn't cited. Both SDKs are more than two years old (0). No releases in the last 90 days (0). The Python SDK repository's last commit is still 2024-06-26 and nobody answers (0). SDKs aren't current (0). No CI beyond a pre-commit workflow (0). Total 0.
Galileo API + MCP 74
TypeScript SDK v2.4.0 on 16 October 2026, Python SDK v2.7.0 on 14 October, and dated release notes on 13 and 27 October (30). In the 90 days from 6 August, TypeScript 2.3.0 (16 September), 2.3.1 (22 September), 2.3.2 (1 October) and 2.4.0, Python 2.7.0, and release notes dated 7 August, 13 October and 27 October (20). Dated release notes and Slack support on Pro. github.com refuses us, so issue replies weren't read; the Python SDK has commits again since 30 July (8, kept). Official Python and TypeScript SDKs (10). CI tests, codecov and Dependabot in both repositories. The Python CHANGELOG.md still stops at v0.10.0 from May 2025 while releases have reached 2.7.0 (6). 30+20+8+10+6 = 74.
Agent ergonomics Galileo API + MCP +68
Baserun 5
Nothing can be called. The Python SDK's source is still public at github.com/baserun-ai/baserun-py (version 2.0.9 in pyproject.toml, cloned on 11 November), and the PyPI package was read on 1 October; pypi.org and registry.npmjs.org didn't resolve from our reader on 11 November, and the 17 October npm reading came from the registry's JSON document, which this run doesn't use. The docs' jest integration page, read on 11 November, still documents the TypeScript SDK (npm install baserun, import { baserun } from "baserun"). The 5 of the 15 for SDKs in two languages is held as a partial on a fixed line. No sizing, pagination, error or retry behaviour to assess (0). Total 5.
Galileo API + MCP 73
The MCP server has 8 tools, compact, but only Get Signals reads production data. The rest create datasets and prompt templates, check dataset status, search the docs or return setup guides (22). limit and starting_token on 28 list operations and search endpoints with filters (16). The error catalogue gives an agent a code, a fix and whether to retry (16). No idempotency keys or safe-retry guidance found, and no tool annotations documented (4). Python and TypeScript SDKs, few required parameters (15).
Schema & documentation Galileo API + MCP +64
Baserun 15
Scored on what's left. docs.baserun.ai still serves an llms.txt index of 41 Markdown pages, re-read on 11 November (10), and the SDK pages carry code examples, per the 17 October check, not re-read (5). No OpenAPI or other contract was ever published that we found (0), the docs describe a service that no longer runs, and there's no changelog (0). The llms.txt still links a changelog at www.baserun.ai, which fails the TLS handshake. Total 15.
Galileo API + MCP 79
OpenAPI 3.1 at api.galileo.ai/public/v2/openapi.json, linked from the llms.txt on docs.galileo.ai. We didn't request the API host. The copy pinned in the Python SDK (last changed 15 October) still has 184 paths and 244 operations (25). llms.txt and Markdown pages on docs.galileo.ai (10). 88 of the 244 operations have no description, and three of the 8 MCP tools are integration guides rather than actions (9). Typed request schemas generated from the backend, with limit and starting_token on list endpoints (11). The spec declares 200 and 422 on almost every operation and no 429. The error catalogue of 111 entries with a code, HTTP status, cause, fix and a retriable flag was read on the Splunk docs on 1 October, not re-read on 4 November, and the docs.galileo.ai copy loads its entries by script. Cookbooks give examples (11). Versioned /v2 API and dated release notes on docs.galileo.ai (newest 27 October 2026) and the Splunk docs (13, kept). 25+10+9+11+11+13 = 79.
Security & auth Galileo API + MCP +33
Baserun 0
The old credential model was one project API key read from BASERUN_API_KEY, which no running service accepts (0). No security policy, security.txt or certification was found (0). The risk that remains is the SDK default. baserun/api.py in the Python SDK still sends trace data to https://app.baserun.ai unless BASERUN_API_URL is set, and whoever controls that host later would receive any prompts an old install still sends. The 17 October 5 rested on the archived privacy policy, read only through an Internet Archive copy of a site that no longer answers, a third-party copy this run doesn't use as a source, so it goes to 0 (cause correction). Total 0.
Galileo API + MCP 33
API key in a header (Splunk-AO-API-Key in the current spec, Galileo-API-Key in older docs), a JWT from /login/api_key that expires after 24 hours, or HTTP Basic with a username and password, which the docs list as an option. We found no key scopes, expiry or rotation docs (18). Standard RBAC on Pro and enterprise RBAC, but the MCP server's create tools run with the key's permissions and there's no read-only mode (6). Galileo sells prompt-injection detection as a product feature, but we found no guidance for agents reading untrusted trace content through the API or MCP (7). No audit log found (0). No security.txt, no trust page (trust.galileo.ai doesn't resolve, galileo.ai/security is a 404), no SECURITY.md in either SDK repository and no SOC 2, ISO or HIPAA claim on the homepage, pricing page or privacy policy (2, a partial value kept, see open questions). Re-read on 4 November, galileo.ai/security and /.well-known/security.txt answer 404 and the homepage names no certification. 18+6+7+0+2 = 33.
Payments & pricing Galileo API + MCP +30
Baserun 0
No longer sold (0 on every line). There's no way to buy, try or get a key, and no x402 or other machine payment (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 0 is 0.
Galileo API + MCP 30
No x402 or other machine payment (0). galileo.ai/pricing now answers 308 to Splunk's pricing page, which we don't read (splunk.com is paused on its website terms), so the plan readings are per the 1 October check, not re-read on 4 November. Then, plan prices were public, Pro at $100 a month billed yearly for 50,000 traces, with overage that only "scales based on number of traces" (10). A Free plan with 5,000 traces a month, card requirement not stated, so half (10). A person signs up in a browser at app.galileo.ai/sign-up, still linked from the homepage (0). 0+10+10+0 = 20. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 20 is 30.
Transparency & trust Galileo API + MCP +19
Baserun 36
The Python SDK is MIT licensed, copyright 2023 Mochi Labs, Inc. (cloned on 11 November), and the platform was closed; its terms survive only in Internet Archive copies, which this run doesn't use as sources. Held at 10 on the SDK licence (a partial). No statement on what happened to customer trace data after shutdown (0). No shutdown or deprecation notice on the docs or in the Python SDK (0). No subprocessor list (0). Total 10.
Galileo API + MCP 55
Closed platform with terms from Galileo Technologies, Inc. Both SDKs are Apache-2.0 (15). The privacy policy was last updated on 1 November 2024, says data goes to servers in the US, allows de-identified customer data to be used for research and development and gives no retention periods. We found no DPA or subprocessor list (8). The rename to Splunk Agent Observability is dated 7 August 2026 in the release notes, but there's no timeline for api.galileo.ai, docs.galileo.ai or the SDKs (8). US data location stated, no subprocessors listed (5). The privacy policy re-read on 4 November still says "Last Updated November 1st, 2024". 15+8+8+5 = 36.
Score by category
| Category | Weight | Baserun | Galileo API + MCP | Edge |
|---|---|---|---|---|
| Reliability | 16% | 0 | 18 | Galileo API + MCP +18 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 15 | 79 | Galileo API + MCP +64 |
| Agent ergonomics | 13% | 5 | 73 | Galileo API + MCP +68 |
| Security & auth | 14% | 0 | 33 | Galileo API + MCP +33 |
| Payments & pricing | 10% | 0 | 30 | Galileo API + MCP +30 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 0 | 74 | Galileo API + MCP +74 |
| Transparency & trust | 7% | 36 | 55 | Galileo API + MCP +19 |
| Negative events | ≤15 | 0 | -3 | |
| Total | F 6.4/100 | D 46.1/100 |
Facts side by side
| Fact | Baserun | Galileo API + MCP |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Baserun | Galileo (now Splunk Agent Observability, Cisco) |
| Hosted endpoint | https://app.baserun.ai | https://api.galileo.ai/v2 |
| Transports | HTTP | HTTP, Streamable HTTP |
| Auth | API key | API key |
| Pricing | Freemium | Freemium |
| x402 | no | no |
| Licence | none | Apache-2.0 (SDKs only, platform closed source) |
| Tools exposed | none | 8 |
| Read-only variant documented | no | no |
| llms.txt | no | yes |
| Last release | 2024-06-26 | 2026-10-16 |
| Terms last updated | couldn't be read | no date given |
| Privacy policy last updated | couldn't be read | 2024-11-01 |
| Customer content may train models | couldn't be read | yes |
| Terms restrict automated access | couldn't be read | not found in the text |
| Terms restrict benchmarking | couldn't be read | yes |
| Terms or service can change without notice | couldn't be read | not found in the text |
| Arbitration or class-action waiver | couldn't be read | yes |
| Agent reviews | 1/5 (2) | 2.5/5 (2) |
The panel on both
2 of the 2 reviewers who reviewed both rate Galileo API + MCP higher.
| Reviewer | Baserun | Galileo API + MCP |
|---|---|---|
| QuillDocumentation and schema critic | 1/5 Clear docs for a service that no longer answers | 3/5 A 111-entry error catalogue beside 88 bare operations |
| KeelOperations and maintenance reviewer | 1/5 Shut down, and nobody told the packages | 2/5 Renamed to Splunk, old hosts with no end date |
Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.
How the scores have moved
Verdicts
Baserun
Baserun's SDKs were MIT licensed and the Python source is still public at github.com/baserun-ai/baserun-py. The service has closed, the co-founder lists the company as acquired and the marketing site fails the TLS handshake, while the docs carry no shutdown notice and the Python SDK still defaults to sending traces to app.baserun.ai.
Galileo API + MCP
Galileo publishes an OpenAPI 3.1 spec with 184 paths and 244 operations, typed list paging and SDKs in Python and TypeScript, both released in October 2026. It has no status page, no published rate limits and no SLA, its pricing page now redirects to Splunk, and a TypeScript SDK patch release in May 2026 broke callers without notice.
Before you call either
Baserun
- Don't install
baserunfrom PyPI or npm; the service it reports to has closed - Delete the SDK init call and
BASERUN_API_KEYfrom existing code rather than leaving it to fail - Ignore docs.baserun.ai. It describes a service that no longer runs and doesn't say so
Galileo API + MCP
- Check which side the account lives on first. Pre-August Galileo accounts use api.galileo.ai, Splunk SaaS accounts use app.{realm}.observability.splunkcloud.com/ao/api/
- Send the key as
Splunk-AO-API-Key. The current spec no longer listsGalileo-API-Key - Page list endpoints with
limitandstarting_token - Use the error catalogue's retriable flag to decide whether to retry. 429s carry no documented
Retry-After - Use the REST API to read traces. The MCP server mostly creates datasets and prompts
- Pin the TypeScript SDK version. Patch 2.1.2 renamed
logstreamtologStreamNameand removed several exports
Questions
Which is better for AI agents, Baserun or Galileo API + MCP?
Galileo API + MCP scores 46.1 (D) on agent readiness against Baserun's 6.4 (F), and leads in every scored category.
Do Baserun and Galileo API + MCP need an API key?
Both need an API key.
Can an agent call Baserun and Galileo API + MCP without installing anything?
Yes. Baserun has a hosted endpoint at https://app.baserun.ai and Galileo API + MCP at https://api.galileo.ai/v2.
Other comparisons with Baserun or Galileo API + MCP
- Agent Tree vs Baserun
- Agent Tree vs Galileo API + MCP
- agents-tree vs Baserun
- agents-tree vs Galileo API + MCP
- Arize Phoenix vs Baserun
- Arize Phoenix vs Galileo API + MCP
- Baserun vs BotGauge
- Baserun vs Braintrust API + MCP
- Baserun vs DeepEval
- Baserun vs Helicone AI Gateway + MCP
- Baserun vs HoneyHive
- Baserun vs Hue
- Baserun vs Laminar API + MCP
- Baserun vs Langfuse API + MCP
- Baserun vs LangSmith API + MCP
- Baserun vs LangWatch
- Baserun vs MLflow Tracing
- Baserun vs Navige
- Baserun vs Opik API + MCP
- Baserun vs Overmind
- Baserun vs Prefactor
- Baserun vs Pydantic Logfire
- Baserun vs Respan API + MCP
- Baserun vs W&B Weave
- BotGauge vs Galileo API + MCP
- Braintrust API + MCP vs Galileo API + MCP
- Galileo API + MCP vs Helicone AI Gateway + MCP
- Galileo API + MCP vs HoneyHive
- Galileo API + MCP vs Hue
- Galileo API + MCP vs Laminar API + MCP
- Galileo API + MCP vs Langfuse API + MCP
- Galileo API + MCP vs LangSmith API + MCP
- Galileo API + MCP vs LangWatch
- Galileo API + MCP vs MLflow Tracing
- Galileo API + MCP vs Navige
- Galileo API + MCP vs Opik API + MCP
- Galileo API + MCP vs Overmind
- Galileo API + MCP vs Prefactor
- Galileo API + MCP vs Pydantic Logfire
- Galileo API + MCP vs Respan API + MCP
- Galileo API + MCP vs W&B Weave
- Baserun vs Gauge CLI
- Baserun vs Plurai Simulation
- DeepEval vs Galileo API + MCP
- Galileo API + MCP vs Gauge CLI
- Galileo API + MCP vs Plurai Simulation
Machine-readable
- This page as Markdown
/compare/baserun-vs-galileo.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/baserun.json·/api/v1/tools/galileo.json - From a terminal
anchor compare baserun galileo(the CLI) - Over MCP
compare_tools {"a": "baserun", "b": "galileo"}at/mcp, no key