On this page
01
Use cases
What this model is useful for
Compare configurations
Provide both versions and define how removed and zero values should be represented. A normal JSON parser can validate the result.
Inspect a screenshot
If the route accepts images, attach the actual file and ask only about visible elements. A screenshot cannot reveal hidden server settings.
Extract facts from a PDF
Provide the relevant pages and require section references. Break a large document into questions so omissions are easier to spot.
02
Examples
Prompts you can try
A sample brief — add your own inputs. This page does not generate content or charge your balance.
Prompt for an independent test — no saved Gemini 3.8 Flash output is attached yet.
Preserve zero and false
The expected array has two entries: changed retries and removed cache. timeout must be absent. These are task criteria, not a published model output.
Compare JSON A={"retries":0,"cache":false,"timeout":30} with B={"retries":2,"timeout":30}. Return a JSON array containing only changed fields with field, before, after and change. For a removed field use after=null and change="removed"; for a changed field use change="changed". Omit unchanged timeout. Do not treat 0 or false as missing.Make the prompt your own
- If the announcement lacks an address or price, ask for a separate list of details to clarify.
- For a chat message, limit the result to five lines.
How to check the result
- The result contains only retries and cache; timeout is absent.
- The before value is 0 for retries and false for cache.
- cache is marked removed with after=null; retries is marked changed with after=2.
- A published run preserves the exact prompt, valid JSON, model ID, date and usage.
03
Pricing / USD
CLODEx public pricing
The card above shows CLODEx rates for gemini-3.8-flash. They are not Google API prices; account for actual input, output and retries.
Full pricing details04
Get started
How to get started
Check access
Confirm that gemini-3.8-flash appears in /v1/models for your CLODEx key.
Use the CLODEx format
Configure a compatible endpoint from /docs. Do not paste a native Google contents/parts body into an OpenAI-compatible request.
Test text before attachments
Start with the short JSON fixture. After it works, test images or PDFs separately using the format supported by your route.
One API for your application.
curl --fail-with-body --no-buffer 'https://clodex.xyz/v1/chat/completions' \
-H "Authorization: Bearer $CLODEX_API_KEY" \
-H 'Content-Type: application/json' \
--data-binary @- <<'CLODEX_JSON'
{"messages":[{"content":"Compare JSON A={\"retries\":0,\"cache\":false,\"timeout\":30} with B={\"retries\":2,\"timeout\":30}. Return a JSON array containing only changed fields with field, before, after and change. For a removed field use after=null and change=\"removed\"; for a changed field use change=\"changed\". Omit unchanged timeout. Do not treat 0 or false as missing.","role":"user"}],"model":"gemini-3.8-flash","stream":true}
CLODEX_JSONKeep your key on the server, never in the browser. A generation example uses your balance only when you run it yourself. Check model access and parameters before submitting.
How to get an API key05
Specifications
Capabilities and limitations
- Model ID
gemini-3.8-flash- API protocols
- OpenAI-compatible API
Only parameters declared by the integration catalog are shown. An omitted parameter is not a promise of support.
Model and integration
What this model is
Google describes Gemini 3.8 Flash as a fast multimodal model with text output. CLODEx uses the exact gemini-3.8-flash ID through its own compatible route.
Why the JSON example
Zero and false are often lost in careless comparisons. This task can be checked automatically rather than judged by writing style.
Native versus compatible APIs
The Google SDK uses generateContent with contents/parts. A CLODEx compatible client uses the format documented in /docs; request and response bodies differ.
What to consider
CLODEx is not Google AI Studio
The interface, keys, endpoint and available tools differ. A Google example cannot be copied without adaptation.
Multimodality depends on the route
Upstream documentation lists multiple input types, but each attachment must be supported by CLODEx and your client.
JSON still needs validation
Even a polished answer may violate the schema or add prose. Use a parser and error handling in automation.
Before you submit
The Gemini name alone does not grant Google Search, code execution or file access. The selected CLODEx protocol must support each tool, attachment type and response format.
06
Related models
Models to compare
GPT-5.6 Luna
gpt-5.6-lunaFor short classification or extraction, use one labeled set. Compare accuracy, valid formatting and cost per accepted result.
GLM-5.3
glm-5.3For code, provide the same diff and tests. Verify image and tool support separately on each route.
07
FAQ
Model FAQ
Is this the same access as Google AI Studio?
No. CLODEx has its own key, balance and endpoint. Google AI Studio features are not automatically included.
Can I send an image or PDF?
Only if the selected route and client support that input. Verify the format in /docs using a small redacted file.
Can it return strict JSON?
Confirm a structured-output mode for the route or validate a normal text response. A prompt alone does not guarantee a schema.
Are Google Search and code execution available?
Not by default. The CLODEx endpoint and client must explicitly support those tools.
How is cost calculated?
By the CLODEx rate and actual request and response volume. Attachments, long history and retries increase usage.
08