Pre-merge review
Send the diff and the changed function's contract. Ask for bugs with reproducible consequences, kept separate from style preferences.
Coding / API
GPT-5.6 Sol through the CLODEx API: from diff analysis to test preparation. Explore public Fixed Usage pricing, an integration example and change-review workflows.
gpt-5.6-solopenaiIn the public catalog A catalog listing is not a live availability guarantee. Check /v1/models for access with your API key.
01 / YOUR BRIEF
Review the payment-handler diff. Focus on idempotency, signature verification and webhook redelivery. For each bug, provide inputs, expected behavior and a regression test.
A sample brief — add your own inputs. This page does not generate content or charge your balance.
02 / USE CASES
Send the diff and the changed function's contract. Ask for bugs with reproducible consequences, kept separate from style preferences.
Specify expected errors, date formats and empty-input behavior. Request tests that fail on the old implementation and pass on the new one.
03 / SPECIFICATIONS
gpt-5.6-solOnly parameters declared by the integration catalog are shown. An omitted parameter is not a promise of support.
04 / DEVELOPERS
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":"Review the payment-handler diff. Focus on idempotency, signature verification and webhook redelivery. For each bug, provide inputs, expected behavior and a regression test.","role":"user"}],"model":"gpt-5.6-sol","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.
Documentation ↗Fixed Usage is expressed per total tokens, not just input. Cached input has a separate row when that rate is published. Share only relevant files and remove secrets. Review changes and run tests before applying them. A model response does not guarantee correct code.
05 / FAQ
Sign in to CLODEx, check model access for your key and choose the workspace or API. Reading this page does not submit a model request.
Public rates appear in the pricing section. Check the unit: total tokens, separate input and output tokens, per image or a parameter-based video quote. Confirm your account rate in the dashboard.
Keep the request ID and check the request log. For asynchronous generation, check the existing job's status first. If the cause remains unclear, contact support with the ID, never the API key. Resubmitting may create another paid job.