When an operation continues after the request returns, give the client a stable job identifier and a way to inspect progress. “Accepted” describes receipt, not successful completion.
Implementation steps
- Document the status endpoint and its authentication requirements.
- Distinguish queued, running, completed, and failed outcomes where supported.
- Make the final result or failure explanation retrievable.
- Avoid starting duplicate work merely because the first response took time.
Agent Friendly’s assessment API exposes job and run resources. An agent should follow the existing job to its result rather than interpreting the initial acceptance as a finished website assessment.
A check you can run
Submit a test job and record each observed state until completion or failure. Confirm the client reports the final outcome rather than celebrating the initial response.
Download preview image