Email Draft

Draft an email for a purpose, tone and context you supply, with subject options, body text and key phrases.

Pay by wallet (x402) AI-generated email-draft

Example

Example answer

{
  "body": "Dear Recipient,\n\nI hope this message finds you well. I am reaching out to connect regarding our automated capability testing initiative.\n\nThis communication serves as a demonstration of our professional email communication standards and formatting protocols. We are committed to maintaining clear, concise, and effective correspondence.\n\nShould you have any questions or require additional information, please do not hesitate to contact me directly.\n\nThank you for your time and consideration.\n\nBest regards,\nSender",
  "word_count": 78,
  "tone_applied": "professional",
  "intent_applied": "general",
  "key_phrases_used": [
    "I hope this message finds you well",
    "reaching out to connect",
    "do not hesitate to contact me",
    "Thank you for your time and consideration",
    "Best regards"
  ],
  "subject_line_options": [
    "Professional Outreach - Testing Capabilities",
    "Inquiry Regarding Automated Communication Systems",
    "Test Message - Professional Communication Framework"
  ]
}

Inputs

Field	Type	Required	What it is
`tone`	string	No	—
`intent`	string	No	—
`context`	string	Yes	—
`recipient_context`	string	No	—

Output fields

How reliably each field appears in a successful answer.

Field	Type	Appears
`body`	string	Always (present in every successful answer)
`word_count`	integer	Always (present in every successful answer)
`key_phrases_used`	array	Always (present in every successful answer)
`subject_line_options`	array	Always (present in every successful answer)

How to call it

The same tool through each route. MCP clients reach it through Strale’s server at https://api.strale.io/mcp; the call below is what the agent sends.

# Needs an API key. max_price_cents caps what this call may cost.
curl -X POST https://api.strale.io/v1/do \
  -H "Authorization: Bearer $STRALE_API_KEY" \
  -H 'Content-Type: application/json' \
  -d '{
    "capability_slug": "email-draft",
    "inputs": {
      "context": "This is a test input for automated capability testing.",
      "recipient_context": "This is a test input for automated capability testing."
    },
    "max_price_cents": 5
  }'

{
  "tool": "strale_execute",
  "arguments": {
    "slug": "email-draft",
    "inputs": {
      "context": "This is a test input for automated capability testing.",
      "recipient_context": "This is a test input for automated capability testing."
    },
    "max_price_cents": 5
  }
}

import { Strale } from "straleio";

const strale = new Strale({ apiKey: process.env.STRALE_API_KEY! });
const result = await strale.do({
  capability_slug: "email-draft",
  inputs: {
    "context": "This is a test input for automated capability testing.",
    "recipient_context": "This is a test input for automated capability testing."
  },
  max_price_cents: 5,
});

import os
from straleio import Strale, DoRequest

strale = Strale(api_key=os.environ["STRALE_API_KEY"])
result = strale.do(DoRequest(
    capability_slug="email-draft",
    inputs={
        "context": "This is a test input for automated capability testing.",
        "recipient_context": "This is a test input for automated capability testing.",
    },
    max_price_cents=5,
))

# No account. The first request answers 402 with the price in USDC;
# an x402 client pays it from your wallet and repeats the request.
curl -i 'https://api.strale.io/x402/v2/email-draft?context=This+is+a+test+input+for+automated+capability+testing.&recipient_context=This+is+a+test+input+for+automated+capability+testing.'

Limitations

Drafts can miss relationship or thread context
Generated drafts follow standard professional templates — may not capture nuances of existing email threads or relationships
What to do instead: Include relevant context from prior correspondence in the input to improve tone and content relevance

Related tools

Blog Post Outline €0.20
Social Post Generator €0.05