Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Useful for AI agent developers, AI app teams, automation engineers, and platform engineers who need a self-hostable, multi-tenant, RBAC-audited gateway that exposes curated web access to Claude Code, Codex, Cursor, Windsurf, Cline, and Zed via a single MCP endpoint, an OpenAI-compatible REST surface, or a WebSocket/SSE event stream — with a 52-platform channel registry that already covers web, Git
Who should use it
Who should skip it
Skip oxbshw/Agent-Span unless the captured evidence suggests it solves a problem you are actively working on.
About this signal
oxbshw/Agent-Span is tracked by RepoRadar as a agent gateway in the AI Agents section. It was first seen on 2026-07-02 and last updated on 2026-07-02. The current verdict is 'try now' with a Gold tier and easy setup difficulty. The standout signals for oxbshw/Agent-Span are workflow potential (9.8) and practical usefulness (9.0), while maturity (6.5) trails — that balance shapes where it fits best. This page summarizes the evidence RepoRadar has captured from captured source metadata. The score, tier, risk label, and verdict on this page are never influenced by sponsorship, ads, or tips — they reflect only the usefulness, popularity, novelty, momentum, maturity, and evidence signals described in the RepoRadar methodology.
How this item is evaluated
RepoRadar assigned oxbshw/Agent-Span a composite score of 8.3 out of 10, placing it in the Gold tier. This score combines weighted sub-signals: usefulness (35%), novelty (18%), momentum (14%), maturity (10%), open-source/build quality (7%), evidence quality (6%), workflow potential (6%), and setup ease (4%). Popularity is tracked separately at 1.0 and never affects the composite score or tier. The risk label of 'conditional' reflects inherent user-impacting hazards, not generic novelty. Items with no risk flag may still require normal code review before production use.
Putting this into practice? Read How to vet an AI agent or MCP server before you wire it in for the checklist behind this score.
Risk explanation
Some Tier 1 channels (Twitter, Reddit, Bilibili, Xiaohongshu, Instagram, LinkedIn, Discord, Telegram, Spotify, Twitch, Scholar, Podcasts, OpenAI, Anthropic, Brave, Bing, Google, Notion, Slack, Flight) need a per-channel API key or cookie — keep the cookie file outside the agent's writable workspace and rotate cookies per the upstream platform's policy, otherwise session-cookie exfiltration to an LLM is an immediate compliance event on multi-user / multi-tenant workstations; The 52 channels are 'reader/search' only by design — AgentSpan is not a browser-automation agent (no click, no login, no form fill); use Browser-Use or Playwright for those workflows. The README's 'What AgentSpan is not' section is the canonical reference; The 2 MiB request-body cap and the global in-flight concurrency shedder can return 503s under bursty load — keep a higher-tier concurrency budget on the host (raise `AGENTSPAN_MAX_INFLIGHT` in `.env.example`) if you front the gateway with a fan-out agent that issues many parallel reads, and review the `x-trace-id` / audit event stream before promoting the gateway to multi-tenant production access.