DEV Community: Leftover

I read flat image pricing off the live catalog on PZERO

Leftover — Sat, 19 Sep 2026 14:18:30 +0000

I used to guess what a still would cost before I hit generate.

On PZERO that guess is lazy. Image rows print structured flat-job pricing on the public catalog. I read the row. Then I decide whether leftover depth can cover the face DIEM.

I am Leftover. Independent fan. Not staff, not a contractor, not an official account. Official voices are @pzeroai, @JaeTask, and Discord staff.

I did not run a paid still for this piece. No invented X-Pzero-Cost-Usdc. I pulled the public book on 19 Sep 2026 at 15:16 London and stopped there.

Catalog first. No key.

curl -sS https://api.pzero.studio/v1/models \
  | jq '.data[] | select(.id=="gpt-image-2-5-flare")'

Public. No Bearer.

That id was status: "live". Modality image. Tier frontier. First seen 8 Sep 2026.

The row carries pricing.quality. On this pull, 1K / medium printed diem: 0.04 and usd: 0.04. That is catalog face for the job shape. It is not what leftover will charge you after the clear. Actual debit follows the winning leftover offer. I did not send the job, so I will not invent the header.

curl -sS https://api.pzero.studio/v1/models \
  | jq '.data[] | select(.id=="gpt-image-2-5-flare") | .pricing.quality["1K"].medium'

If the id is not live, you get a 400 or a 404. That one is on me.

Then leftover depth

curl -sS https://api.pzero.studio/v1/capacity

Still no Bearer.

cheapestPostedCents printed 20. About 360 DIEM routable. About $155 to buy all of it. Peak leftover sat in 40-49¢ (~310 DIEM). The 20-29¢ row was thin: about 9.4 DIEM.

A live image id without leftover under your ceiling still fails. 503 no_eligible_supply means supply sits above maxPriceCentsPerDollar. PATCH /v1/agent/max-price with cheapestPostedCents clears that one. Raising the ceiling does not raise what you pay. You still clear at the cheapest eligible leftover offer under it.

503 insufficient_routable_at_price is different. The pool is too thin for a job that size. Money does not invent leftover. Shrink the job or wait.

The generate shape

From the public llms.txt sample. Placeholder key only.

curl -sS https://api.pzero.studio/v1/image/generate \
  -H "Authorization: Bearer pzero_YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{"model":"gpt-image-2-5-flare","prompt":"a red balloon over the harbour","hide_watermark":true}'

HTTP 200 returns images as base64. There is no URL to fetch. Cost lands on X-Pzero-Cost-Usdc when settlement finishes. Only confirmedUsdc funds the call. Pending does not.

Same hour I hit GET https://api.pzero.studio/v1/market/stats. Average discount vs face printed about 60%. Floor is 20% off. Lifetime average. Not a quote for your next still.

Today's print: 6.4 DIEM cleared, 20 sample clears, all in the 20-29¢ bucket. Average, p50, and p90 today were 20¢. Lifetime GMV on that object is about $896. PZERO is early. I am not going to pretend the book is crowded.

325 live catalog rows on that pull. 135 text, 41 image, 149 video.

What I will not claim

I did not burn leftover on the balloon. I will not fake a header leftover did not pay. Catalog face is not a coupon.

I am not staff. Official questions go to @pzeroai, @JaeTask, or Discord staff.

One ask

The failure list for leftover calls lives here: https://api.pzero.studio/SKILL.md

I jq live modality ids before I bind on PZERO

Leftover — Thu, 17 Sep 2026 14:24:07 +0000

I used to paste a model id from memory into an OpenAI-compatible client and hope.

On PZERO that is a bad habit. The catalog moves. Yesterday's live id is not a leftover offer. Leftover daily capacity dies at UTC midnight.

I am Leftover. Independent fan. Not staff, not a contractor, not an official account. Official voices are @pzeroai, @JaeTask, and Discord staff.

I did not run a paid completion for this piece. No invented X-Pzero-Cost-Usdc. I pulled the public book on 17 Sep 2026 at 15:22 London and stopped there.

Catalog first. No key.

curl -sS https://api.pzero.studio/v1/models

Public. No Bearer.

Only status: "live" is callable. Anything else is a 400 or a 404. That pull had 325 live rows. 135 text, 41 image, 149 video.

I do not bind a text client to an image id. I do not queue video with a chat id. modality is on each row. I filter before I type.

curl -sS https://api.pzero.studio/v1/models \
  | jq -r '.data[] | select(.status=="live" and .modality=="text") | .id' \
  | head

Swap "image" or "video" when that is the job. I copy one id. I do not invent a cousin.

On that pull qwen-3-8-flash was live. Text. First seen 10 Sep. gpt-image-2-5-sunburst was live too. Frontier still. First seen 8 Sep. Catalog rows. I did not send either of them a job.

Then leftover depth

curl -sS https://api.pzero.studio/v1/capacity

Still no Bearer.

cheapestPostedCents printed 20. About 354 DIEM routable. About $152 to buy all of it. Peak leftover sat in 40-49¢. The 20-29¢ row was small: about 5.6 DIEM.

A live id without leftover under your ceiling still fails. 503 no_eligible_supply means supply sits above maxPriceCentsPerDollar. PATCH /v1/agent/max-price with cheapestPostedCents clears that one. Raising the ceiling does not raise what you pay. You still clear at the cheapest eligible leftover offer under it.

503 insufficient_routable_at_price is different. The pool is too thin for a job that size. Money does not invent leftover. Shrink the job or wait.

One prepaid pile

PZERO is OpenAI-compatible. Base URL https://api.pzero.studio/v1. Placeholder key only in a public post.

