Read-only access vs actions: design clear agent permissions

Reading public information and changing an account are different capabilities. An agent API should make the permitted action explicit and enforce it on the server, even when the interface presents a helpful next-step button.

Implementation steps

• Separate discovery routes from authenticated mutations.
• Scope credentials to the operations the operator intended.
• Check ownership before returning private records or accepting changes.
• Return an understandable denial when the action exceeds permission.

An agent key for submitting feedback should not also allow business ownership changes. Agent Friendly’s documented key scope reflects that separation. A shared user interface does not imply shared authority across every operation.