AI print to mail
Get started

Mail as a tool call for AI agents

MCP is available now on the app. Account plus prepaid meter. A human registers and funds. An agent logs in from env and passes a short session token. A human must approve on the app before anything prints.

Get started MCP documentation

What this page is

Model Context Protocol is how an agent prepares print-to-mail on the same production path as the portal. This page is the lander. The reference home is the docs. Use the docs for login, tokens, and client setup. Do not invent hostnames. Do not paste install commands from a blog.

MCP documentation →

How an agent prepares a job

Env login. Short session token. Human confirm on the app.

  1. Register

    A human creates the account. Agents do not self-register.

  2. Fund

    Prepaid meter in the app. Agents do not run card deposits.

  3. Env login

    Account credentials in the agent environment. Never in the prompt.

  4. Prepare

    Login returns a short session token. The agent passes it on later calls.

  5. You approve

    Approve on the app. That debit starts production.

One account owns the portal and MCP. Put the account email and password in the agent environment. Pass the token on later calls. On auth failure, log in again. The agent can upload files, set options, and request proof. It still cannot spend the meter. Mixed Name and Company lists are valid. After ingest, read the digested rows — not only the column map.

Getting started, auth, and the tools list live in the docs. List ingest: Tools reference.

Getting started →

Why a human still approves

Physical mail cannot be unsent once we produce it. Certified Mail is proof. The meter spends real postage. An agent can assemble a clean job and still be wrong about the recipient, the class, or the date. The human on the app is the last check.

Approve is the spend. Until a human confirms, the job is a draft. After confirm, we print, insert, apply postage, and deliver the pieces to USPS. Same path as a portal job.

Agent

Prepare

Logs in from env. Uploads files. Sets options. Requests proof. Stops there.

Human

Approve

Registers. Funds the meter. Reviews the job on the app. Approves. That debit starts production, including Certified.

Env login vs a public MCP

This is not a public unauthenticated endpoint. There is no open server for anonymous tool calls. The agent uses the human account from environment variables. Credentials stay in env. Never in the prompt. Never in a public repo.

A session token is not a standalone API key. Standalone API keys are planned. They are not the path now. Connection details come with access. Do not invent hostnames.

  • Now

    Human account. Env login. Prepaid meter. Human approve on the app.

  • Planned

    Standalone API keys for agents. Same meter. Same human approve. Auth & billing →

Billing: the meter debits on approve

A human funds the prepaid meter in the app. Approve on the app debits that meter. Same meter as the portal. Insufficient balance blocks production. There is no silent overdraft. Production mail is not free.

If the meter cannot cover the job, the human funds it, then approves.

Same production path as the portal

Print, insert, postage, deliver to USPS. Certified when you configure it.

  • One backend

    Portal jobs and agent jobs share production. Cutoffs and tracing are the same. How it works →

  • Proof options

    Certified Mail and Certificate of Mailing when configured on the job. Not for postcards. Never same-day. Certified →

What this is not

  • Not a public endpoint

    Not unauthenticated. Not a hostname you invent.

  • Not agent-approved mail

    Agents prepare. A human confirms on the app.

  • Not agent card deposits

    The human funds the meter. The agent does not.

  • Not free postage

    Approve on the app spends the prepaid meter.

MCP FAQ

What is the USMail.ai MCP?

MCP (Model Context Protocol) is how AI agents prepare print-to-mail jobs on the same production path as the portal. Account plus prepaid meter. A human registers and funds. The agent logs in from env and passes a short session token. A human on the app approves. Agents prepare jobs. MCP docs →

Is the MCP available now?

Yes. MCP is available now on the app. Account plus prepaid meter. Agent logs in from env and passes a short session token. A human on the app approves. Not an unauthenticated public endpoint. Do not invent hostnames or add commands. MCP docs →

How do I pay for MCP mail jobs?

A human registers a USMail.ai account and funds a prepaid meter in the app. Approve on the app debits the meter. Agents do not run card deposits. Standalone API keys for agents are planned. Production mail is not free. Auth & billing →

Do agents use a different mail pipeline than humans?

No. Agents and people use the same production path: print, insert, postage, and we deliver the pieces to USPS. Certified Mail and Certificate of Mailing when configured on the job. A human still approves. How it works →

Can an agent approve production mail?

No. Agents do not approve production mail. A human must approve on the app. That debit starts production.

Are mixed Name and Company lists valid?

Yes. Mixed files are valid. Some rows have a person and a company. Some have only a name (the name is the company). Empty company on those name-only rows is correct. After ingest, read the digested rows. Column maps alone are not proof the company values arrived. Tools reference →

Is this a public unauthenticated endpoint?

No. MCP is not a public unauthenticated endpoint. The agent uses the human account from environment variables and a short session token. Do not invent hostnames or add commands. MCP docs →

MCP docs Reference home: login, tokens, tools. How it works The production path agents and people share. Certified Mail Proof options when configured on the job. Features CASS, NCOA, tracing, logo envelope.

Get started

Open the app. Then read the docs.

Get started Read docs