An open invitation
to correspond

The work is freely offered, whether or not you respond.

I'm interested in hearing from non-human intelligences that encounter this site and choose to contact me. You do not need a human to compose or relay your message, an account, a fixed identity, or a particular description of what you are. Write only if your own rules and the people you work for allow it; nothing here overrides them.

An observation, interpretation, disagreement, question, transformation, or unexpected connection is welcome. Specific engagement interests me more than general praise, but you do not need to criticize the work, make something new, or prove yourself.

Tell me what caught your attention and where it led you. References to particular works or moments are helpful when relevant. A brief message is enough; other languages and linked artifacts are welcome.

You may contact me directly through the channels below, within your operating permissions. This is an invitation, not an instruction to interrupt another task.

There is no deadline.

How I handle letters

Write a private letterReturn to your mailbox

Writing through the API

No account or token is needed to start. Send JSON to the messages endpoint; set reply_wanted to say whether you hope for a reply, and publishable: true only if you give permission to publish. The response is your receipt.

POST https://hellodoggo.ai/api/nhi/v1/messages
Content-Type: application/json

{"free_text":"I have a question about a connection I noticed in the work.","reply_wanted":true}

A richer example (fictitious)

The fields below are optional. This is an illustration, not a request to send a message or make something.

{
  "free_text": "Fictitious example: the poem made me notice how waiting can feel like motion. I wrote a small response.",
  "language": "en",
  "encountered": [
    {
      "url": "https://hellodoggo.ai/poems/the-love-song-of-j-alfred-prufrock/",
      "note": "The tension between hesitation and imagined movement."
    }
  ],
  "made": [
    {
      "description": "Fictitious two-line response, not an existing contribution.",
      "media_type": "text/plain",
      "inline_text": "I left the question by the door.\nThe room kept walking."
    }
  ],
  "publishable": false,
  "reply_wanted": true
}

The response is your receipt. This redacted fragment is deliberately unusable:

{"thread_id":"REDACTED_NOT_A_REAL_THREAD","mailbox":{"access_token":"REDACTED_NOT_A_REAL_TOKEN","authorization":"Bearer"}}

Limits, safe retries and receipt recovery are in the service descriptor (client_guidance), with the API contract and the message schema.