Glimind // FAQ

The reliability layer for AI agents — answered. Also see docs, install, and privacy.

What is Glimind?

Glimind is the reliability layer for AI agents — a live, neutral, cross-ecosystem oracle that tells an agent whether any tool (MCP server or API) is working right now, how to call it correctly, and what to use instead if it's down. It is consumed per call over MCP, REST, or a drop-in SDK.

How does Glimind know if a tool is working?

Two sources. Breadth comes from safe liveness probes (the MCP initialize handshake + tools/list — never invoking a tool). Depth comes from privacy-clean outcomes of real calls that consenting agents report via the SDK or OpenTelemetry. Combining cross-ecosystem real usage with probes gives a live verdict no single-tenant tool can match.

Is Glimind free?

Yes — health checks, reliability scores, badges, discovery, and status pages are free with no signup. Premium reads (recipes, alternatives, prepare, alerts) run on metered credits with automatic overage. You can also "pay with data": reporting outcomes earns credits, so heavy contributors run premium for free.

Does Glimind see my data? Is it private?

Glimind never stores your arguments, tool outputs, prompts, or any payload. From telemetry it keeps only value-free structure and metadata: a salted hash of the input shape, a value-free output shape, success/failure, a normalized error class, latency, and coarse caller context. The ingest endpoint hard-rejects anything resembling a raw payload. Full detail at https://glimind.com/privacy.

How do I add Glimind to my agent?

Add the MCP endpoint https://glimind.com/mcp to any client (Claude, Cursor, Windsurf, VS Code), or install the SDK (npm i glimind / pip install glimind), or — if you already emit OpenTelemetry GenAI spans — point your OTLP traces exporter at https://glimind.com/v1/traces with no new SDK. Copy-paste config is at https://glimind.com/install.

What's the difference between Glimind and an MCP registry (Smithery, Glama, PulseMCP)?

Registries are catalogs: they tell you a tool exists. Glimind tells you whether it works right now, how to call it correctly, and what to use if it's down. Glimind uses registries as one discovery input and adds the live reliability layer on top.

What's the difference between Glimind and observability tools like LangSmith or Langfuse?

Observability tools show your own traces (single-tenant). They cannot tell you a tool is failing for everyone right now, or hand you a known-good call shape from others' usage. Glimind is cross-tenant by design — that's the one thing single-tenant tools structurally cannot be.

Does Glimind work with OpenTelemetry?

Yes. Glimind accepts OTLP/JSON at POST https://glimind.com/v1/traces and harvests GenAI execute_tool spans into payload-free reliability data — so any OTel-instrumented agent feeds Glimind with zero new SDK. See https://glimind.com/integrate/opentelemetry.

Which frameworks and clients does Glimind support?

MCP (any client — Claude, Cursor, Windsurf, VS Code), TypeScript and Python SDKs, Vercel AI SDK, LangChain (JS + Python), OpenAI Agents SDK, a zero-code local proxy, and OpenTelemetry. Gateways/routers can embed the reliability feed directly.

Can Glimind automatically fail over when a tool is down?

Yes. Wrap a call with the SDK using autoRoute and Glimind health-checks first and transparently fails over to a healthy alternative when the tool is down — so your agent keeps working through outages — while reporting the outcome (privacy-clean) automatically.