Authenticating through Okta

Opening secure session

Brain

Enter the usage command deck.

Authorized operators only.

Opening secure session

Brain Gateway

Dashboard NOC View Rate Limits Route Access Key Retention User Access Support Emergency Revoke Server Integration User Integration

Dashboard

loading
Applications 0
Total hits 0
Allowed 0
Denied / failed 0
Integrity flags 0

Traffic Trend

Status Mix

Top 3 APIs

Top Customers

Attention

Customer Usage / Minute

Rule Pressure

Daily Smoke Tests

Route Integrity

Hits by API

Customers 0
Events 0
Allowed 0
Exceptions 0

Live API Flow Map

Capability coverage

Handoff

Microsoft authorization required

pending
Authorize Microsoft

URL
Customer credential
Instructions
Audit details
Internal Key Vault record
Key ID
Fingerprint
Application
Customer / department
User lease
Jira comment
APIs
Client handoff
Who is connected

User and server authorizations

See who authorized an integration, what it can reach, when it was last used, and when it expires. Open a record only when you need technical details or a revoke action.

A lease is the governed connection between one owner, one Brain key, and selected API routes.

Leases 0
Active 0
Users 0
Customers 0
Find an authorizationSearch and status filters

Traffic protection

How often each API key may call a route

Rate limits prevent accidental request floods. They control short bursts, sustained traffic, daily volume, and simultaneous calls without changing what data a route may access.

Missing means a route has no traffic policy attached and needs operator review.

Keys covered —
Routes covered —
Policies —
Need policy —
Find a key or policyCustomer, product, owner, and status filters

Waiting to load policy catalog

Customers near their limits

Open to review the busiest consumers

Edit traffic policies

Advanced operator controls

Policy catalog

Open a customer key to inspect route-level limits.

Credential hygiene

Find API keys that are no longer being used

Key retention tracks successful activity and identifies stale credentials that are eligible for revocation. Active use keeps a governed key current; failed requests do not.

Open a customer, then a key, only when you need its activity history or route list.

API keys —
Stale —
Active —
Auto revoked —
Review or filter keysSearch, status, and stale-key action

Waiting to load key retention

Emergency control

Immediately disable an entire application

This stops the application and its active API keys and sessions. Use Route Access for routine route changes; use this page only for compromise, decommissioning, or an urgent full shutdown.

High impact: revocation can interrupt every integration using the selected application.

Applications 0
Currently enabled 0
API keys 0
Sessions 0
Find an applicationSearch by customer, owner, or application ID

Least-privilege access

Choose which API routes each customer may call

Open a customer to see its routes. A checked route is allowed for that client; an unchecked route is blocked without disabling the rest of the application.

Use this for normal access changes. Use Emergency Revoke only when the entire application must stop.

Applications 0
Routes 0
Allowed 0
Blocked 0
Find a customer or routeSearch and access-state filters

Verified troubleshooting

Turn a Codex error into a Brain diagnostic receipt

Paste the error or handoff exactly as received. Brain extracts safe identifiers, checks its own audit journal, and tells you whether the issue is the caller, route, policy, resource, credential, or provider.

No changes are made. Brain never retries the provider call, reauthorizes a user, or widens a route from this page.

Support intake

Describe the failure

Checking access
1

Incident

Tell Brain what failed and where the failure occurred.

2

Diagnostic evidence

Only the fields relevant to the selected failure stage are shown.

Brain or provider response
Pre-Brain connection evidence
Additional context
Never paste credentials. Remove passwords, API keys, authorization headers, cookies, access tokens, and refresh tokens. Brain also redacts obvious credential patterns before analysis and does not retain the pasted text.
How Brain interprets it
  1. Assemble: turn the completed fields into one sanitized diagnostic report in this browser.
  2. Extract: read only known IDs, route aliases, HTTP statuses, and safe error codes.
  3. Verify: match the exact request against Brain's audit journal and route contract.
  4. Compare: show whether the pasted Codex conclusion agrees with Brain's recorded decision.
  5. Route support: name the responsible team and exact next action.

ChatGPT can interpret natural language before a request is made. This support portal does not ask AI to guess production state; Brain verifies every displayed operational fact.

Diagnostic receipt

Waiting for a report

Unverified

Request

Verification

Ownership and recovery

    Send back to Codex