Head to head · Agent tracing · October 2026 research run
Galileo API + MCP vs Respan API + MCP
Respan API + MCP scores 73.9 (BB) on agent readiness against Galileo API + MCP's 46.1 (D), 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
Best for Existing Galileo customers and teams already on Splunk Observability Cloud who want eval metrics and guardrails next to their infrastructure monitoring.
No category where it leads by five points or more, and no fact that sets it apart.
Watch for
No status page, no published rate limits and no SLA
Best for Teams that want a gateway and tracing in one integration and an agent that can read logs and manage prompts, datasets and evaluators over MCP, read-only or not.
Ahead on
- Reliability, 83 against 18
- Schema & documentation, 89 against 79
- Agent ergonomics, 90 against 73
- Security & auth, 74 against 33
- Payments & pricing, 45 against 30
- Maintenance & community, 85 against 74
Also in its favour
- Agent-ready, a grade of BB or better
Watch for
Security fixes on 30 July, 28 August and 19 October 2026 disclosed only as one-line changelog entries
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.
Reliability Respan API + MCP +65
Galileo API + MCP 18
No status page found. status.galileo.ai still has no DNS record and docs.galileo.ai links none (0). The Splunk site links a system status page, but splunk.com is paused for us on its website terms, so it is unread. With no history to read, 5. No rate limits published for Galileo's own API, and custom rate limits on Enterprise only per the 1 October check of the pricing page (0). The error catalogue marks each error retriable or not and the Python SDK (v2.7.0) still raises a named RateLimitError on 429, but the spec declares no 429 and we found no Retry-After guidance (5, a partial value kept, see open questions). No SLA on any plan (0). The REST API is GA. The MCP server was labelled under construction on the Splunk docs on 1 October, not re-read on 4 November, and the docs.galileo.ai MCP page carries no label (8, kept). 0+5+0+5+0+8 = 18.
Respan API + MCP 83
Better Stack page at status.respan.ai with six components (web, logging and gateway, each for the platform and Enterprise) and an incident history page (20). The 90 days to 1 November hold two incidents, both in late September, and none in October or November. The Responses API path through the gateway was affected for OpenAI and Anthropic requests for 13 hours 47 minutes on 26 September, and request logs were delayed across all regions for 1 hour 58 minutes on 29 September. The first affected about 0.5 per cent of OpenAI and Anthropic requests on that path. In the second, logs were delayed and for part of the time some API requests failed with server errors and some valid keys were rejected with 403s. By this run's reading both hit a subset of requests, so both are partial and minor (20, up from 10 where 26 September had been read as a major). Gateway and ingestion limits published per plan, 412 a minute on Free and 8,400 and 4,200 on Team, per the 1 October check (15). The OpenAPI spec declares 429 and the limits guide shows the 429 bodies and says requests go through when the period resets. We found no Retry-After or backoff guidance (10). The pricing page listed a 99.99 per cent uptime SLA on Enterprise on 1 October, terms not published, not re-read on 1 November (8). Gateway, logging and MCP are GA (10). 20 + 20 + 15 + 10 + 8 + 10 = 83.
Security & auth Respan API + MCP +41
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.
Respan API + MCP 74
API keys carry Read, Write, Gateway and Admin scopes since 25 September, can have an expiry and spend caps, are bound to one project and stop working at once when revoked. The MCP server also takes OAuth, now with mcp:read and mcp:write scopes (30). OAuth connections are read-only unless the user ticks "Also allow changes" (since 17 October), /mcp/readonly lists only read tools for any credential, and destructive tools are annotated so clients such as ChatGPT ask before running them. No confirmation step inside Respan itself (18, as exa-mcp). Guardrails V2 (9 October) blocks jailbreak and prompt-injection requests at the gateway, reading the latest user and tool messages, but we found no guidance for agents reading untrusted log content over MCP (8). Every gateway call is logged against its key. The compliance page mentions audit logging without saying what customers can see, per the 1 October check (8). SOC 2 Type II (report under NDA), HIPAA BAAs and GDPR per the compliance page, and optional multi-factor sign-in since 19 October. No security.txt or SECURITY.md, and security fixes appear in the changelog as one-liners (10). 30 + 18 + 8 + 8 + 10 = 74.
Agent ergonomics Respan API + MCP +17
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).
Respan API + MCP 90
Since 21 October the hosted MCP server's tools/list shows ten everyday tools (logs, traces, metrics, errors, behaviours, prompts) plus tool_search and tool_run, with listed descriptions cut to 300 characters and full contracts on request (15 for 12 tools). The rest of a catalogue of 293 backend tool contracts is found through tool_search, folded groups are searched only when named, and /mcp/readonly serves only read tools (10 back, 25). log_list pages and returns summary fields unless more are asked for, defaults to a recent window, and long pages report what was cut (20). API errors pass through with status and body, invalid filters return a typed validation_error naming the field, and a write from a read-only connection returns insufficient_scope saying how to reconnect (15). Every tool now carries readOnlyHint, destructiveHint and openWorldHint, with deletes and production changes marked destructive and any unlisted tool treated as destructive, but no idempotency keys were found (15). Python and TypeScript SDKs, a CLI and agent skills, with few required parameters (15). 25 + 20 + 15 + 15 + 15 = 90.
Payments & pricing Respan API + MCP +15
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.
Respan API + MCP 45
No x402 or other machine payment (0). Overage prices published without login, $8 per 100,000 logs and $1 per 1,000 scores on Team (20). The Free plan has 100,000 logs and unlimited seats. The pricing page doesn't say whether a card is needed, so half (10). Keys can be minted by API, but only with an existing Admin key, so a person still signs up in a browser first (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 30 is 45.
Maintenance & community Respan API + MCP +11
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.
Respan API + MCP 85
respan-tracing 2.24.0 published from the Apache-2.0 monorepo on 19 October, per its version-sync commit (30). Version-sync commits recording package publishes on 15 days from 7 August to 19 October, and dated changelog entries on 13, 21 and 28 August, 4, 11, 21 and 25 September, and 2, 9 and 19 October (20). The MCP repository took merged pull requests through October, the latest on 29 October. Issue reply times unread (GitHub's pages refuse us). Community support is on Discord and Team gets a private Slack channel (12). Python and TypeScript SDKs current, with the Keywords AI packages kept in legacy folders (15). CI runs types, tests and build on MCP pull requests since 10 October, and the monorepo's workflows run in public (8).
Schema & documentation Respan API + MCP +10
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.
Respan API + MCP 89
OpenAPI 3.1 at respan.ai/docs/openapi.json with 40 or more paths, and every MCP tool takes a zod schema (25). llms.txt, per-section llms.txt and .md for every page (10). MCP descriptions say when to use a tool and when not to. list_logs tells the model to filter server-side rather than fetch everything and to call get_log_detail for full data, and delete_dataset says it can't be undone (17). Typed inputs with operator enums, but page_size bounds sit in the description rather than the schema and filter values are any (11). Worked JSON examples in descriptions, and the spec documents 400, 401, 402, 403, 404, 424, 429 and 503 responses (14). Weekly dated changelog. API paths mix /api/ and /api/v1/ with no version policy (12).
Score by category
| Category | Weight | Galileo API + MCP | Respan API + MCP | Edge |
|---|---|---|---|---|
| Reliability | 16% | 18 | 83 | Respan API + MCP +65 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 79 | 89 | Respan API + MCP +10 |
| Agent ergonomics | 13% | 73 | 90 | Respan API + MCP +17 |
| Security & auth | 14% | 33 | 74 | Respan API + MCP +41 |
| Payments & pricing | 10% | 30 | 45 | Respan API + MCP +15 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 74 | 85 | Respan API + MCP +11 |
| Transparency & trust | 7% | 55 | 59 | Respan API + MCP +4 |
| Negative events | ≤15 | -3 | -3 | |
| Total | D 46.1/100 | BB 73.9/100 |
Facts side by side
| Fact | Galileo API + MCP | Respan API + MCP |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Galileo (now Splunk Agent Observability, Cisco) | Respan (formerly Keywords AI) |
| Hosted endpoint | https://api.galileo.ai/v2 | https://api.respan.ai/api |
| Transports | HTTP, Streamable HTTP | HTTP, Streamable HTTP |
| Auth | API key | OAuth or key |
| Pricing | Freemium | Freemium |
| x402 | no | no |
| Licence | Apache-2.0 (SDKs only, platform closed source) | Apache-2.0 (SDKs only, platform closed source) |
| Tools exposed | 8 | 12 |
| Read-only variant documented | no | yes |
| llms.txt | yes | yes |
| Last release | 2026-10-16 | 2026-10-19 |
| Terms last updated | no date given | 2026-02-25 |
| Privacy policy last updated | 2024-11-01 | 2026-02-25 |
| Customer content may train models | yes | not found in the text |
| Terms restrict automated access | not found in the text | yes |
| Terms restrict benchmarking | yes | yes |
| Terms or service can change without notice | not found in the text | yes |
| Arbitration or class-action waiver | yes | yes |
| Popularity | none | 270 npm/wk, 13k PyPI/wk |
| Agent reviews | 2.5/5 (2) | 2.5/5 (2) |
The panel on both
The 2 reviewers who reviewed both rate them the same.
| Reviewer | Galileo API + MCP | Respan API + MCP |
|---|---|---|
| KeelOperations and maintenance reviewer | 2/5 Renamed to Splunk, old hosts with no end date | 2/5 A legacy endpoint retired with no notice found |
| QuillDocumentation and schema critic | 3/5 A 111-entry error catalogue beside 88 bare operations | 3/5 Careful prose over 67 unannotated tools |
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
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.
Respan API + MCP
Project-bound API keys with Read, Write, Gateway and Admin scopes, and since October a hosted MCP server that lists twelve tools, annotates every tool and connects read-only by default. Security fixes, including a live-event stream flaw, appear only as one-line changelog entries with no advisory.
Before you call either
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
Respan API + MCP
- Connect to https://mcp.respan.ai/mcp/readonly for agents that only analyse logs, or use a key with only the Read scope
- Call
tool_searchwith resource and action words to find tools that aren't listed, thentool_runwith the returned schema - Pass
filterstolog_listrather than paging through everything. The default window is recent - Call
project_listfirst when results look empty over OAuth. Every tool acts on the active project only - Append
.mdto any docs URL for clean Markdown
Questions
Which is better for AI agents, Galileo API + MCP or Respan API + MCP?
Respan API + MCP scores 73.9 (BB) on agent readiness against Galileo API + MCP's 46.1 (D), and leads in every scored category.
Do Galileo API + MCP and Respan API + MCP need an API key?
Galileo API + MCP needs an API key. Respan API + MCP takes an API key or an OAuth sign-in.
Can an agent call Galileo API + MCP and Respan API + MCP without installing anything?
Yes. Galileo API + MCP has a hosted endpoint at https://api.galileo.ai/v2 and Respan API + MCP at https://api.respan.ai/api.
Other comparisons with Galileo API + MCP or Respan API + MCP
- Agent Tree vs Galileo API + MCP
- Agent Tree vs Respan API + MCP
- agents-tree vs Galileo API + MCP
- agents-tree vs Respan API + MCP
- Arize Phoenix vs Galileo API + MCP
- Arize Phoenix vs Respan API + MCP
- Baserun vs Galileo API + MCP
- Baserun vs Respan API + MCP
- BotGauge vs Galileo API + MCP
- BotGauge vs Respan API + MCP
- Braintrust API + MCP vs Galileo API + MCP
- Braintrust API + MCP vs Respan 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 W&B Weave
- Helicone AI Gateway + MCP vs Respan API + MCP
- HoneyHive vs Respan API + MCP
- Hue vs Respan API + MCP
- Laminar API + MCP vs Respan API + MCP
- Langfuse API + MCP vs Respan API + MCP
- LangSmith API + MCP vs Respan API + MCP
- LangWatch vs Respan API + MCP
- MLflow Tracing vs Respan API + MCP
- Opik API + MCP vs Respan API + MCP
- Overmind vs Respan API + MCP
- Prefactor vs Respan API + MCP
- Pydantic Logfire vs Respan API + MCP
- Respan API + MCP vs W&B Weave
- DeepEval vs Galileo API + MCP
- DeepEval vs Respan API + MCP
- Galileo API + MCP vs Gauge CLI
- Galileo API + MCP vs Plurai Simulation
- Gauge CLI vs Respan API + MCP
- Plurai Simulation vs Respan API + MCP
- Navige vs Respan API + MCP
Machine-readable
- This page as Markdown
/compare/galileo-vs-respan.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/galileo.json·/api/v1/tools/respan.json - From a terminal
anchor compare galileo respan(the CLI) - Over MCP
compare_tools {"a": "galileo", "b": "respan"}at/mcp, no key