Skip to content
CortexDocs

Gateway product tour

Connect providers, manage budgets and access, inspect usage, and investigate routing decisions and refusals.

Start with the task you need below. Each guide includes required permissions and a result check.

Connect a client

  • Use a cct_ personal capture token with the organization-issued Gateway URL.
  • Provider credentials stay on the managed path.
Gateway Overview and spend over timeOpen in Cortex

Generate your key and send the first request.

Connect a provider

  • Choose the upstream account, configure its endpoint and company key, then run Check API key on the saved row.
  • Test a new request after configuration reaches an enrolled device.
  • For shared Egress, ask your administrator to confirm the provider connection before testing a request.
Choose a provider preset from the Add connection dialogOpen in Cortex
Set the endpoint, company key and enabled state in Configure connectionOpen in Cortex

Configure or replace a provider credential.

Find teams and members

Review six teams, captured spend and saved daily capsOpen in Cortex
  • Start with the team list, open the member table, then review reporting relationships and Team membership.
  • Use Access & limits → Budgets to change a configured cap; reporting relationships do not grant budget-edit access.
Explore the Directory reporting tree with aligned managers and activityOpen in Cortex

Open Teams and hierarchy.

Manage budgets

  • Select a subject, daily cap, filters and threshold action.
  • Review configured records in the budget table. Test the affected path after checking the saved configuration.
Compare the saved $100 daily cap with the edited $150 capMobile preview. Enlarge for the full view.Open in Cortex
Confirm the saved $150 daily cap, threshold action and filtersMobile preview. Enlarge for the full view.Open in Cortex

Create a budget and verify its saved configuration.

Set rate limits

Create an organization requests-per-minute limit and confirm the RPM and active status.

Review organization RPM limits and active statusOpen in Cortex

Set an RPM limit and verify the affected path.

Restrict model and provider access

  • Add a scoped deny for a provider, exact model or both.
  • Review active and disabled rows.
  • To allow access again, disable the matching deny and check for other active matches before testing the request path.
Review deny rules by scope, provider, model and statusMobile preview. Enlarge for the full view.Open in Cortex

Create a deny or restore access.

Inspect usage and spend

Select a reporting range and filters, then compare captured activity and estimated spend within that population.

Filter members by team, type, status and reporting windowOpen in Cortex

Filter usage and investigate spend.

Understand routing decisions

  • Inspect Turns for captured session context and Traces for the requested model and recorded routed target.
  • Check application state and any linked response separately.
Review routed sessions with captured prompt context and priced routing summariesOpen in Cortex

Inspect routing recommendations and application state.

Troubleshoot refusals

Start with the client status, then inspect the matching control and available denial evidence.

Compare recent rate-limit denial counts with their configured limitsMobile preview. Enlarge for the full view.Open in Cortex

Find the matching control and verify a new request.