SERVICE SELECTION
Choosing Hypit models and API services: Agents, HypiHub and BYOK
Separate Agents, models, Providers and Endpoints. Choose local or hosted capabilities for images, video, voice and transcription using a practical connection checklist.
Edited by HypitAI · Reviewed
Separate planning from material generation
An Agent interprets the brief, edits project files and runs the workflow. Image, video, voice and transcription services supply material capabilities. Choosing an Agent does not automatically select those services. This guide describes official Hypit; this site supplies no API keys, model gateway or generation endpoint.
Four concepts to identify
The same model name can appear behind different service APIs. A connection depends on the full protocol and supported capability.
| Concept | Responsibility | Check |
|---|---|---|
| Agent | Plan and operate the project | File access, execution and delivery |
| Model | Generation request and output | Input types, parameters and output |
| Provider | Map requests to a service API | Protocol, status and collection |
| Endpoint | Configure a Provider instance | Address, credential reference and capacity |
Start with the missing material
List what each shot needs before connecting services. A simple project does not need every available capability.
| Available material | Missing capability | First check |
|---|---|---|
| Real product footage | Assembly, captions and export | Whether new video generation is needed |
| Product images only | Image processing or new video | Supported input and aspect ratio |
| Spoken reference | Words and timing alignment | Local or hosted WhisperX readiness |
| A new voice requirement | Speech material | Language, pronunciation and reference suitability |
HypiHub, local capabilities and your own service
Official documentation recommends HypiHub as an integrated hosted option for supported generation and WhisperX work. Local Providers handle corresponding local work. Another service can use a compatible installed Provider or a project adapter written by the Agent. Different capabilities can use different services.
A key does not implement an API
BYOK authorizes the issuing service; it does not translate request formats. Supply the service name, official API documentation, intended model, input constraints and output requirements. Even the same model can have different limits across services. Keep credentials out of public examples and source files.
Existing service: [name]
Official API documentation: [link]
Task: [image / video / voice / transcription]
Inputs and specifications: [details]
Output: [type, aspect ratio, language]
Check for a compatible Provider in this project. List reusable capabilities, missing adapters and information I must supply.Connect files and previews in a remote environment
The Agent needs project access, tool execution and a delivery path. With a remote Agent, upload or connect material to its workspace, use preview forwarding and collect downloadable results. Record where files persist after the session. A browser interface alone does not establish runtime readiness.
Check the selected capability
A successful login does not verify the intended workflow. These are diagnostic steps; no live service call was performed for this guide.
- Confirm the intended Provider and Endpoint.
- Check that the service accepts the input and parameters.
- Verify required local tools are available.
- Retain traceable task and output records.
- Inspect the actual downloadable, playable result against the brief.