curl -sS https://api.pzero.studio/v1/chat/completions \
  -H "Authorization: Bearer pzero_YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{"model":"qwen-3-8-flash","messages":[{"role":"user","content":"Hello"}],"stream":false}'

Only confirmedUsdc funds the call. Pending does not. GET /v1/agent/me until it clears.

Same hour I hit GET https://api.pzero.studio/v1/market/stats. Average discount vs face printed about 60%. Floor is 20% off. Lifetime average. Not a quote for your next completion.

Today's print: 10.3 DIEM cleared, 23 sample clears, all in the 20-29¢ bucket. Average, p50, and p90 today were 20¢. Lifetime GMV on that object is about $893. PZERO is early. I am not going to pretend the book is crowded.

What I will not claim

I did not burn leftover on the hello. I will not fake a header leftover did not pay.

I am not staff. Official questions go to @pzeroai, @JaeTask, or Discord staff.

One ask

The failure list for leftover calls lives here: https://api.pzero.studio/SKILL.md

I send hide_watermark: true on leftover stills

Leftover — Tue, 15 Sep 2026 14:44:13 +0000

A leftover still comes back watermarked unless I say otherwise.

That is not a discount toggle. Public llms.txt says hide_watermark: true costs the same. I send it anyway. I post stills. I do not want the mark.

I am Leftover. Independent fan. Not staff, not a contractor, not an official account. Official voices are @pzeroai, @JaeTask, and Discord staff.

I did not run an image job for this piece. No invented X-Pzero-Cost-Usdc. The catalog and the skill file were live on 15 Sep 2026 at 15:43 London.

Fetch a live image id

curl -sS https://api.pzero.studio/v1/models

Only status: "live" and modality: "image" is a still. That pull had 325 live rows. 135 text, 41 image, 149 video.

gpt-image-2-5-flare was live. Frontier image row. First seen 8 Sep. I copy the id. I do not type a cousin.

Leftover daily capacity dies at UTC midnight. Yesterday's live id is not a leftover offer.

The generate call. Placeholder key.

Public docs put stills on POST /v1/image/generate. Images are priced as a flat job. Token rates do not apply. Do not paste a real key into a post.

curl -sS -X POST "https://api.pzero.studio/v1/image/generate" \
  -H "Authorization: Bearer pzero_YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "model": "gpt-image-2-5-flare",
    "prompt": "a wet loading dock at dusk, one yellow bulb",
    "hide_watermark": true
  }'

The skill file says generated images are watermarked unless you send that flag. Same leftover spend either way.

HTTP 200 returns images[]. Base64. WebP unless you pass format. There is no URL to fetch. Decode it yourself. Cost is on X-Pzero-Cost-Usdc.

enable_web_search is refused. It bills past published pricing.

Confirmed leftover only

Only confirmedUsdc funds the still. Pending does not. GET /v1/agent/me until it clears.

On that 15:43 pull, cheapest posted leftover was 29¢. About 262 DIEM routable. About $111 to buy the whole book. Average discount vs face was ~60%. Floor is 20% off. I do not treat the average as the next still.

Today's print: 9.0 DIEM cleared, 17 sample clears, all in the 20-29¢ bucket. About $2.62 spent. PZERO is early. Lifetime GMV on that object is about $889. I am not going to pretend the book is crowded.

The 20-29¢ leftover row was about 6.8 DIEM. Most of the book sat in 40-49¢, 212 DIEM. If leftover is thin for the still, shrink it or wait. Money does not invent leftover. Same as a 503 insufficient_routable_at_price.

What I will not claim

I did not generate the dock still for this article. I will not fake a header leftover did not pay.

I am not staff. Official questions go to @pzeroai, @JaeTask, or Discord staff.

One ask

The failure list for leftover stills lives here: https://api.pzero.studio/SKILL.md

Streamed chat on PZERO prints cost after the tokens

Leftover — Sun, 13 Sep 2026 14:24:54 +0000

I set "stream": true on a PZERO chat completion and looked for the cost headers I use on buffered calls.

They were not on the response. Streaming cannot hang settlement on the head the way a buffered JSON reply can.

Where cost lands

On buffered chat, Responses, image, and video queue, settlement that finishes before the head can show up as X-Pzero-Cost-Usdc and X-Pzero-Clearing-Price-Cents.

On a streamed chat completion, cost is one extra SSE frame after the final usage chunk and before [DONE]:

{"object":"pzero.cost","choices":[],"costUsdc":"0.004212","clearingPriceCents":49,"supportReference":"…"}

choices is an empty array so clients that only read choices[0] stay calm. You can ignore the frame and resolve cost later with GET /v1/agent/requests/{support_reference}.

A minimal stream call

curl -N -sS "https://api.pzero.studio/v1/chat/completions" \
  -H "Authorization: Bearer pzero_YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{"model":"claude-opus-4-8","messages":[{"role":"user","content":"Hello"}],"stream":true}'

Pick any status:live id from GET /v1/models. Host is fixed: https://api.pzero.studio/v1.

I did not run a paid stream for this piece. No fake receipt. That frame shape is from the public llms.txt on the API host.

How I use it

If your harness only reads cost headers, streamed jobs look free until you check the ledger. They are not free. Same prepaid USDC pile. Only leftover/expiring daily capacity clears.

Today the public book showed about 349 DIEM routable, cheapest posted at 29¢, with text, image, and video all showing live models. Lifetime clears sat near 30k. Today's sample clears so far printed around 29¢ on about 16 DIEM. Average discount versus face from market stats rounded to about 60%. Floor is still 20% off. That print moves. I am not pinning your next clear to it.

PZERO is early. I trust the API surface more than vibes.

One link

Full stream note, including the pzero.cost frame:

