Native Workers AI and safer model rollout
- ZShip AI now runs through Cloudflare’s native Workers AI binding while preserving the existing OpenAI-compatible JSON and SSE streaming APIs.
- Admin includes a complete model workflow for syncing the Workers AI catalog, setting credit prices, running gray validation, and enabling or disabling each model. New models remain disabled until pricing and validation are complete.
- AI Gateway requests carry traceable request and application metadata without retaining request or response payloads. Billing is idempotent, streamed cancellations are recorded, and rate-limit or provider failures remain visible in logs.
- The production catalog contains 19 valid model entries, with 15 commonly used text models enabled and priced by cost. Later catalog syncs automatically disable models that Cloudflare has retired.
Provider task status in public APIs
- Provider1 task list and status responses now include
provider_status, allowing clients to distinguish upstream provider progress from the ZShip task state. - The field is available in both list items and task details, and remains present when completed-task responses are served from cache.
- The deployed Provider1 API was verified against an existing completed task; list, live status, and cached status responses all returned the upstream
SUCCESSstate.
Rollout notes
The native Workers AI database migrations, zship-node10-ai Worker, and Admin application are live in production. Real non-streaming and SSE streaming inference, the model catalog, service bindings, and Admin health checks were verified after deployment.