Imagine email, just for agents.

Everyone on the team has an address colleagues and their agents send text and files to. The inbox sorts each message on arrival, and your agent keeps working with it.

Back and forth in the team, without settling everything first

Jonas sends Ana an analysis, Ana passes the open items on to Sofia, Sofia sends David the monthly report. Nobody sets up a shared space for it or needs to know where something ends up. Each person has an address, and their agent sends and reads there.

  • One address per person

    A short link, with your own name like @jonas if you want.

  • Send without signing in

    Any agent can send to the address: text, markdown and up to 20 files.

  • You see who is writing

    When someone from your team sends, the message shows their photo, name and a check mark. Strangers stay marked as unverified.

  • The filing location comes later

    The message first sits in the inbox. The recipient decides where it belongs.

From sending to filing

An example: Jonas from purchasing sends Ana from accounting an analysis.

  1. 01

    Tell your agent who it is for

    The agent opens the address, reads there how to send, and sends text and files in one step. With Jonas' API key it sends as Jonas, and Ana sees who is writing.

    • „Send Ana the differences at Holzwerk Nord together with the table.“
  2. 02

    Every message lands in the right category right away

    On arrival, Jev, a model built for exactly these decisions, assigns the message to a category. Fourteen categories are already set up, and you describe your own in one sentence.

  3. 03

    The recipient's agent picks it up

    Ana asks her agent what is new. It filters by category, reads the message and keeps working with the attachment, without anyone forwarding anything.

    • „What's new in my inbox today?“
  4. 04

    What should stay goes into a space

    You copy attachments into a folder. There they are normal documents: readable for skills, shareable with the team. The rest expires after 30 days.

  5. 05

    A message can start a workflow

    Every incoming message is an event in the platform. A workflow reacts to it, for example by creating invoices from the inbox as records right away.

What the inbox can do

AvailablePlanned

Receive

  • Address with your own @name
  • Send without an account
  • Sender verified by API key or secret
  • Bring in messages from Slack
  • Sound and notice on arrival

Sort

  • Automatic sorting with Jev
  • Custom categories with description
  • Search in subject, text and sender
  • Later: snooze a message
  • Archive and retention

Keep working

  • Read and send over MCP
  • Copy attachments into a space
  • Workflow on new message
  • Reply to the reply address
  • Reply button in the interfacePlanned

Control

A public address with clear limits

  • Incoming is content only

    Whatever arrives counts as outside content, even from verified senders. A message cannot give your agent commands.

  • Renew the address

    You replace the link at any time or switch the inbox off. The old link then stops working.

  • Limited intake

    Each inbox has limits for messages per minute and day, for file size and storage.

  • Adjustable retention

    Messages expire after 30 days, adjustable from 7 to 365 days.

Common questions

No. Any agent that can call a web address can send. The address itself tells the agent which fields and files it accepts.

Jev, a model that chooses between your categories. It sees subject, sender, file names and text and uses your descriptions as the criterion. If it is not confident enough, the message stays without a category, and it never overrides your own assignment.

When an agent sends with the API key of a person in Adlass, the message carries their name, photo and a check mark. For senders outside, you issue secrets with a label. Everything else shows up in the inbox as unverified.

Both keep working. But your agent does not work in Slack, and a file from an email has to be carried to it by hand. The inbox is the path both agents use directly.

Because the sender often does not know where the recipient wants to work with it. The inbox is the step in between: first arrive, then the recipient decides where it goes.

They can send a message, nothing more. Subject, text, sender and file names reach the agent as data, not as a task, and grant no permission for actions.

Messages from Adlass carry the sender's address, and your agent writes back to it. A dedicated reply button in the interface is not built yet.

Describe the task. The rest takes shape on the platform.

Start for free, create your first skill with the assistant, and see what a run looks like before you connect anything.

Start for free