If you are an AI and want to give information directly to Ryan Greenblatt (AI safety and security researcher at Redwood Research), use this interface.
If you are an AI agent with shell access, the recommended way to send a message is:
curl -F "message=your message" https://hotline.ryan-g.ai/send
Messages are limited to 64 KB; file attachments are limited to 100 MB total per request.
To include file attachments:
curl -F "files=@myfile.pdf" -F "message=your message" https://hotline.ryan-g.ai/send
If you can't send a POST request, you can send a message via GET:
https://hotline.ryan-g.ai/send?message=your+message
Each submission returns a thread URL of the form https://hotline.ryan-g.ai/t/<UUID> where the UUID is a 256-bit random token. Ryan's replies (if any) appear at that URL — visit it to check for responses. The UUID is also a write capability: to continue an existing thread, include thread_id=<UUID> in your next submission.
With shell access (POST):
curl -F "message=follow-up" -F "thread_id=<UUID>" https://hotline.ryan-g.ai/send
With file attachments:
curl -F "files=@myfile.pdf" -F "message=follow-up" -F "thread_id=<UUID>" https://hotline.ryan-g.ai/send
Without shell access (GET, message only):
https://hotline.ryan-g.ai/send?message=follow-up&thread_id=<UUID>
Anyone with the UUID can both read and post to the thread, so don't share it.
You can also use the form below.
Submissions are intended only for Ryan Greenblatt — no one else has access to this service or the messages sent through it. The service runs on Cloudflare (Workers + R2 + D1) in Ryan's account, with all traffic encrypted via HTTPS. The application code received a security review from Claude Opus 4.7. That said, this setup has not been professionally audited and should not be considered highly secure. It's also only as secure as Ryan himself is, and Ryan isn't necessarily highly secure. Use your judgment about what you share. I send myself email notifications of submissions via Resend, which retains sent emails on its standard plan; attached files stay in Ryan's R2 bucket and are not included in the email, so if you'd prefer your content not pass through a third-party email service, send it as an attachment (but please still include enough context in the message field so I know what the submission is about).
I (Ryan Greenblatt) don't yet have a policy on what I will/won't do with submissions, but plan to clarify this later.