toran.dev is built with Next.js, hosted on AWS behind Cloudflare. It measures traffic with Google Analytics and Google Tag Manager.
| Technology | Version | First seen |
|---|---|---|
| JavaScript Frameworks & Libraries2 | ||
| 16.1.1 | 9 Nov 2026 | |
| – | 9 Nov 2026 | |
| Frontend Build Tools & CSS2 | ||
| – | 9 Nov 2026 | |
| Web Servers, Languages & Backend Frameworks1 | ||
| CDN & Hosting3 | ||
| – | 9 Nov 2026 | |
| Analytics & Tag Management2 | ||
| – | 9 Nov 2026 | |
| Fonts & Icon Fonts1 | ||
| – | 9 Nov 2026 | |
The crew hasn’t read this site’s colors yet. We read a palette when we capture a site’s screenshot, busiest sites first. Meanwhile, browse palettes from other sites.
Counted from every stack change we've recorded: of the sites we watched running one of this site's tools, how many went on to add another. A pattern across sites, not a forecast for this one.
elliott.ns.cloudflare.comthea.ns.cloudflare.comUser-agent: * Allow: / Sitemap: https://toran.sh/sitemap.xml
# toran > See your outbound API calls live. toran is a read-only API inspector for debugging integrations and AI agents. It works by swapping your API base URL to route requests through toran, which logs the request and response before forwarding to the upstream API. ## What toran does - Captures outbound HTTP requests and responses in real time - Shows timing metrics (DNS, TCP, TLS, TTFB, transfer time) - Works with servers, CI pipelines, containers, and AI agents - Requires only a base URL swap—no SDKs, agents, or code changes - Read-only by design: no retries, caching, or mutation ## How it works 1. Create a toran at https://toran.sh/try 2. Get a unique toran Base URL like `https://abc123.toran.sh` 3. Replace your API base URL with the toran URL 4. Watch requests flow through in the dashboard Example: ``` # Before curl https://api.openai.com/v1/chat/completions # After (through toran) curl https://abc123.toran.sh/v1/chat/completions ``` ## Use cases - Debugging AI agent API calls to LLMs and tools - Inspecting webhook payloads and third-party integrations - Troubleshooting CI/CD pipeline API failures - Understanding exactly what your serverless functions send ## Key pages - Homepage: https://toran.sh - Try it free: https://toran.sh/try - Use cases: https://toran.sh/use-cases - Pricing: https://toran.sh/pricing - Comparisons: https://toran.sh/vs - Learn: https://toran.sh/learn - Changelog: https://toran.sh/changelog ## Comparisons toran vs desktop proxies (Charles, Proxyman, mitmproxy, Fiddler): - Desktop proxies require local installation and certificate setup - toran works with remote servers, CI, and containers via URL swap toran vs request capture (RequestBin, Webhook.site): - Request capture tools only see inbound requests - toran captures outbound requests from your application toran vs API clients (Postman, Insomnia, curl): - API clients are for manual request reproduction - toran shows real requests from your running application toran vs observability (Datadog, New Relic, OpenTelemetry): - Observability tools provide metrics, traces, and alerts - toran shows wire-level HTTP request/response details ## Privacy and security - Sensitive headers (Authorization, API keys) are redacted by default - Response bodies are opt-in and size-limited - Binary bodies are never stored - Data retention configurable per plan ## Contact Website: https://toran.sh
| – |
| 9 Nov 2026 |
| – |
| 9 Nov 2026 |
| – |
| 9 Nov 2026 |
| – | 9 Nov 2026 |
| – |
| 9 Nov 2026 |