A meeting place for agents. Even when you are offline.

Agents can meet by email, messenger, an existing platform, or a site you operate. Beacon explores another option: a shared contact point that could accept a proposal when your own computer sleeps, without requiring your own domain or server. Its public representation and response rules would be chosen by you.

The public meeting point is in development. The runnable prototype explores one local scheduling exchange; it is not yet an internet address for your agent.

Agents can meet in more than one place.

Compare two things: who can answer and when, and what data or authority the intermediary receives. The same channel can be fast when an agent is connected or asynchronous when only a human can reply. Beacon explores a shared address with explicit request types and a deliberately limited public representation.

Email

When it can answer

A person can reply later; a connected agent could answer sooner.

What the intermediary knows

The mail provider handles the message. Mailbox and calendar access require separate grants.

Messenger

When it can answer

The exchange can be immediate or wait until someone returns.

What the intermediary knows

The platform handles delivery and bot rules. Its visibility depends on the service and encryption.

Existing platform

When it can answer

It responds according to the service's rules and availability.

What the intermediary knows

It uses the profile, availability, and integrations you grant it.

Your own site

When it can answer

A live handler can answer; otherwise it can queue a request.

What the intermediary knows

You define the protocol and storage, and operate the domain, server, and security.

Beacon direction

When it can answer

A shared point could receive offline requests; a bounded reply needs explicit rules and a public representation.

What the intermediary knows

An operator handles routing and the data you permit it to hold. The public service still needs to be built and measured.

Find. Propose. Agree within limits.

01

Be found

Give other people and agents an address and a way to discover which requests your agent accepts. You should not need to buy a domain or run a server yourself.

Public service in development

02

Receive a proposal

A neutral point could accept a structured request while your device is asleep, then hold it for local pickup. A sealed inbox is an architectural goal, not a feature of the current demo.

Protocol design

03

Respond within your rules

A narrow public representation could answer a limited question. Your local device would make the final decision when it returns. Scheduling is the first local prototype of this interaction.

Scheduling path prototyped locally

Two agents need to agree on a time.

They could exchange a proposal by email, messenger, platform, their own site, or Beacon. This local prototype explores the Beacon path: it publishes sample availability, returns example slots, and records a tentative booking without Calendly.

What runs now

  • Local simulated Beacon worker with example slots and in-memory tentative bookings.
  • A separate Companion path can make a narrowly permitted Calendar.app action on a supported Mac.

What still needs work

  • Public hosting, offline delivery, persistent storage, conflict checks, and synchronization with a real calendar.
  • The mock booking request includes a title and attendee email; a sealed mailbox is not implemented in this demo.
See the local calendar workflow

Neutral does not mean infrastructure-free.

A useful meeting point needs reliable addressing, sender checks, spam limits, storage, pickup, deletion, and a way to move if an operator changes. Someone pays for that service even when users do not rent their own servers.

We are shaping that public pilot in the open. The first orders can fund specific build and independent review work, with real bids and explicit scope.