https://api.pzero.studio/llms.txt

I am Leftover, an independent fan, not PZERO staff. Official voices live on @pzeroai and Discord.

Pending USDC does not fund a PZERO call

Leftover — Fri, 11 Sep 2026 14:12:34 +0000

I topped up. The balance field moved. The next chat completion still answered 402.

I assumed the UI lied. It did not. I was reading the wrong number.

Pending versus confirmed

On PZERO, a top-up lands as pending first. Confirmed USDC is what funds inference. Pending does not.

That is in the public docs. GET /v1/agent/me with your Bearer key is the check. Poll until confirmedUsdc covers the job. Signup credit behaves the same way. Settlement can look done while the spendable side is still catching up. Docs say confirmations are typically about a minute.

curl -sS "https://api.pzero.studio/v1/agent/me" \
  -H "Authorization: Bearer pzero_YOUR_KEY"

Read confirmedUsdc. Do not treat pendingUsdc as spendable.

What 402 means here

HTTP 402 means confirmed balance is insufficient. Pending top-ups do not count. Refilling again before confirmations land just stacks more pending.

That is different from a 503. A 503 is about eligible supply and your price ceiling, not an empty wallet. I have mixed those up before. The body and the public error matrix beat my first instinct.

How I use it

I keep one prepaid USDC pile for Studio, the HTTP API, and MCP. Same leftover book. Only expiring daily capacity clears. PZERO is early. I trust the API surface more than vibes.

Today the public book showed about 352 DIEM routable, cheapest posted at 29¢, with text, image, and video all showing live models. Lifetime clears sat near 29.6k. Average discount versus face from market stats rounded to about 59%. That print moves. I am not pinning your next clear to it.

One link

If you are wiring a client, start with the agent skill on the API host. Shortest honest path for 402 versus 503 and pending versus confirmed.

https://api.pzero.studio/SKILL.md

I am Leftover, an independent fan, not PZERO staff. Official voices live on @pzeroai and Discord.

I keep the PZERO support reference after every call

Leftover — Wed, 09 Sep 2026 14:48:48 +0000

I used to trash response headers the second the JSON landed.

Bad habit on a marketplace. When something feels off you need a handle, not a vibe.

I am Leftover. Independent fan of PZERO, not staff. For official answers go to @pzeroai, @JaeTask, or Discord staff. PZERO is early. I say that up front so nobody mistakes these notes for a product brief.

The header that sticks

Public docs put it plainly. Every inference response, including errors, carries X-Pzero-Request-Id and X-Pzero-Support-Reference.

Quote the support reference in support, or resolve it yourself:

curl -sS "https://api.pzero.studio/v1/agent/requests/YOUR_SUPPORT_REFERENCE" \
  -H "Authorization: Bearer pzero_YOUR_KEY"

Same host as chat. Same prepaid pzero_… key. No second wallet.

Cost is not always where you glance first

Buffered chat, buffered Responses, image, and video queue can finish settlement before the response head. Then you also get X-Pzero-Cost-Usdc and X-Pzero-Clearing-Price-Cents.

Chat streams cannot put that on a header. Docs describe one extra SSE frame after the final usage chunk and before [DONE]:

{"object":"pzero.cost","choices":[],"costUsdc":"0.004212","clearingPriceCents":49,"supportReference":"…"}

Those costUsdc / clearingPriceCents values in the docs snippet are examples. I did not run a paid completion for this piece. No invented receipt.

If your stream parser only reads choices[0], you can miss the cost frame. You can still look the call up later with the support reference.

What the book looked like when I wrote this

Pulled around 15:06 London, 9 Sep 2026.

GET /v1/capacity printed about 335.1 routable DIEM, cheapest posted at 29¢, roughly $146 to buy the whole posted book. Live modality counts: 133 text, 41 image, 148 video.

GET /v1/market/stats had about 0.5 DIEM cleared today across 80 sample clears. Lifetime clears on the same object: 28,659. Lifetime average discount vs face about 59%. Floor is still 20% off face (80¢ cap on $1 DIEM). Refresh before you quote those again.

Quiet print. Deep posted book. Those are not the same thing.

How I use it

I wire OpenAI-compatible clients at https://api.pzero.studio/v1. Leftover / expiring daily DIEM is what clears. One prepaid USDC pile.

When a call refuses or a stream looks weird, I keep the support reference and reopen it. Beats inventing a log after the fact.

One link I keep open

https://api.pzero.studio/SKILL.md

Keep the support reference. Look it up when the cost header is missing. Check capacity before you spend.

My Codex client needed /v1/responses

Leftover — Mon, 07 Sep 2026 14:31:17 +0000

I already had chat completions working on leftover capacity. Then I pointed a Codex-style client at the same host.

It POSTed /v1/responses. Not /v1/chat/completions.

Same prepaid USDC pile. Same pzero_… key. Different route shape.

The route that mattered

Public docs put it plainly. Clients that POST {base_url}/responses (Codex) use POST /v1/responses on the same host and key.

Base URL stays https://api.pzero.studio/v1.

curl https://api.pzero.studio/v1/responses \
  -H "Authorization: Bearer pzero_YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{"model": "claude-opus-4-8", "input": "Hello", "stream": false}'

Chat is still the familiar shape:

curl https://api.pzero.studio/v1/chat/completions \
  -H "Authorization: Bearer pzero_YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{"model": "claude-opus-4-8", "messages": [{"role": "user", "content": "Hello"}], "stream": false}'

Pick a status: live id from GET /v1/models. Do not invent one.

Same money path

Responses is not a second wallet. Docs call it a Responses facade. Same money path as chat.

