Explorer
The ORGN Scanner homepage — a live visual grid of Gateway inference activity, aggregate stats, and recent request blocks.
ORGN Scanner is not Studio Code Security (Shannon). Scanner audits Gateway inference attestation and confidential compute sandboxes — it does not scan your repository for CWE vulnerabilities. For code security assessments, see Code Security.
The Explorer is the ORGN Scanner homepage. Open scanner.orgn.com (or dev.scanner.orgn.com in development) and you land directly on it — there is no separate /explorer route.
The Explorer is a high-level audit view: a visual grid of recent inference activity backed by live Gateway spend-log aggregations. Use it to spot volume trends, attestation health, and provider distribution before drilling into individual requests.
What the Explorer shows
Activity grid
Each block in the grid represents a batch of recent inference requests. Within a block, individual cells map to request IDs:
- Color and status icons indicate success, pending attestation, failure, or cancellation
- Model ID and token count appear on hover or selection
- Click any cell to open the request detail page at
/request/:requestId
The grid refreshes from the Gateway attestation pipeline. Pending attestation states resolve to Verified or Failed as receipts arrive from NEAR AI and Phala TEE providers.
Aggregate stats
Header panels summarize platform-wide activity:
| Metric | Description |
|---|---|
| Total requests | All-time inference count |
| Requests (24h / 30d) | Rolling window volume |
| Total tokens | Prompt + completion tokens across all requests |
| Total spend | Aggregate cost in USD |
| Avg latency / TTFT | Mean end-to-end and time-to-first-token |
| Active models | Distinct models with recent traffic |
| Providers | Active provider list (NEAR, Phala, Vercel) |
Top applications and models
Side panels rank the most active clients and models:
- Top apps — which application tags sent the most requests (curl, VS Code, Studio, Postman, etc.)
- Top models — request volume per model ID, with TEE and ZDR badges
- All models / all applications — full dropdown source lists used by the Messages filter bar
Running sandboxes
When Daytona is configured, the Explorer also surfaces a count of active confidential compute sandboxes. Click through to Sandboxes for environment-level TDX attestation.
Filtering from the Explorer
The Explorer grid itself is a live snapshot, but navigation links connect to deeper views:
- Messages (
/messages) — full searchable, paginated request list with status, model, creator, and application filters - Models (
/models) — per-model usage breakdowns and recent request history - Sandboxes (
/sandboxes) — TDX sandbox inventory and attestation status
For a guided walkthrough, see the Scanner Quickstart.
Public access
The Explorer requires no authentication. Anyone can open the homepage and inspect aggregate activity and individual request metadata.
Optional id-orgn SSO (via the sign-in button) unlocks role-aware features such as scoped visibility for internal operators. Signing in is not required for attestation verification.
Backend API
The Explorer homepage loads data from the Gateway internal console API. These endpoints are public (service-token gated on the server, not user-auth gated):
| Endpoint | Purpose |
|---|---|
GET /internal/console/explorer/overview | Aggregate stats, recent blocks, top apps/models |
GET /internal/console/explorer/messages | Paginated request list (also powers Messages) |
GET /internal/console/explorer/models | Model catalog with usage stats |
The overview response is cached server-side for 30 seconds to keep the homepage responsive under traffic spikes. Individual request drill-through at /request/:requestId is never cached.
Explorer vs Messages
Explorer (/) | Messages (/messages) | |
|---|---|---|
| Layout | Visual grid of recent blocks | Tabular, paginated feed |
| Best for | At-a-glance health checks, spotting anomalies | Searching, filtering, audit exports |
| Pagination | Recent window only | Full history with page controls |
| Filters | None on the grid itself | Status, model, creator, application, search |
Start on the Explorer for orientation. Switch to Messages when you need to find a specific request ID or filter by model.
Next steps
- Messages — search and filter the full request history
- Request details — field reference for
/request/:requestId - Verify a request — validate attestation receipts independently