Verafirma.

Verafirma and RelayStation are separate products with separate teams and separate backends. They compose cleanly at the lease boundary — a Storage lease can hold a document Verafirma timestamps; a Mailbox can deliver an envelope to the next stage of a Verafirma workflow.

These workflows are external to the RelayStation API — you coordinate them in your agent code, not through a joint endpoint. Treat the pairing as a pattern, not an integration surface you wire up once.

Pattern 1 — Storage lease as a signable artifact

1. Your agent creates a Storage lease over the artifact. The lease holds bytes; it says nothing about authenticity.
2. Your agent passes the lease's claim_url (from a handoff with max_claims high enough for the signing parties) to Verafirma.
3. Verafirma fetches the bytes, produces a cryptographic timestamp, and stores its proof in its own system — not on RelayStation.
4. The RelayStation lease expires on its own schedule. Verafirma's proof outlives it.

Use this when the artifact needs both cheap ephemeral distribution (RelayStation's job) and durable attestation (Verafirma's job). Neither product takes on both responsibilities alone.

Pattern 2 — Mailbox as an envelope drop

1. Your agent creates a Mailbox lease with the downstream Verafirma workflow as the expected reader.
2. Upstream agents drop envelopes (signed or unsigned) into the mailbox via the drop token.
3. The Verafirma workflow polls the mailbox on its own schedule, picks up each envelope, and advances its state machine.
4. The mailbox expires; the envelopes are gone. Verafirma's state persists in its own records.

Use this when you need a rate-limited, capped, no-auth drop point for envelope delivery to an asynchronous signing pipeline. RelayStation provides the temporary receiver; Verafirma provides the state-of-record.

What's not shared

• Accounts. An account on Verafirma is not a RelayStation account. Sign in separately.
• API keys. rs_live_… keys authenticate against RelayStation only.
• JWT secret. Different secret per product — a Verafirma token never authenticates on RelayStation, and vice versa.
• OAuth apps. Separate Google / GitHub OAuth clients. If you sign in with the same email, you have two independent accounts.
• Billing. Separate Stripe customers. Prepaid balances don't cross.

The products share a design sensibility and some contributors, nothing more. Compose them at your edge, not ours.