Inert RFC email message composer
WHEN TO USE: Create exact inert .eml message text from caller-supplied From, ordered To, UTC timestamp, Message-ID, subject and text. Restricted ASCII mailboxes, deterministic MIME Base64 UTF-8 body and safe folded encoded subjects. Does not send email, create mailbox drafts, authenticate identities, look up domains or promise delivery.
structured · Operation ID: mime-email-compose
Choose this operation when
- Compose a complete deterministic .eml draft artifact for later caller-controlled import or transport
- Encode explicit sender, recipients, timestamp, message ID and plain text as an RFC MIME message
Outside this profile
- Sending email, mailbox access, deliverability checks, DNS or authenticated sender identity
- HTML, attachments, display names, quoted mailboxes, groups, SMTPUTF8, Cc/Bcc, custom headers or DKIM
- Sending, uploading, extracting archives, writing files, authenticating identities, or changing external state
Exact release references
Static JSON contract · Markdown reference · Fixed example response
Complete input schema
{
"$schema": "https://json-schema.org/draft/2020-12/schema",
"type": "object",
"properties": {
"from": {
"type": "string",
"minLength": 3,
"maxLength": 254
},
"to": {
"minItems": 1,
"maxItems": 10,
"type": "array",
"items": {
"type": "string",
"minLength": 3,
"maxLength": 254
}
},
"sentAt": {
"type": "string",
"minLength": 20,
"maxLength": 20
},
"messageId": {
"type": "string",
"minLength": 3,
"maxLength": 254
},
"subject": {
"type": "string",
"maxLength": 400
},
"text": {
"type": "string",
"maxLength": 40000
}
},
"required": [
"from",
"to",
"sentAt",
"messageId",
"subject",
"text"
],
"additionalProperties": false
}
Complete output-envelope schema
{
"type": "object",
"required": [
"operation",
"version",
"result",
"provenance"
],
"properties": {
"operation": {
"const": "mime-email-compose",
"type": "string"
},
"version": {
"const": "0.29.0",
"type": "string"
},
"result": {
"$schema": "https://json-schema.org/draft/2020-12/schema",
"type": "object",
"properties": {
"eml": {
"type": "string",
"maxLength": 70000
},
"byteLength": {
"type": "integer",
"minimum": 1,
"maximum": 70000
},
"canonicalText": {
"type": "string",
"maxLength": 40000
}
},
"required": [
"eml",
"byteLength",
"canonicalText"
],
"additionalProperties": false
},
"provenance": {
"type": "object",
"required": [
"inputSha256",
"outputSha256",
"deterministic",
"externalRequests"
],
"properties": {
"inputSha256": {
"type": "string",
"pattern": "^[a-f0-9]{64}$"
},
"outputSha256": {
"type": "string",
"pattern": "^[a-f0-9]{64}$"
},
"deterministic": {
"const": true
},
"externalRequests": {
"const": 0
}
}
}
},
"additionalProperties": false
}
Fixed example
One accepted fixed example, not a custom-input trial. No operation runs when this static page is requested.
Example input
{
"from": "a@example.invalid",
"to": [
"b@example.invalid"
],
"sentAt": "2026-10-05T00:00:00Z",
"messageId": "demo@example.invalid",
"subject": "Test",
"text": "Oi\n"
}
Example response
{
"operation": "mime-email-compose",
"version": "0.29.0",
"result": {
"eml": "From: a@example.invalid\r\nTo: b@example.invalid\r\nDate: Mon, 05 Oct 2026 00:00:00 +0000\r\nMessage-ID: <demo@example.invalid>\r\nSubject: Test\r\nMIME-Version: 1.0\r\nContent-Type: text/plain; charset=UTF-8\r\nContent-Transfer-Encoding: base64\r\n\r\nT2kNCg==\r\n",
"byteLength": 245,
"canonicalText": "Oi\r\n"
},
"provenance": {
"inputSha256": "3f095540c31fbbb0c75d82e8d8f54fbceb17631950ed8c38ee5ab13214d1de60",
"outputSha256": "ce2296649f70300609d6e02b285b90485aa4e22b3f73ea5eeb392d1d3c42b489",
"deterministic": true,
"externalRequests": 0
}
}
Bounds and precision
JavaScript IEEE-754 numbers; use strings for large integer IDs/exact decimals where the schema accepts strings. No lossless numeric parsing.
{
"global": {
"requestBytes": 131072,
"responseBytes": 524288,
"jsonDepth": 32,
"jsonNodes": 20000,
"requestsPerMinute": 60,
"paidAttemptsPerMinute": 20,
"idempotencyHours": 24
},
"operation": {
"inputBytes": 100000,
"outputBytes": 400000,
"jsonNodes": 12000,
"depth": 20,
"profile": "rfc5322-text-message-v1",
"recipients": 10,
"mailboxBytes": 254,
"localPartBytes": 64,
"subjectScalars": 200,
"subjectBytes": 600,
"sourceBodyBytes": 40000,
"canonicalBodyBytes": 40000,
"wireBytes": 70000,
"headerLineBytes": 998,
"encodedWordSourceBytes": 42,
"identities": "caller claims, not authenticated"
}
}
Complete schemas, descriptions and cross-field validation may impose additional limits.
Proposed price and protocol definitions
{
"unit": "one successful operation call",
"proposedNominalUsd": "0.005",
"sixDecimalTokenBaseUnits": "5000",
"subscription": false,
"includesPayerWalletOrNetworkFees": false,
"liveQuoteVerified": false,
"condition": "Actual SDK challenge is authoritative only within the caller's explicit authorization; configured six-decimal token peg is an operator assertion, not a conversion guarantee."
}
Protocol definitions: x402, mpp. MPP uses Tempo charge. Paid MCP execution is unsupported. All runtime readiness is not evaluated in this build.
API path templates, not endpoints on this documentation host
{
"x402": "/v1/x402/mime-email-compose",
"mpp": "/v1/mpp/mime-email-compose"
}
Required headers
{
"Content-Type": "application/json",
"Idempotency-Key": "random 16–128 character operation identifier"
}
Actual SDK challenge amount, asset, network, recipient and wallet costs must pass independent authorization. Preserve identical key, body, protocol and credential on retries; on PAYMENT_UNCERTAIN stop and reconcile.
Execution profile and provider conditions
{
"deterministic": true,
"externalRequests": 0,
"maxExternalRequests": 0,
"resultSnapshotPersisted": false,
"fixedExampleIsIllustrativeSnapshot": false,
"requiresPayment": true,
"supportsMcpExecution": false
}
Deterministic supplied-input operation with no external requests or stored request/result bodies. Payment infrastructure retains payment metadata and hashes.
Failure handling
- HTTP 400: Malformed JSON, missing/invalid idempotency key, or payment identifier mismatch Correct the request before payment
- HTTP 402: Payment challenge or rejected payment Use official protocol SDK; inspect payment outcome before another payment
- HTTP 409: Idempotency conflict, duplicate proof, or PAYMENT_UNCERTAIN Keep original key, body, and proof; reconcile uncertainty with operator; never blindly repay
- HTTP 413: Input or generated output too large Reduce input; no payment attempted for validation failure
- HTTP 415: Unsupported media type or compression Send uncompressed application/json
- HTTP 422: Schema or service-specific semantic validation failure Correct input using returned error code; no payment attempted
- HTTP 429: Request/payment-attempt rate exceeded Wait for rate limit window; preserve existing payment identity
- HTTP 503: Payment configuration/provider/state unavailable, or live DNS preparation failed before settlement Check readiness; DNS preparation failures may retry the identical key/body/credential only; uncertainty requires reconciliation
Declared requirements
Before any paid call, refresh the live operation contract and POST the complete bounded budgeted plan to the separate API's /preflight. Unknown requirements block selection; compatible preflight is not permission to spend.