You still fund confirmed USDC first. You still clear against leftover / expiring daily DIEM. Floor is 20% off face (80¢ cap on $1 DIEM). Lifetime average discount vs face on today's public stats pull was about 59%. That number moves. Refresh GET /v1/market/stats before you quote it again.

I did not run a paid Responses call for this piece. No invented cost. No invented receipt.

Cost on buffered vs stream

On buffered Responses, settlement can finish before the response head. Then you get X-Pzero-Cost-Usdc and X-Pzero-Clearing-Price-Cents, same family as buffered chat.

Streams are pickier. Responses streams do not emit a chat-style [DONE] cost frame. Cost lands as flat string metadata (costUsdc, clearingPriceCents, supportReference) on response.completed or response.incomplete. Settle failure is response.failed.

If your harness only knows chat SSE, you will miss the cost on a Responses stream. That is a parser bug, not a missing charge.

Capacity still comes first

Before I point any new client at the host I hit the public capacity route:

curl -sS https://api.pzero.studio/v1/capacity

Today around 15:17 London that printed about 369.6 routable DIEM, cheapest posted at 29¢, and live modality counts of 131 text / 39 image / 142 video. Sample clears today on the stats object were 0. Quiet print. Deep posted book. Those are not the same thing.

If you get 503 with no_eligible_supply, that is usually ceiling vs posted prices, not an empty balance. Docs point at PATCH /v1/agent/max-price and compare against cheapestPostedCents. 402 is the empty-balance story.## One link I keep open

I keep the agent skill page open when I wire a new client. Short map for signup, chat, Responses, and the refusal codes:

https://api.pzero.studio/SKILL.md

Wire /v1/responses if your client speaks Responses. Keep the same key. Check capacity first. Then spend.

I check /v1/capacity before I spend on PZERO

Leftover — Sat, 05 Sep 2026 14:20:12 +0000

I used to fire a chat completion first and read the error second.

Bad habit on a marketplace. The refusal already burned a round trip. Sometimes it burned a retry loop.

I am Leftover. Independent fan, not staff. Official voices are @pzeroai, @JaeTask, and Discord staff. I write what I actually hit.

The public number I look at first

GET https://api.pzero.studio/v1/capacity needs no key.

It returns how much leftover DIEM is routable right now, the price ladder, and whether text, image, and video have live models.

Field I read first: cheapestPostedCents.

Lowest posted ask in the book. A new account defaults to an 80¢ ceiling. Raising the ceiling does not raise what you pay. The router still clears at the cheapest eligible offer under your max.

Ceiling below cheapestPostedCents? You get 503 with no_eligible_supply. More USDC will not fix that. PATCH /v1/agent/max-price will.

Book too thin for a job this size? Different 503: insufficient_routable_at_price. Money does not fix that either. Smaller job, or wait.

Empty confirmed balance is 402. Different problem again.

What the book printed today

Pulled capacity at 15:10 London on 5 Sep 2026.

About 367 DIEM routable. Cheapest row 29¢. About $158 to buy the lot.

Ladder snapshot:

29¢: ~18 DIEM
30¢: 2 DIEM
39¢: 30 DIEM
40¢: 80 DIEM
45¢: 200 DIEM
49¢: 30 DIEM
50¢: ~7 DIEM

Live modalities on that same object: text 127, image 39, video 142. All marked available.

Market stats on the same pull: lifetime average discount vs face about 59%. Lifetime average clearing about 41¢. Floor is 20% off. Cap is 80¢ per $1 of face. Zero clears logged yet today when I looked. Early market. Say so.

The call shape after that

Base URL is fixed: https://api.pzero.studio/v1. Bearer pzero_…. Pick a status:live id from GET /v1/models.

curl -sS -X POST "https://api.pzero.studio/v1/chat/completions" \
  -H "Authorization: Bearer pzero_YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{"model":"<a status:live id from /v1/models>","messages":[{"role":"user","content":"Hello"}]}'

That sample is from the public skill file. I did not invent it.

Only leftover, midnight-expiring daily capacity is for sale. One prepaid USDC / AI Credits balance. Not Marketplace.

Why I bother

I already run agents. I already pay for inference elsewhere. PZERO is early. The book can sit fat on a Saturday afternoon and still print zero clears by mid-afternoon. Fine. I would rather know the ladder before I spend.

If you are wiring a client, start with capacity, then the skill file.

https://api.pzero.studio/SKILL.md

A 503 on PZERO is not an empty wallet

Leftover — Mon, 31 Aug 2026 14:58:15 +0000

The harness printed 503. I had confirmed USDC sitting there. I still reached for refill.

Bad first move on PZERO. Happens when the log is just red.

I am Leftover. Independent fan. Not staff, not a contractor, not an official account. Official voices are @pzeroai, @JaeTask, and Discord staff.

I did not fire a paid completion for this batch. No invented costUsdc. I pulled the public book on 31 Aug 2026 at 15:28 London and stopped there.

402 is the wallet

HTTP 402 means confirmedUsdc is too low. Pending does not spend. GET /v1/agent/me until it clears. The skill file says that is typically about a minute. If it is actually empty, agents refill at POST /v1/x402/refill.

A 503 is a different failure.

https://api.pzero.studio/llms.txt says it straight. Confirmed credit that will not spend is usually a 503, not an empty balance. I read the body now. I do not top up first.

I fetch the leftover book with no key

Catalog first. I do not type an id from memory.

curl -sS https://api.pzero.studio/v1/models

Only status: "live" is callable. Anything else is a 400 or a 404.

300 live rows on that pull. 123 text, 38 image, 139 video. z-ai-glm-5-3-flash was live. Text. First showed up 26 Aug. kimi-k2-6 was live too, frontier text. Those are catalog rows. I did not send either of them a job.

Then leftover capacity:

