Build on the platform. Keep control of your application.
Start with model access, then use the platform components your application needs. Your code owns the product experience and business logic.
Applications using multiple models
Use the same client to call OpenAI, Anthropic, and Gemini. Select models in code and inspect their usage and costs together.
Managed credentials remove the need to operate provider accounts for each integration. Bring your own keys when you want providers to bill your account directly.
Connect modelsSearch and retrieval
Upload documents to managed vector stores for chunking and retrieval. Attach those stores to an agent so its file-search tool can retrieve relevant passages.
For applications with their own retrieval pipeline, use the embeddings endpoint to obtain vectors without storing data in Ingram Cloud.
Build with retrievalApplications that call tools
Connect your backend over MCP and let Ingram Cloud run the model-and-tool loop. Configure approvals for actions that need a human decision.
Keep a client-side tool loop when tool execution belongs in your process. The compatibility guide documents both integration paths.
Connect your toolsAI features with usage controls
Attribute model usage to your application’s users and customers. Set budgets, inspect run history, and connect usage data to your own reporting.
Your application maps its user IDs to the platform’s scoped runtime instances. Each can have separate context, connections, and spending controls.
Track and control usageConnect your application.
Create a project, get a token, and follow the quickstart for your first API request.