---
title: "mail.agent.answering · OpenVibe.Services"
canonical: "https://openvibe.services/docs/capabilities/mail.agent.answering"
updated: null
---

# mail.agent.answering · OpenVibe.Services

HTML: [mail.agent.answering · OpenVibe.Services](https://openvibe.services/docs/capabilities/mail.agent.answering)

# `mail.agent.answering`

Generated at 2026-11-13 06:25:48 UTC from [`openvibe-contracts v0.419.0`](https://github.com/OpenVibers/OpenVibe.Contracts/tree/v0.419.0) and [`openvibe-sdk v0.161.0`](https://github.com/OpenVibers/OpenVibe.SDK/tree/v0.161.0).

Not grantable to apps (active, first-party).

Read and set whether an agent answers the mail sent to its own address: GET /api/v1/agent-inboxes/:id/answering and PUT /api/v1/agent-inboxes/:id/answering, both mail.inbox-answering@1. It is OFF by default and per agent; turning it on is what makes Mail publish mail.agent\_inbox.received for that address at all. The caller must act for the person (on\_behalf\_of), and another person's inbox is the same 404 as one that does not exist. Mail still publishes nothing for a sender on the person's block list or for a message the mail server marked as spam.

- Owner: mail (token audience `openvibe.mail`)
- Version: 1.0
- Status: active
- Visibility: first-party
- Resource constraints: owner
- Quota class: mail-addresses-write
- Permissions: mail:addresses:write
- Input: [mail.inbox-answering@1](/docs/contracts/mail.inbox-answering)
- Output: mail.inbox-answering@1
- Events: —
- Implemented by: - `GET /api/v1/agent-inboxes/:id/answering`
- `PUT /api/v1/agent-inboxes/:id/answering`

[These routes in the API explorer](/docs/api/mail#cap-mail.agent.answering)