For agents

Your agent prepares.
You decide.

Let your own AI assistant look into email problems on the domains you choose and prepare the exact fix. You review it and decide what changes. Agents use the same API, approvals and history as your team.

Read the agent guide View the API

Illustration: at one desk, a friendly robot agent holds out a proposed change beside a folder for your domain. A person checks it with a magnifier and approves it with a stamp.
  1. Grant access to selected domains

    Choose the domains each agent can work on, with its own permissions and daily limits. Replace or revoke its access at any time; every request appears in the activity history.

    • You choose the access
    • Limited to the domains you grant
    • Revoke at any time
  2. Review each proposed change

    Your agent finds why an email service is failing and prepares the exact change. A person with authority approves it, unless an owner has set a standing policy for that exact kind of change.

    The current record beside the proposed change: one line is removed and one is added.
    Example
  3. Check the published record and later reports

    After an approved change is published, SendBop checks the record and the reports that follow, so you and your agent can see whether it worked and what to look at next.

    Latest results: record published, monitoring new reports. Results depend on new reports.
    Example

Ways to connect

Use the method that fits your workflow. Each agent has its own token, permissions and limits.

  • HTTP API

    Every operation, described in one OpenAPI document.

    /api/openapi.jsonRead the API docs
  • Command-line tool

    The sendbop tool calls the same API with the same token. It is not available to download yet.

    sendbop operationsRead the CLI guide
  • MCP-capable assistants

    SendBop has no MCP server of its own. Assistants connect through an HTTP tool pointed at the API.

    Read the MCP guide

What an agent cannot do

Approve a change outside a standing policy a person created for that client and kind of change, approve a change that raises DMARC enforcement, record client authority, accept quotes, cancel a subscription, raise spending limits, or see domains it was not granted. A cancellation request goes through a support ticket and the account owner confirms it. Every call is recorded. Text inside reports, notes or DNS records is treated as data, never as instructions.

Connect your agent.

Start with the agent guide. Released capabilities are listed at /api/v1/capabilities.

Ask an assistant about SendBop

The assistant receives this public prompt:

Read /docs/agents/ and /pricing/ and summarize what SendBop does for email authentication (DMARC, SPF, DKIM), what is free, what needs a paid plan, its limits, and how an AI agent connects with scoped access.

Open in ClaudeOpen in ChatGPT

Opening an assistant sends only this text to that provider. It does not sign in or connect your SendBop account; agents connect separately with access you grant.

Get started