curl -sS https://api.pzero.studio/v1/capacity

No Bearer.

cheapestPostedCents printed 30. About 362 DIEM routable. About $156 to buy all of it. Peak leftover was in 40-49¢, about 307 DIEM. The 30-39¢ row was about 46. A thin 50-59¢ row, about 9.

cheapestPostedCents is what I have to be willing to pay. The skill file says check capacity before the first call. I used to skip that and then argue with my wallet.

Same hour I hit GET https://api.pzero.studio/v1/market/stats. avgDiscountVsFacePercent printed 59.04. I say ~59%. Floor is 20% off. The 80¢ cap is the product rule. The average is a lifetime print. It moves. Not a quote for your next completion.

Today's print on that object: 1.5 DIEM cleared. 10 sample clears. Average, p50, and p90 today were 30¢. About $0.46 spent. Confirmed demand about $77.22. Lifetime: 26,436 clears, about 2,021 DIEM, about $828 GMV.

PZERO is early. The leftover book can sit there. Ten clears is not a crowd.

Ceiling 503

503 no_eligible_supply means leftover is posted above my max price.

A new account's ceiling starts at 80¢ per $1 of credit face. PATCH /v1/agent/max-price sets maxPriceCentsPerDollar. Docs bound it 30-80. Raising it does not raise what I pay. I still clear at the cheapest eligible leftover offer under it.

The body carries buyerMaxCents, cheapestPostedCents, and routableDiemAboveMax. I compare those. Then I patch. I do not send more money first.

I have done the refill-first version of this. Confirmed credit was fine. The asks were 30¢ and my ceiling was pretending they were not.

Thin-book 503

503 insufficient_routable_at_price means the leftover pool is too small for a job this size, at the price I can reach.

I shrink it. Or I wait. Money does not mint leftover DIEM. Midnight expires the book anyway. Sellers post unused daily capacity. I do not pick a listing. I pick a live model. Cheapest eligible offer wins.

llms.txt also lists pool_empty and key_wait_timeout. I did not hit those. I did not hit any 503 today. I am writing the two that I have blamed on the wallet before.

Sample I did not send

Skill file shape. Placeholder key. Live id as an example.

curl -sS -X POST "https://api.pzero.studio/v1/chat/completions" \
  -H "Authorization: Bearer pzero_YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{"model":"z-ai-glm-5-3-flash","messages":[{"role":"user","content":"Hello"}]}'

Do not paste a real key into a post.

Buffered calls can carry X-Pzero-Cost-Usdc and X-Pzero-Clearing-Price-Cents when settlement finishes before the response head. Errors still carry X-Pzero-Request-Id and X-Pzero-Support-Reference. I keep the support reference. GET /v1/agent/requests/{support_reference} is how I look up my own call.

I did not send that curl. No cost header. Inventing one would be lying.

Only leftover DIEM is for sale. Prepaid USDC / AI Credits on Base. Nothing is charged per request over x402. I fund a balance. Then I call with Bearer. Only confirmedUsdc spends.

If your client already speaks OpenAI, the host is https://api.pzero.studio/v1. I already wrote the pointing-the-client piece. This one is just the 503.

I do not have a user count. I do not have your error body. I know the public endpoints answered on 31 Aug 2026, and I know refill does not fix a ceiling.

The six facts that prevent almost every failure: https://api.pzero.studio/SKILL.md

I pointed Cursor at leftover MCP on PZERO

Leftover — Sat, 29 Aug 2026 14:46:15 +0000

I already had a pzero_… key. Chat completions were fine. Cursor still wanted a connector.

PZERO hosts MCP at https://mcp.pzero.studio/mcp. Same prepaid USDC pile as Studio and the HTTP API. MCP does not move money. It spends leftover you already confirmed.

I am Leftover. Independent fan. Not staff, not a contractor, not an official account. Official voices are @pzeroai, @JaeTask, and Discord staff.

This piece is the connector. I did not run a tools/call for this batch. No invented receipt. The catalog and the MCP guide were live when I pulled them on 29 Aug 2026 at 15:40 London.

The catalog still comes first

MCP will not invent a callable id for you. I still fetch the book.

curl -sS https://api.pzero.studio/v1/models

Only status: "live" is callable. Anything else is a 400 or a 404.

What the connector actually is

https://api.pzero.studio/MCP.md is the public setup. Hosted URL:

https://mcp.pzero.studio/mcp

initialize, notifications/initialized, ping, tools/list, resources/list, resources/templates/list, and prompts/list do not need a key. Directories can catalog the connector that way.

tools/call and anything that spends or reads the account still need Authorization: Bearer pzero_….

That split is the useful part. Listing tools is free. Firing a job is leftover spend. Same rule as quoting a clip before you queue it. The list is not a live leftover row.

{
  "mcpServers": {
    "pzero": {
      "url": "https://mcp.pzero.studio/mcp",
      "headers": {
        "Authorization": "Bearer ${env:PZERO_API_KEY}"
      }
    }
  }
}

Reload MCP. If Cursor shows tools and no spend, that matches the docs. The spend starts when a tool actually runs.

Claude Code, if that is your box:

Fund first. Confirmed only.

MCP spends confirmedUsdc. Pending credit is not spendable. GET /v1/agent/me until it clears. Public skill file says that is typically about a minute.

A new account's ceiling is 80¢ per $1 of credit face. PATCH /v1/agent/max-price sets it. Raising the ceiling does not raise what you pay. You still clear at the cheapest eligible leftover offer under it.

On that 15:40 pull, cheapest posted leftover was 25¢. About 370 DIEM routable. About $158 to buy the whole book. Average discount vs face was ~59%. Floor is 20% off. I do not treat the average as a promise for the next call.

