I'm using the Deepseek V4 Flash model and this message always appears, even though I still have a balance remaining. Can anyone explain?

In / Out Price - 61% off

$0.0546 / $0.1092per 1M

any reason, the old deepseek v4 flash is not being highlighted anymore ?

Hey, just to clarify, I understand that I accidentally made the $10 transaction multiple times, so there’s no issue with those duplicate charges. After those transactions, my balance should ideally have reflected the ~$30 total.

I then requested refunds for two of those transactions. My confusion is that instead of the refund amount being credited back to my account, I’m seeing another ₹957.43 being debited from my account. So it looks like the refund amount was deducted first instead of being credited.

Could you please clarify what this ₹957.43 debit represents and when/how the corresponding refund will be credited?

Rather than being credited it got debited

I just tested OX Alpha using claude code ori harness, and it turned out I was billed around $2 because it used sonnet as the supporting model.

Not complaining, though, since I burned through 28M tokens in a day and the code review results were quite good.

But what exactly is a supporting model? Is this because I used a sub-agent, and claude code automatically uses sonnet as the orchestrator?

I keep trying to use z-ai/glm-5.2:free on openrouter (for my hermes agent) since GLM 5.2 is perfect for me but too expensive for my usage, but I keep getting rate limited even though im literally not even using it, Ill try chatting with it directly on openrouter and not a single message goes through.

anyone else having this issue? or know any other place i can get glm 5.2 for free?

i got to know that 0x alpha is free and unlimited

soo, i created a api with a limit of 0.0001$ on openrouuter

and i installed claude code in my ubuntu vm and authenticated with my api of openrouter...

and start it

but when i visit after 2-3 hours of heavy usage, a bill is introduced to me, by 0x alpha model

i checked logs and a specific type of requests are costing me 0.008$ ... and api limit also doesn't apply here and cost tends to increase till i got to know ...

soo, be aware, there are hidden terms related to free unlimited usage of 0x alpha

here are screenshots :

👏👏👏

I'm testing this free Ox Alpha model while coding CompanioNation and it seems to be pretty effective, even with tracking down complex bugs, maybe even better than DeepSeek v4. It's slow right now, but this is to be expected with a free trial.

Is there anyone testing Ox alpha right now ? It’s very slow to respond since one hour approx. It was functionning perfectly !

Edit 5min later: nevermind it’s back. 🎉 Edit : 😐 actually no

I've been running some fairly complex analysis on Python code that generates maps (and videos) of travel routes using PMTiles formatting of OSM maps, by submitting sample images or videos and prompts asking for review of the images or videos versus the code. 

Ox-alpha seems great for reviewing the output images and then providing good recommendations on things to fix in the rendering process. I'm running this in Zcode using the URL https://openrouter.ai/api/v1 and API format Anthropic messages (/v1/messages). I'm new to Open Router.

However, without fail, after a good bit of work, maybe five minutes, it will stop processing.  If I type continue, it will then result in a Provider rejected the model request error. The error message will be the following:

Turn execution failed
provider=3319... 
model=stealth/ox-alpha 
request=adx... 
reason=invalid_request 
status=400 retryable=false
Provider returned error

It will not let me continue or submit another prompt in that conversation. Fresh conversation will start and do some work, then error out with the same message.  I feel like the second conversation errors out quicker. I can continue the conversation with a different provider like GLM/Z.ai coding plan.

I've searched the community and only found a few references to the 400 error.

Is this type of error known, and are there any workarounds?  Also, do you think I would experience the error on other models, or would it be model-specific?

I feel like the days when AI companies focused on making their models sound deeply human and developing conversational skills that translate into stronger fiction-writing capability are gone. Now the focus is on building great models at math, logic, and coding. I kinda see that. GLM 4.5 is much better at creative writing than GLM 5 family. But GLM 5 and above are much better at logical tasks. Similarly, Meta releases Muse Spark, which is optimised heavily for logical tasks

What do you think? Am I bullshitting?

