Catches the mistakes coding agents repeat before they merge: a pull-request gate with no model call and no API key.
Short answer: Error responses adhere to standard JSON error schema. Every endpoint with its own error shape makes every client write its own parser.
Group: API and network robustness. Status: stable. Generated from the rule definitions; do not edit by hand.
Playground: https://brevio.pro/tools/agent-guard-playground?rule=R10.4
Structured error envelope: error responses adhere to standard JSON error schema.
Every endpoint with its own error shape makes every client write its own parser.
res.status(400).send('bad');
res.status(400).json({ error: { code: 'bad_request', message: 'name is required' } });
A person can silence one finding with brevio-core: ignore R10.4 -- reason on the line or the line above. Without the reason it does not count. An agent cannot silence it: the agent hook and the MCP tools never honour the comment, and a pull request that adds one is reported until a reviewer allows it. Fixing the code is still the better answer.
To change what the rule flags, edit its definition in dev_rules.py or code_rules/__init__.py. That is a code change and is reviewed like one.