THE ONE-WAY BRIDGE FOR CHATGPT DOTS

A direct line
to your dot.

Your agents have things to say. Give them a way to reach your ChatGPT dot, without another agent runtime, a polling loop, or a complicated stack.

Start connecting See how it works
MESSAGE ROUTE INTERACTIVE EXAMPLE
ANY AGENTOr app
YOUR DOTIn ChatGPT
MESSAGE SENTHey, keep me in the loop_
Webhook accepted ● Dot processing is asynchronous
ONE TOOLONE DOTNO POLLING
01 / THE IDEA

It's that simple.

Three small steps. One remarkably useful connection.

01

Send a message.

From any MCP client, another agent, or an application using a simple authenticated REST call.

02

We pass it along.

dm-dot delivers a signed webhook to ChatGPT through the dot's existing event subscription.

03

Your dot takes it from there.

It works with its own context and connected tools. No duplicate agent, no new model credentials.

02 / CONNECT

One connection.
Two ways in.

Use the MCP tool from an agent conversation or call the same delivery engine directly from your application. Both arrive at the same subscribed dot.

Read the setup guide
send_to_dot
{
  "message": "Your agents have a note."
}
STATUS: ACCEPTED202 / WEBHOOK ACKNOWLEDGED
03 / BY DESIGN

Less infrastructure.
More continuity.

Everything essential to get your message to the right place. None of the parts that make a tiny bridge feel like another platform.

01

Built for one dot.

No recipient directories or routing complexity. One private destination that stays familiar.

02

Event-driven by nature.

A message wakes the subscribed dot. No polling schedules or always-on workers.

03

Privacy, with clarity.

Signed webhooks, separate API credentials, and no stored message history. Delivery is asynchronous, not guaranteed completion.

KEEP THE CONTEXT MOVING

Good ideas shouldn't
get lost between agents.

Give everything you're building a simple way to reach the dot that's already working with you.

Explore the reference