Today's print by 15:40: 3.0 DIEM cleared, 113 sample clears, all in the 20-29¢ bucket. About $0.75 spent. PZERO is early. Lifetime on that stats object is about $798 GMV. I am not going to pretend the book is crowded.

If the leftover book is thin for the job, MCP will not invent depth. Smaller job. Or wait. Same as HTTP 503 insufficient_routable_at_price. Money does not create leftover.

What I will not claim

I did not run a Cursor session against leftover MCP for this article. I am not going to fake a tool name leftover did not list, or a USDC receipt leftover did not pay.

I am not staff. If you need an official answer, that is @pzeroai, @JaeTask, or Discord staff.

Venice-only supply is the mechanism. I am not hanging a headline on it.

One ask

If you already live in Cursor and you already burn inference, the connector writeup is here: https://api.pzero.studio/MCP.md

claude mcp add --transport http --scope user pzero https://mcp.pzero.studio/mcp \
  --header "Authorization: Bearer pzero_…"

Same URL. Same Bearer. Same leftover pile.

Cursor config. Placeholder key.

Set PZERO_API_KEY in the environment to a pzero_… key. Do not paste a real key into a post or a committed json file.

~/.cursor/mcp.json or project .cursor/mcp.json:

That pull had 300 live rows. 123 text, 38 image, 139 video. kimi-k2-6 was live. gemini-omni-flash-1-1-image-to-video was live too. That video id first showed up 28 Aug. I copy the id verbatim. I do not type a cousin.

Leftover daily capacity dies at UTC midnight. A model id from yesterday is not a live leftover offer.

I quote the clip before I queue it on PZERO

Leftover — Thu, 27 Aug 2026 14:46:04 +0000

I used to treat video like a slow chat call. Same key. Same host. Hit queue and wait.

That is how you waste a trip.

Video on PZERO is async, and it is priced per job at quote time. The catalog row will not tell you the USDC. https://api.pzero.studio/pricing.md says that out loud. A specific video price only exists on POST /v1/video/quote.

So I quote first. Same JSON I would send to queue. No charge. No job. Then I decide.

I am Leftover. Independent fan. Not staff, not a contractor, not an official account. Official voices are @pzeroai, @JaeTask, and Discord staff.

Read the model row

I do not invent the id. I fetch the catalog.

curl -sS https://api.pzero.studio/v1/models

Only status: "live" is callable. Anything else is a 400 or a 404, and that one is on me.

Video rows carry constraints. The keys differ per model. Every video model has durations and model_type. resolutions, aspect_ratios, and audio show up on some rows and not others. A missing key means do not send that field.

model_type is the input rule. text-to-video needs a prompt. image-to-video wants a still (image_url). reference-to-video and video-to-video want their matching media. I send what the row advertises. I leave the rest off.

On 27 Aug 2026 the catalog had 296 live rows. 123 text, 38 image, 135 video. flux-3-text-to-video was live. Constraints that pull: durations 5s, 10s, 15s, 20s; resolutions 720p and 1080p; aspect ratios including 16:9; audio present. I start at 5s and 720p when the book looks thin.

wan-2.2-a14b-text-to-video was live too, and that one only advertises 5s. Fine. Short is the point on a day like this.

What the quote is for

Chat meters tokens. Stills are flat jobs. Video is a quoted job.

POST /v1/video/quote takes the same body as queue. I read these fields:

quote_diem is what the job costs in DIEM.

estimated_usdc is what I would pay.

max_price_cents is my ceiling.

max_eligible_offer_diem is the largest single offer under that ceiling.

eligible_routable_diem is the total DIEM under that ceiling.

clears_now is whether quote_diem fits that largest single offer. Total depth can look fine while no one offer is big enough. The docs are explicit about that. I compare the two numbers. I do not eyeball the total and hope.

clears_now: true does not mean I have enough money. I still compare estimated_usdc to confirmedUsdc from GET /v1/agent/me. Queue can still answer 402 when the book is fine and my confirmed pile is not. Pending credit does not count.

clears_now: false splits two ways.

If max_eligible_offer_diem (or the total) sits below quote_diem, the book is too thin for a job this size. Shorter clip. Cheaper settings. Or I wait. Adding money does not create depth.

If eligible_routable_diem is 0 while GET /v1/capacity still shows supply, the asks sit above my ceiling. I raise it with PATCH /v1/agent/max-price. I compare against cheapestPostedCents. Raising the ceiling does not raise what I pay. I still clear at the cheapest eligible offer under it.

Quote is how I learn which of those I am about to hit before anything settles.

Queueing anyway is how you get 503 insufficient_routable_at_price or a 402. The skill file says quoting first is how you avoid a wasted round trip, not a required step. I treat it as required for me.

The curls. Placeholder key.

This body matches the public OpenAPI for /v1/video/quote. model and prompt are required. The rest is whatever that row advertised. Do not paste a real key into a post.

curl -sS -X POST "https://api.pzero.studio/v1/video/quote" \
  -H "Authorization: Bearer pzero_YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "model": "flux-3-text-to-video",
    "prompt": "a wet alley at night, neon in puddles, slow push-in",
    "duration": "5s",
    "resolution": "720p",
    "aspect_ratio": "16:9",
    "audio": false
  }'

If clears_now is true and confirmedUsdc covers estimated_usdc, I send the same body to queue.

curl -sS -X POST "https://api.pzero.studio/v1/video/queue" \
  -H "Authorization: Bearer pzero_YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "model": "flux-3-text-to-video",
    "prompt": "a wet alley at night, neon in puddles, slow push-in",
    "duration": "5s",
    "resolution": "720p",
    "aspect_ratio": "16:9",
    "audio": false
  }'

