Recon
Follow the first signal. Review code and map the risk.
Purchase total shown at secure checkout
Match this code with your terminal, then connect.
Sign in below to connect this terminal.
An AI cyber operator for the work between a suspicious signal and a reproducible finding. Bring your code, your evidence, your next hard question.
One-time credit for new verified accounts. No card required.
Browser + Windows + macOS + Linux
One research workflow. Evidence at every step.
Reason across source, traces, and security boundaries.
Use owned targets, real tools, and negative controls.
Export the conversation and retain the evidence chain.
Start with a focused question. Follow the strongest signal. See the tool activity and the evidence behind the result.
Verified target ownership is required for hosted testing.
Checking Google sign-in…
Give Utah the objective and available evidence. It routes the mission to a cyber specialty, preserves context, and separates observations from proven impact.
Choose a cyber mission, or write your own objective below.
Your request is saved. Review your available usage, then retry when enough is available.
The request has not been sent to the model. Allocation is added only after a verified payment.
The five-phase crew executes tools, normalizes evidence, traces the strongest signals, designs focused verification, and writes a private evidence packet. Hosted execution requires a verified domain; local app and Apple research runs through utah.
Verify the domain, select a native tool or let the skill router choose, then run against the owned surface. Add source for static, dependency, configuration, and redacted secret analysis.
SERVER-VERIFIED RUNNER · SHA-256 —
Loading account billing…
Loading account billing…
For an existing payment question, with the receipt reference.
Credit purchases and adjustments in the latest 30 account events. This is a credit ledger, not a Stripe receipt or your complete payment history.
Follow the first signal. Review code and map the risk.
Go deeper. Connect the evidence and test your hypothesis.
Build the proof. Keep complex investigations moving.
Expand your reserve for sustained, demanding research.
One-time purchases. Every plan uses the same research capabilities. Zero Day adds its full allocation to your existing balance. Usage is measured from model input, output, and cached context. Confirmed payments add allocation; refreshing a success page cannot add credit.
Choose the speed, response length and conversation context for your Utah account. Connect your service accounts from Connectors.
Paste once in your terminal, then run utah inside any project folder. Your existing account connects automatically.
curl -fsSL https://aithatsee.com/install.sh | shirm https://aithatsee.com/install.ps1 | iexutahConnect your Cloudflare account to discover your websites, apps and data. Credentials are encrypted on the server. Create a scoped API token at Cloudflare API Tokens.
Choose read access only for resources you want to connect: Account, Workers Scripts, Pages, D1, Workers KV Storage, Workers R2 Storage, Zone and DNS. Missing permissions appear beside the affected service.
Utah supplies the models for chat, terminal and API requests. All model usage draws from your Utah allocation.
Testing sends one short request using your saved route. Your Utah allocation is billed normally.
Read DNS records, Pages deployments, KV values, R2 objects, and D1 query results from the connected account. Data responses are limited to 1 MiB.
The same saved routing applies to website, terminal, and API requests.
GET /api/configuration
PUT /api/configuration
POST /api/routing/resolve
GET /api/cloudflare/inventory
POST /api/cloudflare/resource
GET /v1/models
POST /v1/chat/completionsOne account. Your conversations, connected services, model routes, and terminal.
New verified accounts receive $10.00 of Utah usage credit once. No payment card is required.
Checking your account…Describe a question, attach source or logs, and choose a skill. The live activity view shows the selected route and work as it happens.
Utah supplies the models. Connect service accounts in Connectors and tune fast, balanced, and deep modes in Model settings.
Browser chats and drafts are saved to your account. Reopen them after signing in on another browser.
Choose a skill explicitly or let Utah select one from your request. Tool execution uses the target and permissions configured in Target & tools.
Your browser session is ready after sign-in. For files and commands on your machine, install Utah below, run utah in your project, then approve the code shown by the terminal.
Loading billing status…
Conversations and model configuration follow this account. Service credentials remain encrypted on the server.
One-time plans. Every research capability included. Choose your capacity, then track your remaining allocation as a percentage.
Follow the first signal. Review code and map the risk.
Go deeper. Connect the evidence and test your hypothesis.
Build the proof. Keep complex investigations moving.
Expand your reserve for sustained, demanding research.
Each purchase adds the selected plan’s full allocation. Percentages compare capacity with Recon; your workspace displays your remaining share of total lifetime allocation. Zero Day is a separate top-tier purchase, not a price difference or recurring charge. Actual consumption depends on input, output, and cached context. No automatic renewal. Existing credit is preserved.
Put the same research engine inside your scripts and workflows. Web, Windows terminal and API draw from one account allocation.
Sign in, open API access, then get your key. Set it in the UTAH_API_KEY environment variable for your process. Keep it on your machine or server; never put it in browser code.
$headers = @{ Authorization = "Bearer $env:UTAH_API_KEY" }
$body = @{
messages = @(@{
role = "user"
content = "Review my authentication checklist."
})
max_tokens = 1024
} | ConvertTo-Json -Depth 5
Invoke-RestMethod -Method Post `
-Uri "https://aithatsee.com/v1/chat/completions" `
-Headers $headers -ContentType "application/json" -Body $bodyThe response includes the answer and an utah_usage.allocation percentage receipt. API usage follows the existing token meter; longer input and output consume more allocation. A request with insufficient allocation returns HTTP 402 before inference. Choose any plan above to add capacity.
Open any authorized project folder and run Utah. Sign in in your browser once—no API key to copy. Describe a cyber mission, or type /bounty for Apple research.
Windows 10/11 · Python included
macOS & Linux · Python 3.9+
██╗ ██╗████████╗ █████╗ ██╗ ██╗ ██║ ██║╚══██╔══╝██╔══██╗██║ ██║ ██║ ██║ ██║ ███████║███████║ ██║ ██║ ██║ ██╔══██║██╔══██║ ╚██████╔╝ ██║ ██║ ██║██║ ██║ ╚═════╝ ╚═╝ ╚═╝ ╚═╝╚═╝ ╚═╝ PS C:\research> utah Review auth.py for missing ownership checks. Read evidence → trace the boundary → verify the fix utah ›
utahPaste this once. Then open a new terminal and type utah.
Windows PowerShell
irm https://aithatsee.com/install.ps1 | iexmacOS / Linux
curl -fsSL https://aithatsee.com/install.sh | shVerified identity. Ownership checks before hosted testing. A private, metered workspace with explicit data boundaries.
Read the security overview ↗SOC 2 and ISO 27001 readiness are ongoing organizational work, not current certifications. Protected health information is not accepted. HIPAA use requires executed BAAs and an approved operating environment.
Your AI workspace
Chat, build and investigate.
Your workspace starts with you.
Welcome back. Your conversations are waiting.
By continuing, you agree to the Terms and Privacy policy.
Reopen this guide from Introduction in your workspace.