Hydracept

Connections / BYOK

Bring your own provider keys. Hydracept encrypts credentials at rest and resolves them at execution time. You pay the provider directly—Hydracept adds no inference markup.

Hydracept API keys identify callers. Provider credentials pay for model inference. See Authentication & Activation for how those fit together.

After activation, open Configure BYOK on the completion page (or /v1/onboarding/byok?organizationId=…&projectId=…). Paste an OpenAI, ElevenLabs, or Meshy key — Hydracept encrypts and binds it in one step.

New Free orgs get a one-time smoke budget so python -m hydracept smoke can run before BYOK. All sustained generation requires your own provider keys.

Manual provider connection (API)

Connect providers through the organization-scoped public API:

  1. Create — POST /v1/organizations/{orgId}/provider-credentials stores the provider secret. Hydracept encrypts it at rest and validates the credential as part of create (there is no separate public validate route).
  2. Bind — POST /v1/organizations/{orgId}/provider-credentials/{credentialId}/bindings attaches the credential to the project/environment that may use it at execution time.

POST /v1/organizations/{orgId}/provider-credentials
Authorization: Bearer <HYDRACEPT_API_KEY>
Content-Type: application/json


POST /v1/organizations/{orgId}/provider-credentials/{credentialId}/bindings
Authorization: Bearer <HYDRACEPT_API_KEY>
Content-Type: application/json

Use the activation form, Studio, or the API with your Hydracept machine credential. Keep provider secrets off game clients.

Walkthrough: 5-minute game asset.

Automated bootstrap

Automated provider setup is not available yet. For now, connect credentials with the create → bind flow above.

Next