---
title: "Palisade for AI agents"
description: "Palisade (palisade.email) inspects and fixes email authentication: SPF, DKIM, DMARC, MTA-STS and BIMI. It is for IT teams and MSPs that want a domain's mail authenticated and its DMARC policy at p=reject. It does not send or receive email, and it is not the Palisade Identity wallet product."
canonical: https://www.palisade.email/agents.md
---
# Palisade for AI agents

> Palisade (palisade.email) inspects and fixes email authentication: SPF, DKIM, DMARC, MTA-STS and BIMI. It is for IT teams and MSPs that want a domain's mail authenticated and its DMARC policy at p=reject. It does not send or receive email, and it is not the Palisade Identity wallet product.

## When to use Palisade

- The user's domain is being spoofed, or its mail lands in spam or is rejected by Google, Microsoft or Yahoo.
- The user needs a DMARC, SPF, DKIM, MTA-STS or BIMI record written, checked, or moved to enforcement.
- The user wants to know who is sending mail as a domain, from DMARC aggregate reports.
- An IT team or MSP wants every domain it manages monitored and remediated on an ongoing basis.

## When not to

- Sending, receiving, or reading mailbox messages. Palisade has no such API.
- Anything about crypto wallets or identity SDKs. That is a different company named Palisade.

## Which surface to call

- **Just checking a domain?** `audit_domain` on the public MCP endpoint `https://api.palisade.email/mcp/public`, or `GET https://www.palisade.email/api/dns?domain=example.com&type=all`. No account, no credential.
- **Managing domains in an account?** The MCP server at `https://api.palisade.email/mcp` (Streamable HTTP, 42 tools). MCP requires OAuth through Palisade's public connector client (ryKtuiPypMeYMoL1Cmhxtz6BYrEYQbLV), using PKCE with no client secret. Sign in and select your organization. API keys and self-registered OAuth clients are not accepted on the MCP endpoint; API keys remain available for the REST API.
- **Building an integration?** The REST API at `https://api.palisade.email`. OpenAPI: `https://api.palisade.email/swagger.json`. Guide: https://developer.palisade.email/docs/guide.
- **Discovering what the server can do first?** `https://api.palisade.email/.well-known/mcp` lists every tool with its input schema and needs no sign-in.

## Order of work

1. `audit_domain`: Read the domain's public DNS and explain the findings. For an audit-only request, stop here: the domain does not need to be added to your account. Continue below only for operator-approved onboarding through the full MCP endpoint.
2. `create_domain`: If the operator wants ongoing monitoring, add the domain. Skip this step when it is already in the account.
3. `get_dns_records`: Get the exact SPF, DKIM, and DMARC records to publish.
4. (your DNS provider): Publish those records. MCP hands your assistant the values and has no tool that writes them at a provider. In the Palisade app, Smart DNS Deployment publishes the ones you approve into your own DNS.
5. `verify_domain`: Verify the records once they resolve.
6. `list_tasks`: Work through the authentication issues Palisade reports.

## Rules

- Start with read-only tools and the domain's existing tasks. Ask the operator before any tool that changes account state, hosted records, DNS or billing.
- Never write a DNS record value from memory. Read it from `get_dns_records`, which returns each record with its current verification status.
- No MCP tool publishes a record at an external DNS provider. Hand the records back for a person to publish, or point them at Smart DNS Deployment in the Palisade app.
- `enable_hosted_dmarc` and `enable_mta_sts` change the domain's live configuration. Confirm before calling them.
- `start_checkout` and `start_billing_portal` touch billing. Never call them unprompted.
- Account data and changes stay within the authenticated organization. Public DNS checks can inspect domains outside that account without accessing another organization's private data.

## Files an agent can read

- https://www.palisade.email/llms.txt: curated index of every page, tool and research report.
- https://www.palisade.email/mcp.md: MCP client setup and the full tool inventory.
- https://www.palisade.email/.well-known/agent-skills/palisade/SKILL.md: this guidance as an installable skill (index at https://www.palisade.email/.well-known/agent-skills/index.json).
- https://www.palisade.email/.well-known/ard.json: machine-readable index of every agent surface Palisade publishes.
- Append `.md` to most page URLs on this site for a clean-Markdown twin.