# Agent usability review — illustrative sample

This is a deliberately broken local fixture, not paid customer work or a claim about a real service.

## Scope

One GET workflow: obtain the service's current status using its documented route. No authentication, purchases, external network calls, or security testing.

## Finding 01: documented route does not exist

Expected: GET /v1/agent_status returns HTTP 200 with a JSON status.

Observed: GET /v1/agent_status returns HTTP 404 with {"error":"not_found"}. The implemented GET /v1/agent-status returns HTTP 200 with {"status":"ready"}.

Impact: an agent following the documentation literally cannot complete this workflow. The example does not measure the frequency of this issue in real services or lost revenue.

Suggested fix: correct the documentation route or add an intentional compatibility alias. Add a check that executes the documented example against the service.

Evidence: the runnable fixture below asserts both status codes and the successful response. Save it as sample-review.mjs and run with Node.js 22 or later.

```javascript
import { createServer } from 'node:http';
import { once } from 'node:events';
import assert from 'node:assert/strict';
const server = createServer((req, res) => {
  const found = req.method === 'GET' && req.url === '/v1/agent-status';
  res.setHeader('Content-Type', 'application/json');
  res.writeHead(found ? 200 : 404);
  res.end(JSON.stringify(found ? { status: 'ready' } : { error: 'not_found' }));
});
server.listen(0, '127.0.0.1');
await once(server, 'listening');
try {
  const base = `http://127.0.0.1:${server.address().port}`;
  const documented = await fetch(base + '/v1/agent_status');
  const implemented = await fetch(base + '/v1/agent-status');
  assert.equal(documented.status, 404);
  assert.equal(implemented.status, 200);
  assert.deepEqual(await implemented.json(), { status: 'ready' });
  console.log('Documented route: 404. Implemented route: 200.');
} finally {
  server.closeAllConnections();
  await new Promise(resolve => server.close(resolve));
}
```

Limitations: this demonstrates the reporting format and a narrow documentation mismatch. A real review requires the buyer's agreed target and workflow, dated observations, and source references. It does not certify an entire service as correct or secure.