Content governance
Apply observation or blocking modes, moderation policies and word lists; link findings to call attribution.
AIGW / Multi-tenant AI + API gatewayGovern every call. Understand every account.
Manage enterprise model and API calls with identity verification, content moderation, usage aggregation, upstream routing, and audit records.
Content reviewed · v2.0.00
- Who it is for
- Enterprise and public-sector AI teams, platform operators, shared-compute partners and organizations opening APIs to internal or external consumers.
01 / Capabilities
Multi-tenant AI + API gateway
Verifiable identity
Distinguish caller-supplied labels from signed identities. Map verified identities to employees, departments and applications.
Usage and allocation
Inspect usage dimensions, organizational snapshots and locked periods. Keep AI Token accounts separate from API byte and latency records.
Capacity-aware routing
Manage model aliases, upstream pools and forwarding using capacity, health and routing policies.
API publishing
Govern HTTP access with published catalogs, subscriptions and policies, retaining access records and explanations.
Shared control and audit
Manage both data planes through one control plane with common identity, API keys, permissions and auditing.
02 / Workflow
How do you attribute shared AI usage?
When departments share an AI application, the upstream service often sees only one application key. AIGW brings identity and organization into the request governance flow and reports usage by user, department and application. Trusted attribution requires the signed identity contract. Caller-supplied user labels alone support statistical attribution, not verified identity.
- Connect applications and verified identities
- Check access, subscription and content policies
- Route to a model or HTTP service
- Record AI usage and API access separately
03 / Product screenshot
AIGW · Overview
04 / Deployment & scope
Deployment & scope
Private delivery is supported. AI and general API data planes share a control plane; general API features are off by default and enabled when needed. Agree on identity sources, upstreams, policies, metering and cluster needs.
Moderation depends on configured policies and services and cannot guarantee detection of every risk. General API governance does not replace every role of an existing gateway. Laboratory benchmarks do not establish customer production performance.
05 / FAQ
Questions & answers
AIGW
Does AIGW only proxy AI models?
No. v2.0.00 supports AI and general HTTP API governance. The general API data plane is disabled by default and enabled as needed.
Is a supplied username enough for trusted attribution?
No. Unsigned body fields and headers are caller assertions. Trusted attribution requires a verifiable signed identity and correct organizational mappings.
Do AI and general APIs use the same billing unit?
No. AI calls record Token usage; general APIs record bytes, latency and other access metrics. Allocation or monetary billing follows tenant configuration and delivery scope.
When is AIGW useful?
AIGW suits applications or tenants sharing model services and needing usage attribution through verified identities, centralized content policies, auditing and upstream routing. General HTTP API governance is enabled as needed.
Does AIGW orchestrate agents or manage MCP tools?
The AIGW described here governs model and HTTP API calls. It does not promise agent workflow orchestration or MCP tool lifecycle management. Tool calls and gateway integration depend on the actual integration design.
06 / Resources
Get resources
The product overview is in English and the brochures are English editions; product screenshots show the Chinese-language interface. Document versions may differ from web content; check the date and version.
HONGCHUANGDA TECHNOLOGY
Contact us
Three independent products, deployable separately. Cross-product integration is scoped per project.