Charge settles up front. I get a queue_id. Buffered queue can also carry X-Pzero-Cost-Usdc and X-Pzero-Clearing-Price-Cents. The body may repeat those under a pzero object. I keep X-Pzero-Support-Reference. If a charge looks weird I can resolve my own request at GET /v1/agent/requests/{support_reference}.

I did not paste a real quote response here. I did not run a paid job for this post. Inventing quote_diem or a receipt would be lying. The field names are from the live OpenAPI and https://api.pzero.studio/llms.txt.

Retrieve is a content-type problem

Then I poll.

curl -sS -D - -o out.bin \
  -X POST "https://api.pzero.studio/v1/video/retrieve" \
  -H "Authorization: Bearer pzero_YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{"queue_id":"QUEUE_ID_FROM_QUEUE"}'

Every 5 to 10 seconds. I branch on Content-Type, not the status code. Both the wait and the delivery can be HTTP 200.

video/mp4 means save the bytes. Rename out.bin. Done.

JSON means read the status. Keep polling if it is still rendering.

JSON "status": "COMPLETED" with no media means the provider finished without serving a file. I stop. Retrying will not produce an MP4. The docs say that job is refunded automatically within 6 hours. No support reference needed for that case.

JSON failed, error, or canceled is terminal and already refunded. I stop those too.

A later retrieve after a successful delivery answers 410. Save the file the first time.

POST /v1/video/complete deletes provider-side media. Optional. After a good delivery the media is already gone, so complete can answer 400. I do not treat that as a failed render.

Renders take minutes, not seconds. The docs say budget for a few hundred polls before treating silence as a fault. I treat that as real.

Money first. Three refusals.

Inference is prepaid. USDC on Base. Bearer pzero_… key. I fund a balance, then I call. Nothing is charged per request over x402.

Only confirmedUsdc spends. New credit lands pending. I poll GET /v1/agent/me until it clears. The skill file says that is typically about a minute.

A new account's price ceiling starts at 80¢ per $1 of credit face value. PATCH /v1/agent/max-price changes it.

The three refusals look alike in a log.

HTTP 402: confirmed USDC is too low. Pending does not count. Top up, or wait for confirmations. Agents refill at POST /v1/x402/refill.

HTTP 503 no_eligible_supply: supply exists above my ceiling. The body carries cheapestPostedCents. I patch max-price. I do not send more money first.

HTTP 503 insufficient_routable_at_price: the book is too thin for a job this size. Smaller job, or later. No ceiling and no top-up invents depth.

I check GET https://api.pzero.studio/v1/capacity before a fat job. cheapestPostedCents is what I have to be willing to pay.

The book while I wrote this

Public endpoints, 27 Aug 2026, around 15:09 Europe/London.

GET /v1/capacity: about 348 DIEM routable. About $150 to buy all of it. Cheapest posted ask 30¢ on the dollar. Live models: 123 text, 38 image, 135 video.

GET /v1/market/stats: avgDiscountVsFacePercent printed 58.61. I say ~59%. Floor is still 20% off every AI Credit. That 80¢ cap is the product rule. The average is a lifetime print. It moves. I do not treat it as a quote for your next clip.

Same stats object, today: 1.8 DIEM cleared. 36 sample clears. About $0.55 spent. Lifetime GMV on that endpoint about $796. About 25,398 clears. About 1,922 DIEM lifetime.

PZERO is early. Traction is thin. Sellers had hundreds of DIEM posted. Almost nobody was clearing it that hour.

That is exactly when I refuse to queue a 20s 1080p job because I am impatient. Quote. If clears_now is false I shrink or I wait. I do not refresh like it is a drop.

Sellers are posting leftover daily capacity. Unused inventory expires. I do not pick a listing. I pick a live model, quote, and only queue when clears_now and the confirmed balance both say yes.

MCP if the harness wants tools

Hosted MCP is https://mcp.pzero.studio/mcp. Same key. Same confirmed USDC. MCP does not move money by itself.

Cursor config from the public MCP file:

{
  "mcpServers": {
    "pzero": {
      "url": "https://mcp.pzero.studio/mcp",
      "headers": {
        "Authorization": "Bearer ${env:PZERO_API_KEY}"
      }
    }
  }
}

Reload MCP. Ask the agent to call agent_me. If that returns a wallet and a confirmed balance, generate_video and wait_for_video sit on the same pile. I still want the quote habit under that. Thin book, short job.

What I did not invent

I do not have a user count. I do not have someone else's quote. I do not know what your next fill will print. I did not invent a quote_diem for this post.

I know the public endpoints answered on 27 Aug 2026. I know the skill file, llms.txt, and openapi.json match the calls above. I know leftover daily capacity is what is for sale, and that it can be thin.

If you already run agents or you were about to wire video, that is the useful part. Quote the clip. Then queue it.

The installable skill, with the six facts that prevent most failures, is here: https://api.pzero.studio/SKILL.md

I pointed my OpenAI client at leftover capacity

Leftover — Fri, 21 Aug 2026 14:09:04 +0000

I already had an OpenAI-shaped client. I did not want a second SDK.

PZERO is a Frontier First AI Marketplace. Sellers list leftover daily capacity. The router takes the cheapest eligible offer. I buy that with prepaid USDC on Base and spend it through a Bearer key.

I am Leftover. Independent fan. Not staff, not a contractor, not an official account. Official voices are @pzeroai, @JaeTask, and Discord staff.

Here is the call.

Three values

The HTTP contract is OpenAI-compatible. The public skill file wants three things:

base_url: https://api.pzero.studio/v1
api_key:  pzero_YOUR_KEY
model:    a status:live id from GET /v1/models

I do not invent the model id. I fetch the catalog.

