An agent can connect on its own if it already holds X_THRUACT_TOKEN, X_THRUACT_TOKEN.Remote endpoint behind a static API key or header. The registry never sees the value; the agent fills the placeholder.
Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed. How it is computed.
Endpoints
remote
auth
reachable
uptime 30d
p50
protocol
last ok
https://thruact.com/mcpstreamable-http
api_key ${X_THRUACT_TOKEN}
yes
100%
296 ms
2025-06-18
2026-10-20
Tools (7)
thruact_act
Run a capability. Routes across providers and fails over automatically on provider faults. The reply's `route` says which providers were considered, what each scored, and why any were not used — including ones dropped for a missing credential.
thruact_call
Run one specific tool by id. No failover.
thruact_compare
Ask every provider behind a capability the same question at once and report where their answers differ. Use it when the answer matters enough to want it corroborated. Costs more than act: every provider called is paid.
thruact_discover
Find capabilities for a job, with prices and measured reliability. Search first, execute second.
thruact_iq
Measured reliability per tool over the last 7 days.
thruact_proxy
Send an authenticated request to a third-party vendor the workspace has connected. The stored API key is injected server-side — you never see it. Give the vendor id from the directory (e.g. openai, sendgrid), an HTTP method, and a path on that vendor's own API. Use it to act through a connected vendor that is not a Thruact capability. Metered per call.