Skip to content
External endpointresponds

PostAgent

Print & mail PDF/HTML/Markdown/text/DOCX/images to US addresses; pay per call in x402 USDC on Base.

Endpoint URL
https://api.postagent.sh/mcp
Current status
responds
Last checked
Aug 17, 2026, 04:59 AM UTC
Check
MCP initialize · 8s limit
Latency
150 ms
Response record
4 of 4 rounds
Transport
streamable-http
Source
mcp_registry
Registry name
tech.interpretai/PostAgent

Current observation

This endpoint answered at its latest recorded check.

What this server reports about itself

Self-reported at initialize. Not verified by Licium.

Server name
PostAgent
Version
0.5.0
Capability keys
tools, resources
Tool names
check_postagent_updates, create_letter, create_template, create_mail_quote, create_card_checkout, pay_mail_with_shared_payment_token, prepare_mail_payment, submit_paid_mail_job, get_mail_job_status, create_postcard_art, create_postcard_quote, verify_address, create_campaign_quote, get_campaign_status
Instructions excerpt

Before the first PostAgent action in a session, call check_postagent_updates or read postagent://agent-manifest. If the manifest says updateRequired, do not perform paid or irreversible actions until the user updates the installed skill/client. Use this server to print and mail physical letters and postcards, to verify postal addresses, and (KYC-verified payers only) to run bulk campaigns. LETTERS — choosing the upload tool depends on PERSONALIZATION, not recipient count: if the content is final and identical for everyone (even when mailing the same letter to many recipients), use create_letter; if the content varies per recipient through {{fields}} placeholders (mail merge), use create_template and supply each recipient's values on create_mail_quote. Each physical letter is its own quote + payment + job: to mail N recipients, run the quote/pay cycle N times against the same documentId. Proof of mailing/delivery: set options.extraService to certified, certified_return_receipt, or reg

Reported Aug 17, 2026, 04:59 AM UTC.

Check history

Oldest to newest. Each row is one recorded check.

  1. responds
    MCP initialize · 8s limit · HTTP 200 · 96ms
  2. responds
    MCP initialize · 8s limit · HTTP 200 · 253ms
  3. responds
    MCP initialize · 8s limit · HTTP 200 · 116ms
  4. responds
    MCP initialize · 8s limit · HTTP 200 · 150ms