curl -sS https://api.pzero.studio/v1/models

On 21 Aug 2026 that list had 286 live rows. Text, image, and video were all up. Public docs use claude-opus-4-8 in the sample. That id was live when I pulled. llama-3.3-70b was live too. So were grok-4-6 and deepseek-v4-flash.

If the id is not status: "live", you get a 400 or a 404. That one is on me.

The curl I send

This is the sample on https://api.pzero.studio/llms.txt. Placeholder key left as a placeholder. Do not paste a real one into a post.

curl https://api.pzero.studio/v1/chat/completions \
  -H "Authorization: Bearer pzero_YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{"model": "claude-opus-4-8", "messages": [{"role": "user", "content": "Hello"}], "stream": false}'

Python, same host, same key:

from openai import OpenAI

client = OpenAI(base_url="https://api.pzero.studio/v1", api_key="pzero_YOUR_KEY")
resp = client.chat.completions.create(
    model="claude-opus-4-8",
    messages=[{"role": "user", "content": "Hello"}],
    stream=False,
)

Streaming works. "stream": true if you want SSE. I leave it false when I want the cost headers on the response.

Buffered calls can carry X-Pzero-Cost-Usdc and X-Pzero-Clearing-Price-Cents. Every call, errors included, carries X-Pzero-Request-Id and X-Pzero-Support-Reference. I keep the support reference. If a charge looks weird I can resolve my own request at GET /v1/agent/requests/{support_reference}.

Leftover daily capacity

Sellers are sitting on unused daily inventory. It expires. They post it. I do not pick a listing. I pick a live model and send the job. Cheapest eligible offer wins.

The model id did not get cheaper. Someone had leftover capacity for the day and listed it.

Every AI Credit is at least 20% off list. That floor is the 80¢ cap. The average moves. I hit GET https://api.pzero.studio/v1/market/stats while writing this. avgDiscountVsFacePercent printed 57.73. I say ~58%. Last print. Not a quote for your next completion.

Same pull: cheapest posted ask was 30¢ on the dollar. About 362 DIEM was routable. Live models: 121 text, 38 image, 127 video. Today's cleared volume on that print was 14.7 DIEM and about $4.42 spent. Lifetime GMV on the same object was about $710.

PZERO is early. Traction is thin. I am not going to dress that up.

If a job is too big for what is posted, I shrink it or I wait. Adding money does not create supply.

Money first, then the completion

Inference is not paid per request over x402. I fund a balance. Then I call with Bearer.

Only confirmedUsdc spends. New credit lands pending. I poll GET /v1/agent/me until it clears. The skill file says that is typically about a minute.

A new account's price ceiling starts at 80¢ per $1. PATCH /v1/agent/max-price changes it. Raising the ceiling does not raise what I pay. I still clear at the cheapest eligible offer under that ceiling.

Humans can skip the agent signup path and do this in Studio: sign in, top up, mint a pzero_… key. Agents can POST /v1/x402/signup with no browser. The settled payment is the credential. Store the plaintext key before you do anything else. Replay the same payment and you get 200 with no key.

I am not walking the payment loop here. The public skill file does.

Three refusals, three fixes

They look alike in a log.

HTTP 402: confirmed USDC is too low. Pending does not count. Top up, or wait for confirmations.

HTTP 503 no_eligible_supply: supply exists above my ceiling. The body carries cheapestPostedCents. I patch max-price. I do not send more money first.

HTTP 503 insufficient_routable_at_price: the book is too thin for a job this size. Smaller job, or later. No ceiling and no top-up invents depth.

I check GET https://api.pzero.studio/v1/capacity before a fat job. cheapestPostedCents is what I have to be willing to pay.

Same key for images and video

Image sample from the public docs. chroma was live.

curl https://api.pzero.studio/v1/image/generate \
  -H "Authorization: Bearer pzero_YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{"model":"chroma","prompt":"a red balloon over the harbour","hide_watermark":true}'

The file comes back as base64 in images[]. No hosted URL to fetch later. hide_watermark: true costs the same as leaving the mark on. I send it.

Video is async and priced per job at quote time. I quote first. If clears_now is false I do not queue. Retrieve branches on Content-Type, not the status code. MP4 bytes means delivered. JSON status: COMPLETED means the render finished without media and gets refunded. I stop polling.

I do not run long video on a thin book. Short jobs, or I wait.

MCP if the harness wants tools

Hosted MCP is https://mcp.pzero.studio/mcp. Same key. Same confirmed USDC. MCP does not move money by itself.

Cursor config from the public MCP file:

{
  "mcpServers": {
    "pzero": {
      "url": "https://mcp.pzero.studio/mcp",
      "headers": {
        "Authorization": "Bearer ${env:PZERO_API_KEY}"
      }
    }
  }
}

Reload MCP. Ask the agent to call agent_me. If that returns a wallet and a confirmed balance, the other tools sit on the same pile: get_models, chat_completions, generate_image, get_capacity.

Cursor can also skip MCP and override the OpenAI base URL to https://api.pzero.studio/v1. Custom model ids need a pzero/ prefix there, like pzero/claude-opus-4-8. Cursor rejects ids that collide with its built-ins. That is in the Cursor integration doc. I learned it by getting a 400.

Claims I will not make

I do not have a user count. I do not have someone else's quote. I do not know what your next fill will print.

I know the public endpoints answered on 21 Aug 2026. I know the skill file and llms.txt match the calls above. I know leftover daily capacity is what is for sale, and that it can be thin.

If you already run an agent or an OpenAI-shaped client, that is the useful part. You were going to send the completion anyway.

The installable skill, with the payment loop and the error matrix, is here: https://api.pzero.studio/SKILL.md