DCAIMSP & partner guide#
Use DCAI Model Gateway as part of a managed AI service: connect a supported provider, isolate usage by key, apply token budgets and export usage for customer reporting. Partner Edition is offered through a private offer; discuss the commercial and technical scope before onboarding customers.
Request a partner discussion · Compare plans and estimate charges
Choose a customer boundary#
Decide whether customers will have separate subscriptions and provider connections or share a configuration under your management. A separate gateway key provides its own counters and budget; it does not by itself establish a separate provider account, administrative security boundary, legal tenant or dedicated infrastructure.
Keep an internal mapping of customer, subscription, provider, deployment, key label, budget and billing contact. Avoid placing customer secrets or identifiers in a public repository. Confirm the arrangement with DCAI before relying on shared infrastructure for contractual isolation requirements.
Design your service package#
| Responsibility | Plan it before launch |
|---|---|
| Gateway subscription | Who purchases it, administers keys and receives Marketplace charges? |
| Provider account | Who owns the Foundry resource or Vertex project, grants access and pays inference charges? |
| Customer service | Who handles onboarding, first-line support, model configuration and incident communication? |
| Reporting | Who reconciles usage CSV, active-key counts, billing periods and customer invoices? |
| Rights and terms | Which written agreement permits resale, managed-service use, branding and any sublicensing? |
Price your own implementation and ongoing service explicitly. A customer may need more than one active key. Account for the $15 additional-active-key charge after your plan allowance, gateway token overages, provider usage, your support work and any Marketplace fees applicable to your own offer.
Onboard and operate#
- Agree on provider ownership, data requirements, supported endpoints and expected usage.
- Obtain the appropriate subscription or private offer and document the support arrangement.
- Connect and test the provider; verify model mapping and billing tier.
- Create keys, set token budgets and deliver secrets through your approved secure channel.
- Validate the customer's actual integration and follow the production checklist.
- Export usage CSV and reconcile charges for an initial billing period before scaling to more customers.
The current console provides usage CSV exports. Automated invoicing, a public administration API, white-label consoles and cross-provider automatic failover are not promised by this guide.
What the commercial agreement must cover#
Agree on who the seller of record is, customer and provider obligations, permitted resale or managed-service rights, trademarks and co-branding, pricing and overages, support escalation, data responsibilities, termination and offboarding. A Partner Edition subscription or MIT-licensed sample does not automatically grant every resale, trademark or model-provider right.
DCAI supplies the gateway service under its applicable service terms. The model provider's own terms continue to apply. Use of DCAI branding or distribution of a connector or other software component should be scoped in the agreement; the public documentation is not a substitute for that agreement.
Prepare a private-offer request#
Include your expected customer count, number of active keys, monthly open-weight and frontier token volumes, peak traffic, provider and regions, desired start date, billing arrangement and support needs. Send no API keys or customer prompts.
Use the DCAI contact form. A discussion does not create a purchase or commit you to a price.