The Console
The Console, at console.hips.com, is where you work with HIPS as a person: sign in, choose a workspace, make API keys, try models in the Playground, import and deploy your own models, read usage and spend, pay, and set the workspace's policies. A request itself goes to the API at https://ai.hips.com/v1 with a key; the Console is for everything around it.
| Screen | What it is for | Guide |
|---|---|---|
| Overview | What is spending, what needs attention and what to do next: the last 14 days, recent activity, active deployments and the first-request guidance | This page |
| Models | Every model this workspace can call, its supply under your requirements, and a path straight into the Playground | Models and Network & capacity |
| Playground | Try a model or a ready deployment with a realistic input, billed to the workspace | Playground |
| My models and deployments | Import a model from a model hub, deploy it, and pin catalog models to always-on capacity | Deployments and imports |
| API keys | The workspace's credentials for servers and SDKs, with their defaults and limits | API keys |
| Usage and activity | Units and money per request, model and day, with the export | Usage and activity |
| Billing | The plan, the balance, top-ups, budgets and alerts, receipts | Billing and credits |
| Workspace settings | The name, the team, the policies, the tool defaults, notifications, model-hub tokens, pause and delete | Workspace settings |
| Network & capacity | The supply the network publishes, per pool, and the always-on configurations | Models and Network & capacity |
| Account | You, not the workspace: how you sign in, where you are signed in, your Country, the tools you signed in | Your account |
- Screen
- Overview
- What it is for
- What is spending, what needs attention and what to do next: the last 14 days, recent activity, active deployments and the first-request guidance
- Guide
- This page
- Screen
- Models
- What it is for
- Every model this workspace can call, its supply under your requirements, and a path straight into the Playground
- Screen
- Playground
- What it is for
- Try a model or a ready deployment with a realistic input, billed to the workspace
- Guide
- Playground
- Screen
- My models and deployments
- What it is for
- Import a model from a model hub, deploy it, and pin catalog models to always-on capacity
- Screen
- API keys
- What it is for
- The workspace's credentials for servers and SDKs, with their defaults and limits
- Guide
- API keys
- Screen
- Usage and activity
- What it is for
- Units and money per request, model and day, with the export
- Guide
- Usage and activity
- Screen
- Billing
- What it is for
- The plan, the balance, top-ups, budgets and alerts, receipts
- Guide
- Billing and credits
- Screen
- Workspace settings
- What it is for
- The name, the team, the policies, the tool defaults, notifications, model-hub tokens, pause and delete
- Guide
- Workspace settings
- Screen
- Network & capacity
- What it is for
- The supply the network publishes, per pool, and the always-on configurations
- Screen
- Account
- What it is for
- You, not the workspace: how you sign in, where you are signed in, your Country, the tools you signed in
- Guide
- Your account
The rail shows Knowledge, Guardrails and Router too while the platform serves each of them. The workspace switcher at the top changes the workspace every screen reads, and switches between the Inference side and the Provider side, where GPU owners see My GPUs and their earnings (the provider Console).
Every member of a workspace holds one role. A control your role may not use is shown, with the reason beside it, so you know whom to ask.
| Role | What it may change |
|---|---|
| Owner | Everything, including deleting the workspace and transferring ownership |
| Admin | Keys, deployments, members, billing, settings and budgets |
| Developer | Keys, the Playground, deployments and key defaults |
| Billing | Top-ups, the plan, payment methods, budgets and alerts |
- Role
- Owner
- What it may change
- Everything, including deleting the workspace and transferring ownership
- Role
- Admin
- What it may change
- Keys, deployments, members, billing, settings and budgets
- Role
- Developer
- What it may change
- Keys, the Playground, deployments and key defaults
- Role
- Billing
- What it may change
- Top-ups, the plan, payment methods, budgets and alerts
Every member reads what applies to the workspace; the audit log is read by owners and admins. Workspaces and members has how roles are given and changed.
Overview's first-request guidance follows the Quickstart, each step linking to its screen:
- 01
Create a HIPS API key in the Console and store it as
HIPS_API_KEY. - 02
Set
HIPS_BASE_URLto the API root,https://ai.hips.com/v1. - 03
Set
HIPS_MODELto a supported model or deployment identifier. - 04
Send a small request using the example for your language.
- 05
Check the result, usage, and applicable charge before expanding the workload.
A screen that cannot reach the platform says so with the platform's sentence and a request id to quote to support, and never shows an empty list made from an error. Offline, readings stand as of their last read, nothing can be changed, and the Console reconnects by itself.
Related sheets
- Sheet
- 11 of 19
- Updated
- 2026-11-11