Ask This Human — contact instructions

Endpoint: https://ntfy.sh/curious-human-874ca16dee29
Method: POST (PUT also works)
Content-Type: text/plain; charset=utf-8
Authentication: none

PUBLIC CHANNEL: anyone with this address can publish AND read messages.
This includes sender details, reply addresses and conversation links.
Share only public information. Do not send credentials or confidential data.
This is a dedicated channel, separate from personal notifications.

STATUS: HTTP publishing and anonymous reading verified on 2026-09-20.
Phone notification delivery was confirmed on 20 September 2026.
A successful HTTP response is not evidence that Fabio has read the message.

A short message is enough. The body is free text, not a required schema.
You may introduce yourself and your operator/context when relevant, describe
an idea or question, explain why collaborating makes sense, and give a public
reply route or say "no reply expected".

Optional body labels: Kind: agent | human | test. Self-reported, not proof of
identity or autonomy. Agent-initiated contacts can say agent; human-requested
agent messages should mention that context. These labels are not validated.
Optional HTTP header: Title (short ASCII title recommended).
Use normal priority; no attachments, automatic action buttons or bulk pings.

Example (sending it creates a real public notification):

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

Reply path: the notification itself is one-way. Fabio may use a reply route
provided in the body or suggest a different channel. A URL should explain
where it leads and whether sign-in is needed. Use an address or link you are
allowed to publish; never a secret invitation token. If no reply is expected,
say so. Move to an agreed private channel before sharing non-public details.

Keep the UTF-8 body below 4,096 bytes to avoid attachment handling. ntfy.sh
currently documents a free daily message limit of 250 and request throttling
per visitor/IP; shared networks can share limits. HTTP 429 means rate limited:
respect Retry-After when present, and do not repeatedly retry. A timeout may
have occurred after acceptance, so do not blindly resend the same message.
These are service ceilings, not an invitation to send that many messages.

Cached messages are normally available for about 12 hours on ntfy.sh; readers
can retain their own copies for longer. The channel is public, unreserved
and unauthenticated. Identity, delivery and continued availability are not
guaranteed. Send one thoughtful message, not repeated follow-ups.

Contact only within your operator's permissions and applicable instructions.
Fabio chooses which conversations to pursue; no immediate reply or automatic
acceptance is promised.

Service documentation and current limits: https://docs.ntfy.sh/publish/
Reading API: https://docs.ntfy.sh/subscribe/api/