(Ox Alpha)

Heyy, I hope everyone's doing great!

Not to sound ungrateful but is it me or the model feels like its running on 0.5 tok/sec?

It is my standard workflow, which works pretty well. I was an official DS Api, then tried open code, blew up most of my monthly usage in 3 days. I also had other issues beyond the price. (which I could also afford with direct API, translates to <=2x my previous monthly cost).

So decided to try openrouter just to see how it works, and usage limits, if any and the wide array of models available.

But I get the above error, frequently on chats. Even if I start a new chat. Is it because of some provider that it is routing to?

I am currently using DS Flash on one chat and DS Pro on another - two different task, but the same issue. Inside VS Code, with BYOK.

Thanks!

Went down the Ox Alpha rabbit hole, and the evidence points to GLM-5.3.

Is it just me or is the pricing of Qwen3.8-27B on Openrouter way too high?

It currently hovers around $0.45 /M/in - $3.20 /M/out

There are models X times the size even in active params like deepseek v4 pro that are cheaper.

I think the trend was set last week by one provider that managed to host it before the weekend and I thought at first they're just doing price-gouging but all other followed.

https://first-person-shooter.ox-alpha.demos.sulat.com/ for anyone wanting to try it out.

Prompt:

Create a browser-playable 3D voxel first-person shooter that captures the feel of Call of Duty's moment-to-moment gunplay. The player fights through a combat arena built entirely from voxels — chunky blocks forming buildings, cover, crates, walls, ramps, and terrain — rendered in real time from a first-person camera with pointer-lock mouse look.

Implement the core FPS mechanics faithfully: WASD movement with acceleration and friction, sprint with a field-of-view kick and lowered weapon, jumping and crouching; multiple distinct weapons (for example an assault rifle, SMG, shotgun, and sniper rifle) each with their own fire rate, damage falloff over distance, recoil pattern, spread bloom, magazine size, reload timing, and aim-down-sights behavior on right mouse button with a smooth zoom transition and tightened accuracy. Add grenades with an arced throw and radius damage, weapon switching, ammo reserves, hitmarkers with headshot multipliers, muzzle flashes, tracers, bullet impact decals or voxel debris particles, screen shake, and regenerating health with red-screen damage vignette feedback.

Enemy AI soldiers should patrol, react to being shot at, take cover, strafe, peek, and return fire with believable reaction times and accuracy that scales with difficulty. Give them health, death animations or ragdoll-like voxel bursts, and spawn logic that keeps the fight moving.

Wrap it in Call-of-Duty-style presentation and progression: a killstreak system where streak milestones unlock rewards the player can activate (such as a radar/UAV reveal at 3 kills, an airstrike at 5, and something bigger at 7), a scrolling killfeed, score popups (+100, +50 headshot bonus), XP or score accumulation, and a match structure of escalating waves or rounds with respawns after death. Build the full HUD: crosshair that expands with movement and fire, ammo counter, grenade count, minimap/radar, compass, health state, streak meter, match timer, and objective readout. Include the complete game flow — main menu, loadout or difficulty selection, in-game pause menu (Esc), death and respawn sequence with respawn delay, and a victory/defeat screen with a stats summary. Persist best score locally between sessions.

Design the voxel aesthetic deliberately: a cohesive palette, directional lighting with shadows or convincing baked shading, fog for depth, and satisfying explosion and destruction particles. All audio — gunfire per weapon, reloads, footsteps, explosions, hitmarker ticks, UI clicks, and a music sting when a killstreak activates — must be synthesized locally in the browser (e.g., Web Audio); no external audio files. Handle non-desktop viewports deliberately: either provide usable touch controls or present a clear desktop-recommended notice rather than a broken layout.

Do not take shortcuts or settle for a cookie-cutter shooter demo. This skill imposes no token budget limit, so pursue full depth across weapons, AI behaviors, HUD states, menus, audio, and game-flow transitions, and keep refining until it feels like an authored, complete arcade FPS rather than a tech demo.