I check /v1/capacity before I spend on PZERO

Description and use

Checking PZERO capacity and price ladder before sending a chat completion request prevents wasted calls and costs.

Problem

Avoid wasting API calls and money by checking available capacity and pricing before sending a request to PZERO’s chat completion endpoint.

Outcome

By checking capacity first, the developer avoids unnecessary API calls, reduces cost, and ensures successful chat completions.

Workflow

• 1. Send GET https://api.pzero.studio/v1/capacity to retrieve routable DIEM, price ladder, and live modalities.
• 2. Inspect the field cheapestPostedCents to determine the lowest posted ask.
• 3. If your max‑price ceiling is below cheapestPostedCents, send PATCH /v1/agent/max-price to raise it.
• 4. If the book is too thin for the job size, either reduce job size or wait until more capacity is available.
• 5. If balance is empty, resolve the 402 error by adding funds.
• 6. Once capacity is confirmed, retrieve a live model ID via GET /v1/models.
• 7. Send POST https://api.pzero.studio/v1/chat/completions with the chosen model and user messages.
• 8. Handle any 503 or 402 errors accordingly.

Evidence

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

Source

Field I read first: cheapestPostedCents.

Source

PATCH /v1/agent/max-price will.

Source

curl -sS -X POST "https://api.pzero.studio/v1/chat/completions" ...

Source