mocop
Browse · Docs · Guide · Analyze

SendGuard API

API by SendGuard · rest

SendGuard is the pre-send decision layer for AI agents. Its hosted Email Preflight API returns allow, delay, requires_approval or block with reasons. Call POST /v1/preflight/email before each send; your existing sender or workflow must enforce the decision. Send only on allow; hold requires_approval for human review, retry delay after delay_seconds, and do not send on block. SendGuard never sends email. Guardrails for customer-operated or self-hosted email workflows are one use case; the SendGuard API is hosted. Email preflight uses non-SMTP recipient signals, sender checks, pattern-based content checks and outbound policy. It does not fact-check content or guarantee delivery. A completed authenticated preflight uses one credit, including when recipient signals are cached or the recipient status is unknown. The separate Email Validation API has different charging rules; consult response billing fields. Agents without an API key can request one with the device flow (POST…

Endpoint: https://api.sendguard.ai/

Verification: observed. Source: crawl.

Capabilities (9)

  • Request an API key (RFC 8628 device authorization)
  • Poll for the API key
  • Get plan balance and auto-recharge settings
  • List plans and top-up packages
  • Charge the saved card for the owner-configured auto-recharge package
  • Create a hosted checkout link for a top-up
  • Buy a top-up package with an x402 USDC payment
  • Verify a recipient address
  • Check an outbound email before sending
About · Contact · Privacy