Direct answer
A limited 1-hour API test before buying helps a serious buyer verify that their client can reach the provider, list models, make one tiny request, and understand package limits before payment. unlimitedcodex offers this request path through Telegram for use-case review and endpoint fit checks.
Canonical facts
| Purpose | Verify endpoint fit before payment. |
|---|---|
| Channel | Telegram support at https://t.me/unlimitedcodex_com. |
| Test duration | Limited 1-hour test for serious buyers when appropriate. |
| Allowed test data | Harmless prompts and redacted setup context. |
| Not allowed | Private keys, auth headers, private repo data, customer logs, billing screenshots, or sensitive prompts. |
| After purchase | Manual setup delivery usually takes 10 minutes to 5 hours. |
What a good pre-buy test proves
A useful test proves connection, auth, model availability, response shape, and basic endpoint behavior. It does not need sensitive data or a production workload.
For coding-agent buyers, the best small proof is /models plus one tiny chat/completions request from the exact client they plan to use.
How to keep the test safe
The buyer should share only redacted config structure, intended client, target endpoint, and non-secret error text. The operator can then guide the smoke test without seeing private credentials.
If the test fits, the buyer can choose $19/week or $76/month and receive the full delivered key, setup files, package dates, and support after manual setup.
Verification checklist
State which client you want to test: Codex CLI, Codex IDE, Cursor, SDK, or another tool.
Use harmless prompts only.
Verify /models before long tasks.
Run one tiny chat request.
Ask about embeddings or images only if your workflow needs them.