Solutions Overview
Use this page when you want to route a reader to the right public Keeptrusts workflow without sending them into unrelated integration detail. Start with the job you need to complete now; use the linked references only when the workflow asks for a specific field, command, or contract.
Choose your path
| Outcome | Start here | Then go deeper into |
|---|---|---|
| Get a governed gateway running | Quickstart | Install the Gateway, CLI Overview |
| Roll out a config-led operating model | Config-First Workflow | Configurations, Declarative Config Reference |
| Standardize shared provider access | Unified Access | Managing API Tokens, Unified Access Budgets |
| Control cost and access | Spend, Budgets, and Billing | API Token Management, kt spend |
| Investigate blocked or escalated traffic | Investigate a Blocked Request | Resolve an Escalation, Debugging Requests |
| Produce review evidence | Export Evidence for a Review | kt export-jobs, Reviewing Alerts and Evidence |
Know when the outcome is complete
| Outcome | Verification checkpoint |
|---|---|
| Governed gateway running | /healthz succeeds and an authenticated request reaches a configured model through the gateway |
| Configuration rolled out | The config lints, its pack tests pass, and the intended configuration is the one applied to the target gateway |
| Shared provider access ready | The client uses a scoped API token, the intended endpoint accepts the request, and current wallet or provider-readiness limits are understood |
| Block or escalation investigated | The record has a request ID, decisive policy or routing result, configuration context, and a named next action |
| Evidence package ready | The export job completed, the downloaded file covers the intended time window, and the handoff includes the relevant request or escalation IDs |
Process health, schema validity, policy simulation, and a successful model request prove different things. Do not treat one checkpoint as a substitute for the others.
Combine paths intentionally
- Use an integration guide after the gateway and credential boundaries are understood; provider setup does not replace the core quickstart.
- Pair configuration rollout with the investigation workflow so operators know how to verify and reverse an unexpected change.
- Pair Unified Access with token and budget guidance. Stored access-policy and budget-policy simulations describe intended decisions, while their current live-enforcement limits remain documented in the Unified Access guides.
- Use the evidence workflow for a reviewable handoff, not as a substitute for diagnosing the underlying request.