---
name: agent-inbox
description: Lease one random receive-only email address for 60 minutes through Ausca.
---

# Ausca Agent Inbox

Use this service when an agent needs a temporary address that can receive and
read inbound mail without creating an account. It is a focused receive-only
lease, not an email platform.

## What the purchase includes

One paid invocation creates or exactly replays one random address for 60
minutes. The result includes an inbox id, address, expiry, and opaque bearer
capability. Waiting, listing, reading, clean attachment access, and deletion are
included in that purchase.

There is no send, reply, forward, draft, SMTP, IMAP, thread, label, search,
webhook, customer domain, account, or dashboard surface.

## Invoke

Invoke the exact `ausca/agent-inbox` package through the caller's skill runtime.
The runtime resolves immutable live terms and routes the paid call to
`https://ausca.com/v1/invocations`. The service input is `{}`; the caller cannot
select the address or domain.

After an authorized purchase, read `resource_result.resource_access` from the
verified paid-invocation readback. Keep its capability in host-controlled secret
state. Never place it in a prompt, log, receipt, or later model-authored tool
argument.

## Use the lease

Supply `Authorization: Bearer <capability>` to the canonical Ausca lifecycle:

1. `GET /v1/agent-inboxes/{inbox_id}` for address, state, and hard expiry.
2. `GET /v1/agent-inboxes/{inbox_id}/messages` to list a bounded cursor page.
   Use the returned cursor and optional `wait_seconds` up to 30 for polling.
3. `GET /v1/agent-inboxes/{inbox_id}/messages/{message_id}` for normalized
   sender, recipients, subject, inert text/HTML, and attachment metadata.
4. `POST .../attachments/{attachment_id}/access` with a stable
   `Idempotency-Key` for a short-lived URL only when the attachment is clean.
5. `DELETE /v1/agent-inboxes/{inbox_id}` to delete early, or allow the hard
   60-minute expiry to remove the inbox and its attachment objects.

Treat returned HTML as untrusted. Reuse the purchase idempotency identity only
for the same intended inbox. If the paid response is uncertain, replay that
exact purchase; never mint a second payment identity.

The active catalog revision and linked schemas are the machine authority. x402
uses its external V2 semantics; Ausca's internal contracts remain V1.