Providers · Available

Use Amazon Bedrock without opening an unbounded provider account.

Native Converse integration with a reviewed catalog of U.S. conversational models, settled-prepaid eligibility, reusable card or Stripe Link authorization, conservative reservation, and usage reconciliation. Model availability is checked before it appears in the customer catalog.

Start in a test environment Read current API behavior

How the connection works

Provider access stays separate from application control.

Publish only reviewed models

The customer catalog is not a mirror of every Bedrock model. A model appears only after its region, Converse support, output limit, price source, effective date, and verification time pass the managed-catalog checks.

Reserve exposure before the call

The gateway reserves a conservative maximum charge against settled credit before submitting a request, then settles the exact normalized token usage afterward. An exhausted balance stops at the gateway instead of becoming an AWS bill for the customer or the company.

Keep each request in its tenant boundary

The authenticated organization, workload, route, request ID, budget, and receipt stay tenant-scoped. The managed adapter translates each request independently to Bedrock Converse and does not add a shared conversation or cross-customer memory layer.

Current shared controls

Status determines what can be configured.

Write-only, encrypted BYOK for implemented provider connections Stable model aliases and protocol-eligible route targets Organization and key budgets, RPM, TPM, and concurrency hard limits Observe, Shadow, Enforce, reason codes, and metadata-only evidence

Beta connections require customer validation against the exact model, payload, streaming mode, region, and provider account before production use.

Client boundary

AIGHQ_BASE_URL=https://api.aigatewayhq.com/v1
AIGHQ_API_KEY=from-your-workspace
AIGHQ_MODEL=company-approved-fast

Applications keep a stable gateway URL and model alias while an administrator changes eligible provider accounts and models.

Implemented boundary

Only documented protocols become eligible.

Fund a settled prepaid balance, keep a reusable payment authorization on file, choose an eligible model from the reviewed catalog, and bind it to a workload route with an explicit budget. Customers do not supply an AWS credential for this managed path.

POST /v1/responses through Bedrock Converse POST /v1/chat/completions with stream=false POST /v1/messages with stream=false

Compatibility is bounded to the provider's current published interface. Review the provider documentation before approving a production model.