--- title: "OCI Generative AI free inference" description: "$300 for new accounts; it does not recur. See verified limits, model IDs, privacy terms, and primary sources for OCI Generative AI." canonical_url: "https://freeinferencing.com/provider/oracle_oci_generative_ai/" md_url: "https://freeinferencing.com/provider/oracle_oci_generative_ai.md" last_updated: "2026-09-19" --- # OCI Generative AI > $300 for new accounts; it does not recur. ## Classification - **Directory:** Current - **Free access:** One-time trial - **Status:** Current trial - **Confidence:** High - **Payment card:** Yes - **Account:** Not documented - **Equivalent paid value:** $300.00 once - **API endpoint:** `https://inference.generativeai.{region}.oci.oraclecloud.com/openai/v1` ## Models mentioned No stable model IDs were recorded in this snapshot. ## Limits and terms ```yaml general_cloud_credit_usd: 300 duration_days: 30 recurrence: false ``` ## What happens to your prompts? **Private.** Ordinary inference is not stored or used for general model or service improvement; persistence is customer-selected. Privacy is audited separately from price. Review the current governing terms before sending sensitive or regulated data. ## Data governance and agreements ```yaml data_governance: review_status: reviewed plan_scope: OCI Generative AI inference and fine-tuning; project Responses, Conversations, files, memory, agents, and other stateful resources have configurable retention. prompt_retention: Oracle states ordinary model-inference inputs and outputs are not stored inside OCI Generative AI. Project-based agent and OpenAI-compatible resources can deliberately retain responses and conversations under customer-selected settings. response_retention: Stateless outputs are not stored; project artifacts and agent sessions follow feature-specific retention. ordinary_logging: OCI retains service, audit, metering, security, and resource metadata under Oracle Cloud terms without treating stateless prompt content as ordinary logs. model_training: Oracle states customer prompts, responses, knowledge bases, and fine-tuning data are not used to improve general OCI models or services. product_improvement: Customer content is excluded from general service or model improvement; operational telemetry remains available for cloud operations. human_or_operator_access: OCI says stateless input and output are not retained or shared with third-party model providers. Saved project resources and support material remain accessible under customer IAM and Oracle Cloud controls. subprocessors_and_routing: OCI does not share prompts, responses, training data, or custom models with underlying third-party model providers such as Cohere, Meta, xAI, or Google Vertex AI. deletion_controls: Stateless content requires no deletion. Customers manage project response and conversation retention, files, memory, custom models, and Object Storage training data within their tenancy. caveat: The no-store statement covers ordinary inference, not newer stateful project and agent features. Verify retention settings whenever using Responses, conversations, files, containers, memory, or RAG. agreements: cloud_services_agreement: https://www.oracle.com/contracts/cloud-services/ data_processing_agreement: https://www.oracle.com/contracts/cloud-services/ privacy_policy: https://www.oracle.com/legal/privacy/privacy-policy.html ``` ## Eligibility ```yaml new_customer_only: true mobile_phone_required_for_most_users: true payment_card_required_for_most_users: true ``` ## API compatibility and modalities - **Compatibility:** OpenAI Responses, OpenAI Chat Completions, Oci Native Inference - **Modalities:** Text generation ## Before you build with OCI Generative AI ### Read the classification narrowly This record describes the bounded offer supported by evidence on 2026-09-19; it does not guarantee permanence, production suitability, uptime, latency, model quality, or access from every account and region. “One-time trial” should be interpreted together with the Current directory placement, High confidence, Yes payment-card status, and the plan-specific sources below. ### Resolve the live model route No stable model ID is recorded. Resolve the current machine-readable ID, endpoint, authentication method, and request shape from the provider's live documentation before writing fixed production configuration. ### Match the quota to the workload shape Translate the allowance into peak requests per minute, input and output tokens, concurrency, retries, and every daily or monthly ceiling that applies to the intended account. The first limit reached by the workload is the practical ceiling. A large token pool can still fail interactive bursts, and a high request limit can still fail long-context work. Include tool calls and retry traffic, test the largest realistic payload, and treat research, experimental, and community access as conditional on their eligibility and fair-use terms. ### Preserve billing and privacy boundaries The recorded payment-card requirement is Yes, and account access is not documented. Confirm both in the live signup flow, set provider-side budgets when charges are possible, and observe the balance or usage fields after a complete request. The prompt-handling classification is **Private** because Ordinary inference is not stored or used for general model or service improvement; persistence is customer-selected. Re-read the terms for the exact route and plan before sending sensitive, regulated, or proprietary content. ### Follow the evidence, then re-check it This record links 10 first-party sources covering the offer, catalog, limits, pricing, terms, privacy, or adoption evidence available to the audit. Prefer the newest and most specific governing document or live catalog when sources disagree. A dated finding can become stale even when the page remains online, so retain the source and snapshot that supported the decision and submit a correction when a provider changes a material term. ### Plan fallback without policy drift A fallback should preserve modality, context length, streaming, structured output, tools, safety controls, and data terms, not only API syntax. Decide which errors may retry, cap retry storms, and prevent an exhausted free route from silently switching to a billable model. Rotating aliases and free pools can change behavior without changing the endpoint, so retain the response model field and test at least one substitute route before the primary offer becomes unavailable. ### Monitor the offer as a dependency Capture the model ID, response model, rate-limit headers, usage fields, latency, HTTP status, and provider request identifier. Watch authorization failure, quota exhaustion, catalog removal, policy revision, and balance movement as separate failure modes. Re-check the live catalog and governing sources on a schedule proportionate to the workload's importance, and keep an owner and exit path for any production dependency on volatile free capacity. ### Test one complete request before scaling Start with the smallest permitted request using the exact credential, model ID, endpoint, region, and account type intended for deployment. Record the status, headers, usage fields, response model, latency, and dashboard balance movement. Then exercise an invalid model, quota exhaustion, or rate limit so failure is explicit and cannot silently switch to a paid route. Validate streaming, structured output, and tool calls separately because a free model can expose fewer features than its paid counterpart. Keep a budget ceiling outside the application whenever billing is possible, and do not send sensitive data until the observed route matches the reviewed agreement. ## Primary sources - [OCI Free Tier](https://docs.oracle.com/en-us/iaas/Content/FreeTier/freetier.htm): Official Trial - [Oracle Cloud Free](https://www.oracle.com/cloud/free/): Official Trial - [OpenAI-compatible API](https://docs.oracle.com/en-us/iaas/Content/generative-ai/openai-compatible-api.htm): Official Docs - [Oracle Cloud Services Agreements](https://www.oracle.com/contracts/cloud-services/): Official Terms - [Oracle Privacy Policy](https://www.oracle.com/legal/privacy/privacy-policy.html): Official Privacy - [OCI Generative AI data handling](https://docs.oracle.com/en-us/iaas/Content/generative-ai/data-handling.htm): Official Docs - [OCI Generative AI projects and retention](https://docs.oracle.com/en-us/iaas/Content/generative-ai/projects.htm): Official Docs - [PyPI download stats for oci (whole-OCI SDK including the Generative AI Inference client)](https://pypistats.org/packages/oci): Package Registry Stats - [2024 Stack Overflow Developer Survey technology section](https://survey.stackoverflow.co/2024/technology): Independent Survey - [Oracle announces general availability of OCI Generative AI (2024-01-23)](https://www.oracle.com/news/announcement/oracle-announces-availability-oci-generative-ai-service-2024-01-23/): Official Press Release ## Sitemap See the full [semantic sitemap](/sitemap.md) for every page and markdown mirror.