Edge APIChecking
Awaiting health response
Live edge diagnostics
Know what is configured.
Prove what answered.
One honest view of the source registry, the protected search worker, and the providers that actually return books, audiobooks, comics, manga, and torrent metadata.
— tracked connectors
— implemented adapters
Standard TorBox tier
Strict match or no result
System truth
Coverage at a glance
Registry counts describe capability. The answering-source count only changes after a real diagnostic search.
Source registry—
tracked connectors
Implemented—
search adapters, not live claims
Last diagnostic—
run a search for live proof
ProtectionChecking
bounded edge proxy
Source registry
Configured is not the same as answered
Check individual sources below. Each check records the query, time, latency, matching candidates, and failure reason. Matches do not prove download or playback.
Loading all source adapters…
Status model: “Implemented” means code exists. “On demand” means it runs only when a relevant search needs it. “Answered” means it returned at least one result in the most recent test.
Live query lab
Test the whole search path
Runs through the public Manager proxy using your real Standard-tier configuration. Nothing here invents source coverage.
Stress tests
Diagnostic complete
Search results
This browser
Recent diagnostics
Your completed tests will appear here.
Protected route
Manager → edge → sources
Browser→Manager proxy→Builder worker→Source lanes
Body limits, provider budgets, circuit breaking, and VPS failover stay enforced across the route.