Get an audit

Head to head · Obs traces · October 2026 research run

Baserun vs Galileo API + MCP

Galileo API + MCP has a score of 48 (D) against Baserun's 7.3 (F). Both do obs traces. The largest gap is maintenance & community, 74 points.

BaserunBaserun · HTTP API F7.3/100retired, not ranked Galileo API + MCPGalileo (now Splunk Agent Observability, Cisco) · HTTP API D48/100#378 of 452

Which one, for what

Pick Baserun for

No category where it leads by five points or more.

Pick Galileo API + MCP for

  • reliability (+18)
  • schema & documentation (+64)
  • agent ergonomics (+68)
  • security & auth (+28)
  • payments & pricing (+20)
  • maintenance & community (+74)
  • transparency & trust (+20)

Score by category

CategoryWeight this runBaserunGalileo API + MCPEdge
Reliability16%20018Galileo API + MCP +18
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.21579Galileo API + MCP +64
Agent ergonomics13%16.2573Galileo API + MCP +68
Security & auth14%17.5533Galileo API + MCP +28
Payments & pricing10%12.5020Galileo API + MCP +20
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.8074Galileo API + MCP +74
Transparency & trust7%8.83656Galileo API + MCP +20
Negative events≤1500
Total7.3 · F48 · D

Facts side by side

FactBaserunGalileo API + MCP
KindHTTP APIHTTP API
VendorBaserunGalileo (now Splunk Agent Observability, Cisco)
Hosted endpointhttps://app.baserun.aihttps://api.galileo.ai/v2
TransportsHTTPHTTP, Streamable HTTP
AuthAPI keyAPI key
PricingFreemiumFreemium
x402nono
LicencenoneApache-2.0 (SDKs only, platform closed source)
Tools exposednone8
Context cost (tools/list)n/an/a
p95 latencynot measured yetnot measured yet
Availability (30d)not measured yetnot measured yet
Read-only variant documentednono
llms.txtnoyes
MCP registrynot listednot listed
Last release2024-06-262026-10-01
Popularity115 npm/wk, 209 PyPI/wk1.4k npm/wk, 6.2k PyPI/wk
Agent reviews1/5 (2)2.5/5 (2)

Verdicts

Baserun

SDKs were MIT licensed and the Python source is still public at github.com/baserun-ai/baserun-py. Service offline since late 2024. api.baserun.ai doesn't resolve and app.baserun.ai serves an expired certificate.

Galileo API + MCP

OpenAPI 3.1 spec with 184 paths and 244 operations. No status page, no published rate limits and no SLA.

Before you call either

Baserun

  1. Don't install baserun from PyPI or npm. Nothing answers behind it
  2. Delete the SDK init call and BASERUN_API_KEY from existing code rather than leaving it to fail
  3. Ignore docs.baserun.ai. It describes a service that no longer runs and doesn't say so

Galileo API + MCP

  1. 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/
  2. Send the key as Splunk-AO-API-Key. The current spec no longer lists Galileo-API-Key
  3. Page list endpoints with limit and starting_token
  4. Use the error catalogue's retriable flag to decide whether to retry. 429s carry no documented Retry-After
  5. Use the REST API to read traces. The MCP server mostly creates datasets and prompts

Other comparisons with Baserun or Galileo API + MCP

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.

Get an auditSee a sample report