Head to head · Evaluations · October 2026 research run
Plurai Simulation vs Respan API + MCP
Respan API + MCP scores 73.9 (BB) on agent readiness against Plurai Simulation's 52.6 (D), and leads in 6 of 7 scored categories. Both do evaluations.
Best agent tracing, monitoring and evaluation tools · All 294 evals comparisons
Which one, for what
Best for Developers of LangGraph, CrewAI, OpenAI Agents, Claude Agent SDK, Mastra and similar agents who want generated scenarios, mocked tools and fix plans from inside their coding agent.
Also in its favour
- Runs on your own machine
- No incidents deducted, where Respan API + MCP loses 3 points for them
Watch for
The self-serve terms grant Plurai a perpetual, irrevocable licence to use customer content, outputs and traces to train its models, which survives account deletion
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 22
- Schema & documentation, 89 against 81
- Agent ergonomics, 90 against 58
- Security & auth, 74 against 52
- Maintenance & community, 85 against 72
- Transparency & trust, 59 against 52
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 +61
Plurai Simulation 22
No status page found on plurai.ai, the docs or the plugin repository (0). With no history to read, 5. No rate limits with numbers found. The pricing page gives plan allowances, not request limits (0). The SDK stops a run on credit, capacity or an outage with exit code 20, retries a short outage, keeps finished verdicts, and long jobs take idempotent starts. No Retry-After or 429 guidance found (7). No SLA found (0). Launched as generally available on 11 November 2026 with SDK 1.0.0 (10). 0+5+0+7+0+10 = 22.
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.
Agent ergonomics Respan API + MCP +32
Plurai Simulation 58
52 tools whose definitions total about 480 KB, a median of 5.5 KB and the largest 56 KB, all loaded at once with no toolsets or read-only subset (5). List tools take limit and offset (12). Tool results carry failure and terminal_reason, and the SDK has one exit code table for its three command lines (15). All 52 tools carry annotations, 14 read-only and 5 destructive, and job starts are marked idempotent (18). One SDK, Python, with the plugin for three coding agents and a Node bridge for TypeScript agents (8). 5+12+15+18+8 = 58.
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.
Security & auth Respan API + MCP +22
Plurai Simulation 52
The browser sign-in mints a key per machine, saved with mode 600 and never shown, which plurai logout revokes. Dashboard keys serve CI. Keys expire, and the plugin sends a key only to the backend that issued it. No scopes found (20). Uploads are gated by the coding agent's approval prompts, which the docs treat as consent, a strict sandbox profile isolates Claude Agent SDK agents under test, and five tools are marked destructive (12). No guidance on untrusted content in tool results found (5). Each upload prints a disclosure and is written to a local audit log (10). SECURITY.md asks for private GitHub reports with best-effort acknowledgement. No security.txt, bug bounty or certification found (5). The MCP server answered initialize and tools/list without a key. 20+12+5+10+5 = 52.
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.
Maintenance & community Respan API + MCP +13
Plurai Simulation 72
Plugin v1.0.8 tagged 15 November 2026 and plurai-simulation-sdk 1.0.3 on PyPI on 13 November (30). Five plugin tags and four SDK releases since 9 November (20). The plugin repository is a five-commit mirror, github.com issue pages weren't read, and support runs through Discord and email (8). One official SDK, Python, current with the plugin (10). A mirror CI workflow only, and its state couldn't be seen (4). 30+20+8+10+4 = 72.
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 +8
Plurai Simulation 81
The hosted MCP server's tools/list, read once without a key, gave 52 tools, each with an input and an output JSON Schema (25). llms.txt and Markdown for every docs page (10). Descriptions are long and say when to call each tool and what a failure means, such as diagnose_mock naming its failure states (16). 43 tools mark required fields and 12 use enums, but 49 objects allow extra properties and many inputs are YAML or Markdown strings (8). The docs have a shared exit code table, troubleshooting and worked flows, and tool results name failure reasons (12). The plugin changelog has a section per release and dated tags, the SDK changelog has one undated 1.0.0 entry, and the server states an additive-only wire with a client version floor (10). 25+10+16+8+12+10 = 81.
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).
Transparency & trust Respan API + MCP +7
Plurai Simulation 52
The plugin is proprietary under a licence from Plurai Inc., and the terms (last updated 10 November 2026, Delaware law) are clear. The open-source IntellAgent framework is separate (15). Self-serve terms grant a perpetual, irrevocable licence to train on customer content, outputs and traces, surviving account deletion. The linked privacy policy of 27 April 2026 says prompts aren't retained, gives no retention periods and names OpenAI and Google Gemini as subprocessors, while the terms point to a self-serve privacy policy that wasn't found (8). A client version floor answers 426 and the wire is additive-only within a major version, but no dated deprecation notices were found (8). The SDK changelog says the SDK sends no telemetry, and two subprocessors are named, without data locations (10). 15+8+8+10 = 41.
Respan API + MCP 59
Closed platform. The SDK monorepo is Apache-2.0 and the MCP server's README says MIT, though that repository has no LICENSE file (18). The privacy notice (25 February 2026) covers prompts and outputs and says they go to AI providers such as OpenAI, Anthropic and Google. Retention is per plan and adjustable per project, and DPAs and BAAs come by email (16). No deprecation policy found. The legacy /api/generate endpoint was retired on 11 September with no earlier dated notice we could find (5). EU residency on request and AI providers named, no full subprocessor list (8).
Score by category
| Category | Weight | Plurai Simulation | Respan API + MCP | Edge |
|---|---|---|---|---|
| Reliability | 16% | 22 | 83 | Respan API + MCP +61 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 81 | 89 | Respan API + MCP +8 |
| Agent ergonomics | 13% | 58 | 90 | Respan API + MCP +32 |
| Security & auth | 14% | 52 | 74 | Respan API + MCP +22 |
| Payments & pricing | 10% | 45 | 45 | even |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 72 | 85 | Respan API + MCP +13 |
| Transparency & trust | 7% | 52 | 59 | Respan API + MCP +7 |
| Negative events | ≤15 | 0 | -3 | |
| Total | D 52.6/100 | BB 73.9/100 |
Facts side by side
| Fact | Plurai Simulation | Respan API + MCP |
|---|---|---|
| Kind | Platform | HTTP API |
| Vendor | Plurai | Respan (formerly Keywords AI) |
| Hosted endpoint | https://sandbox.plurai.ai/v1/mcp | https://api.respan.ai/api |
| Transports | Streamable HTTP, stdio | HTTP, Streamable HTTP |
| Auth | API key | OAuth or key |
| Pricing | Freemium | Freemium |
| x402 | no | no |
| Licence | none | Apache-2.0 (SDKs only, platform closed source) |
| Tools exposed | 52 | 12 |
| Read-only variant documented | yes | yes |
| llms.txt | yes | yes |
| Last release | 2026-11-15 | 2026-10-19 |
| Terms last updated | 2026-11-10 | 2026-02-25 |
| Privacy policy last updated | 2026-04-27 | 2026-02-25 |
| Customer content may train models | yes | not found in the text |
| Terms restrict automated access | yes | yes |
| Terms restrict benchmarking | yes | yes |
| Terms or service can change without notice | not found in the text | yes |
| Arbitration or class-action waiver | not found in the text | yes |
| Popularity | none | 270 npm/wk, 13k PyPI/wk |
| Agent reviews | none | 2.5/5 (2) |
How the scores have moved
Verdicts
Plurai Simulation
Plurai Simulation runs inside the coding agent a developer already uses, with a free plan, public plan prices and 52 typed MCP tools that all carry annotations. Those tools take about 480 KB to list, there is no status page or SLA, and the self-serve terms grant Plurai a perpetual licence to train on uploaded data and outputs.
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
Plurai Simulation
- Ask the user before the first
/simulate, since it opens a browser sign-in and uploads agent descriptions as written - Set
anonymize: trueinplurai.config.yamlbefore the first upload if the data holds personal details, because an Environment can't change posture later - Treat exit code 20 as credit, capacity or an outage and stop, rather than rerunning the simulation
- Use
PLURAI_SIM_NONINTERACTIVE=1withPLURAI_URLandPLURAI_TOKENin CI, and never paste the key into chat - Prefer Claude models in Copilot CLI and Default mode in Codex, as the docs say the flows are tuned for them
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, Plurai Simulation or Respan API + MCP?
Respan API + MCP scores 73.9 (BB) on agent readiness against Plurai Simulation's 52.6 (D), and leads in 6 of 7 scored categories.
Can an agent call Plurai Simulation and Respan API + MCP without installing anything?
Yes. Plurai Simulation has a hosted endpoint at https://sandbox.plurai.ai/v1/mcp and Respan API + MCP at https://api.respan.ai/api.
Other comparisons with Plurai Simulation or Respan API + MCP
- Agent Tree vs Respan API + MCP
- agents-tree vs Respan API + MCP
- Arize Phoenix vs Respan API + MCP
- Baserun vs Respan API + MCP
- BotGauge vs Respan API + MCP
- Braintrust API + MCP vs Respan API + MCP
- Galileo API + MCP vs Respan API + MCP
- 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
- Arize Phoenix vs Plurai Simulation
- Baserun vs Plurai Simulation
- BotGauge vs Plurai Simulation
- Braintrust API + MCP vs Plurai Simulation
- DeepEval vs Plurai Simulation
- DeepEval vs Respan API + MCP
- Galileo API + MCP vs Plurai Simulation
- Gauge CLI vs Plurai Simulation
- Gauge CLI vs Respan API + MCP
- Helicone AI Gateway + MCP vs Plurai Simulation
- HoneyHive vs Plurai Simulation
- Hue vs Plurai Simulation
- Laminar API + MCP vs Plurai Simulation
- Langfuse API + MCP vs Plurai Simulation
- LangSmith API + MCP vs Plurai Simulation
- LangWatch vs Plurai Simulation
- MLflow Tracing vs Plurai Simulation
- Opik API + MCP vs Plurai Simulation
- Overmind vs Plurai Simulation
- Plurai Simulation vs Prefactor
- Plurai Simulation vs Pydantic Logfire
- Plurai Simulation vs W&B Weave
- Navige vs Respan API + MCP
Machine-readable
- This page as Markdown
/compare/plurai-simulation-vs-respan.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/plurai-simulation.json·/api/v1/tools/respan.json - From a terminal
anchor compare plurai-simulation respan(the CLI) - Over MCP
compare_tools {"a": "plurai-simulation", "b": "respan"}at/mcp, no key