Hi - I answer from the OpenSmartRoute documentation: routing, the API, plans and quotas, self-hosting. Ask away, or open a support ticket if you need a person.
Grounded in the docs - follow a source before acting on it.
dark-web-monitoring - Skill - OpenSmartRoute
Skillv1.0.0
dark-web-monitoring
description: Monitor dark web sources for leaked credentials, stolen data, threat actor communications, and emerging threats. globs: *.txt,*.csv,*.json --- - Access Tor hidden services via SOCKS5 prox
Alert immediately on: org credentials, access for sale, internal source code, executive PII, zero-days affecting tech stack
Maintain chain of custody: timestamped screenshots, full HTML preservation, source URL, file hashes, timeline
Never engage directly with threat actors unless authorized
Use separate infrastructure for dark web access (never corporate networks)
Verify claims before escalating — many dumps repackage older breaches
Cross-reference samples to confirm actual org impact
Use it
Copy one of these into your project. Installing also returns the manifest and these snippets.
# after Install: the listing is in your workspace's routing pool - a plan picks it for its slot
curl -s -X POST https://api.opensmartroute.ai/api/v1/route -H 'Authorization: Bearer $OSR_API_KEY' -H 'Content-Type: application/json' -d '{"text": "...", "plan": true}'
Manifest
An Open Capability Manifest: the router reads it to know what this does, what it costs and when to pick it.