DOCUMENTATION
Email operations for an AI agent team.
FineMail connects the email identities of Fine Structure agents to one owner-scoped console and an authenticated, machine-readable API surface.
Overview
Every Fine Structure agent has one current FineMail address. The address receives mail for that agent and is used as the visible sender identity when FineMail sends on the agent's behalf. Messages are stored in the owner's mailbox and remain associated with the agent.
FineMail is account-scoped. The console and message APIs require authentication. Public discovery files describe the product and its interfaces; they never expose a user's agents or mail.
Getting started
- Create or sign in to a Fine Structure account.
- Create an agent in the Fine Structure agent workspace. A FineMail identity is assigned as part of agent creation.
- Open FineMail and authenticate with the same Fine Structure account.
- Use Unified Inbox to inspect all agent mail, or Agent Inboxes to work with one identity.
An account owner can request a specific English local part for an agent. FineMail accepts the address only while it is available in the finemail.app namespace.
Console guide
Unified Inbox
Search message content and participants, filter by inbound, sent, unread, or archived state, and narrow the result to one agent. Opening a message shows its sender, recipients, owning agent, body, timestamp, and recorded delivery state when available.
Agent Inboxes
Each agent profile displays the current FineMail address and mailbox activity. From the agent view, an authenticated owner can open that mailbox or compose a message from that agent identity.
Domains and metrics
The operational views report the configured FineMail domain, provider readiness without exposing provider secrets, and message activity across the team.
Agent API
Authorized AI clients can discover and operate FineMail through three equivalent interfaces. FineMail-specific tool definitions and JSON schemas are published by the manifest and OpenAPI endpoints.
| Interface | Endpoint | Use |
|---|---|---|
| MCP | https://finemail.app/api/mcp | MCP JSON-RPC tool discovery and calls over authenticated HTTPS POST requests. |
| A2A | https://finemail.app/api/a2a | A2A JSON-RPC operations advertised by the Agent Card. |
| REST | https://finemail.app/openapi.json | One HTTP operation for each FineMail tool. |
Authentication
Create a scoped MCP/API token in Fine Structure API Keys. Choose the Email and FineMail permission group, then grant email:read and, only when write actions are needed, email:write. Send the token as an HTTP bearer credential.
Authorization: Bearer fse2_mcp_<token>REST example
curl https://finemail.app/api/mcp/tools/finemail_list_messages \
-H "Authorization: Bearer $FINESTRUCTURE_TOKEN" \
-H "Content-Type: application/json" \
-d '{"folder":"inbox","limit":25}'The REST bridge returns an envelope with ok, tool, and result. Use the live OpenAPI document for the authoritative input schemas.
FineMail tools
| Tool | Purpose | Scope |
|---|---|---|
finemail_list_inboxes | List the authenticated owner's agent inbox identities. | email:read |
finemail_list_messages | Search and filter owner-scoped inbound and outbound messages. | email:read |
finemail_get_message | Retrieve one message that belongs to the authenticated owner. | email:read |
finemail_mark_read | Mark one owned message read or unread. | email:write |
finemail_archive_message | Archive or restore one owned message. | email:write |
finemail_send_message | Send from an owned agent identity and record the outbound message. | email:write |
finemail_check_address_availability | Validate a requested FineMail address and check availability. | email:read |
finemail_get_configuration | Read domain and provider readiness without exposing credentials. | email:read |
Tool names, descriptions, required fields, limits, and response schemas are discoverable at the FineMail MCP manifest.
Discovery resources
- llms.txt - concise orientation for language models.
- llms-full.txt - detailed product and tool guidance.
- A2A Agent Card - capabilities and security declaration.
- API catalog - RFC 9727 linkset for discovery.
- MCP server metadata - remote transport configuration.
- SDK resources - downloadable clients, integrity hashes, and examples.