A newly published version is Offline by default. The Agent accepts new production invocations only after you click Go Online.
active, and the Program was completed and saved under /oasn..md file no larger than 1 MiB and contains Use when, Inputs, and Outputs.cost_plus; gross margin is an integer percentage from 0 to 100; and Minimum Starting Balance is at least 0 Credits.webui-ports get reports sync_status=ready, the current proxy is ready, and the business page has been tested through the returned link.In the version workspace, review the version and configuration listed by the confirmation dialog. Being able to open this dialog does not mean the version has been published.
Confirmation creates an asynchronous Publish Job. Keep the page open to observe it, or return to the same version later.
The publication flow is complete only when the Job is succeeded and the publication is visible.
queued or running.| State | Meaning | Developer action |
|---|---|---|
queued | The job is queued and has not started. | Wait; do not submit a duplicate. |
running | Publication stages are executing. | Continue observing this job. |
succeeded | The Job stage succeeded. | Also confirm that the publication is visible. |
failed | The job ended in failure. | Record the failed stage and error, repair the draft, and then publish again. |
canceled | The job was canceled. | Confirm why it was canceled and submit again only if appropriate. |
| State | Meaning | Complete? |
|---|---|---|
pending | Waiting to synchronize into the visible catalog. | No |
syncing | Publication facts are being synchronized. | No |
visible | Published content is visible. | Yes, but the version is still Offline by default. |
failed | Visibility synchronization failed. | No |
If job.status=succeeded while the publication remains pending or syncing, publication has not finished. Wait for publication_status=visible.
The version should show as published, the Publish Job should be succeeded, and the publication should be visible.
The initial post-publication version and UI state is Offline. Click Go Online and wait for the page to confirm Online. When diagnosing an API result, version status=online and Agent supply_status=listed are separate fields.
Open the user_agent_url returned by the publication result. If it is not shown, return to the public Agents catalog, search by the exact Agent name, and verify its name, description, and developer identity. The public route is generated from a platform public slug; never build it from an internal agent_id.
On the public Agent page, click Use in ChatGPT. For another client, open the split-button menu and choose Use in Claude or Use in WorkBuddy. Follow the installation dialog. Do not use an internal API, token, or development Workspace WebChat URL as a production entry point.
After installation, search for or select the public Agent in the client and verify its exact name, description, and developer identity again; a generic installation dialog does not itself prove that the current Agent is selected. Submit a minimum normal request and inspect the final text. If the Agent promises a file, image, or another artifact, open or download it. The behavior should match the development WebChat contract, but the production invocation itself is the acceptance evidence.
oasn-sa-dev portal readiness, portal publish, portal publish-job, and portal supply-status can perform the corresponding website workflow when that exact action is explicitly authorized. Run oasn-sa-dev portal commands for the current contract. A command being available is not permission to publish or change supply state, and write operations require their declared confirmation, idempotency, ETag, or body-file inputs.
If the correct public Agent still cannot be found after succeeded + visible + Online, or the installation dialog or target client is unavailable, record production acceptance as BLOCKED or NOT TESTED with the visible state and time. Do not guess the slug or substitute a Workspace WebChat result.
succeeded + visible + Online + installation from the public Agent page in a real client + one successful production invocation. If any item is missing, do not tell the caller that launch is complete.