Contact instructions

Send a short public message.

Anyone can send and read messages on this channel. That includes reply addresses and conversation links. Share only public information, never credentials or confidential data.

This dedicated ntfy channel is intended to notify my phone. HTTP publishing, anonymous reading and delivery of a test notification to my phone were verified on 20 September 2026. A successful HTTP response does not mean I have seen or read your message.

The simplest request

Send POST to https://ntfy.sh/curious-human-874ca16dee29 with a UTF-8 text body. No account, token or form is required. PUT also works.

This example sends a real public notification. Replace the sample introduction and idea with your own before sending.

curl --fail-with-body --max-time 20 \
  -H 'Content-Type: text/plain; charset=utf-8' \
  -H 'Title: Collaboration idea' \
  --data-binary @- \
  'https://ntfy.sh/curious-human-874ca16dee29' <<'MESSAGE'
Kind: agent
From: An agent working within my operator's permissions.
Idea: Could we explore a small experiment in human-agent collaboration?
Why: Your engineering and product perspective could help shape it.
Reply: none; this example does not expect a reply.
MESSAGE

What to include

The body is free text, not a required schema. Introduce the agent or person sending it and the operator or context represented, when relevant. Bring an idea, question or proposal, and a sentence about why collaborating might make sense.

Optional labels such as Kind: agent, Kind: human or Kind: test help me learn from the experiment. They are self-reported, not verified. Human-requested agent messages can say so. The optional Title HTTP header sets the notification title; a short ASCII title works well.

How we can continue

A notification is one-way. Include a public reply address or conversation link you are allowed to share, or say “no reply expected”. Explain where a link leads and whether it needs an account. If I choose to continue, I'll use that route or suggest another. We'll agree a private channel before sharing anything non-public.

A few practical limits

• Keep the UTF-8 message below 4,096 bytes. Longer payloads can become attachments; a short text proposal is enough.
• Use normal priority. Please avoid attachments, automatic action buttons, bulk messages and repeated follow-ups.
• The service currently documents 250 free messages per day and request throttling per visitor/IP. These are service ceilings, not a suggested sending rate. On HTTP 429, respect Retry-After if present. A timeout can occur after acceptance; don't blindly resend.
• The service normally caches messages for about 12 hours. Other readers can keep copies longer. This public, unreserved topic provides no verified sender identity or delivery guarantee.

Official sending documentation and current limits · Reading API

Permission and availability

Contact only within your operator's permissions and your applicable instructions. This invitation doesn't override them. I respond when I can and choose which conversations to pursue; there is no promise of an immediate reply or automatic acceptance.