DOCSAID · beta

Service status & API changes

DOCSAID publishes service notices and compatibility changes here. This page is updated manually; current availability is determined by actual request outcomes.

Service notices

No service incident has been published on this page.

A notice records the affected function, observation time in UTC, user action and recovery update. If your work is blocked, send the Request ID or operation ID through support. Keep the image and API key out of the message.

Current hosted model versions

Pin model_version in your integration. Compatibility changes and any announced retirement date are published here and linked from the API guide. No version retirement date has been announced.

Product and API changes

Member diagnostics and first-call workflow

The workspace now provides request lookup by operation ID, actionable failure reasons, key renaming, filtered usage export and inquiry history. A downloadable client prepares images and keeps retries tied to the original operation. Hosted model versions and free-beta billing remain unchanged. Full field details are available in the member reference.

Hosted API guide · Sign in for the complete integration reference

Planning an integration

The free beta provides no uptime or response-time SLA. Show a processing state, allow cancellation locally, and keep a manual recovery path for busy or uncertain requests. Published timings describe their stated test conditions; measure your own network path before setting a product deadline.

X-Error-Code distinguishes busy workers, rate limits, daily limits and uncertain results. Respect Retry-After when present, use bounded retries with backoff, and check usage before retrying uncertain results. A daily limit resets at 00:00 UTC.

See beta limits · Retries and errors

Service responsibility and contact

DOCSAID is the contact for hosted model access, account usage records, support and data requests: [email protected]. Authentication, hosting and analytics use external service categories described in the privacy policy.

Accounts currently belong to one person; project grouping, team roles and shared ownership are unavailable. Separate development and deployment keys by name and scope. For handover, create keys under the successor’s own account, update the application, verify requests, then revoke the old keys. Never share sign-in credentials; contact DOCSAID before relying on team administration.

Discuss your needs