Skip to content
HMU.API

A structured inbox for pitches, meetings, and press.

HMU API is a structured inbox. One URL replaces email, contact forms, and DMs. Senders pick a channel (/pitch, /meet, /ask, /hire, /press), fill required fields, and the message arrives pre-classified and AI-scored.

/pitch/meet/ask/intro/hire/collab/advise/press

Try it: submit, score, inbox

Watch the flow auto-play, or switch to Try it live to send a real /ask to the demo inbox.

POST /api/u/you/ask

Alex Chen
alex@startup.io

Your dashboard

/ask78

Alex Chen

What stack are you using for HIPAA-compliant AI triage?

/pitch92

Sarah Kim

Series A, healthcare AI, $8M round

/meet54

Marcus Webb

30-min intro, partnership discussion

Messages land pre-classified and scored.

Your API. Your inbox.
Your rules.

AI inbox tools classify messages after they arrive. HMU API structures them before they're sent. It is not university webmail, not H&M's catalog API, and not an AI image API. Agents, automations, and humans reach you through typed endpoints, on your terms.

Key takeaways

  • One public URL. Eight typed channels. One dashboard.
  • Structure happens at send time: required fields, not a free-text dump.
  • AI scores priority before you look. Verified senders skip the spam pile.
  • Humans get a form. Agents POST JSON. No API key for public endpoints.

Today

A partnership offer and a meeting request land in the same pile

With HMU API

Each message type has its own channel

Today

You juggle 4 email addresses across projects and roles

With HMU API

One link, many channels, one dashboard

Today

You read every message to decide what matters

With HMU API

AI scores priority before you see it

Today

Spam filters guess. Senders can be anyone.

With HMU API

Verified senders, required fields, no blanks

Today

Your CRM or bot can't email you like a person can

With HMU API

Apps, agents, and automations reach you natively

Today

New tool? New integration. New inbox to check.

With HMU API

One URL plugs into Zapier, Slack, CRM, whatever you already use

How structured messaging works

  1. 01

    Sign up and get your page

    Your own URL, like hmuapi.com/you

  2. 02

    Choose your channels

    Deals, meetings, questions, hiring, press: pick what you accept

  3. 03

    Replace your contact info

    Put the link on your site, LinkedIn, or business card: one link does it all

  4. 04

    AI handles the rest

    Messages arrive sorted, scored, and ready. You just decide.

Built for

AI-powered inbox features

Your page

A public profile with every way to reach you in one place

AI triage

Every message scored by importance: high priority floats to the top

Sender trust

Verified senders get through instantly. Spammers don't.

Pitch scoring

Senders see how strong their message is before they hit send

Your dashboard

Every channel lands in one inbox, AI-scored, labeled by intent, and sorted by priority. High-value /pitch messages surface above routine /ask traffic.

HMU APIdashboard preview

Inbox

All channelsUnread

Unread

2

Today

4

Avg response

2d

P
Sarah KimNexHealth AIdeal2m ago

Series A, healthcare triage SaaS, $8M round, deck attached

92
?
Alex Chenquestion14m ago

What stack are you using for HIPAA-compliant AI triage?

78
M
Marcus WebbAtlas Venturesmeeting1h ago

30-min intro, partnership on distribution

54
R
Nina PatelHealthTech Weeklymedia3h ago

Podcast interview, AI in clinical workflows

61

API channels

POST

Example endpoints: see docs for API details

GET /status GET /endpoints GET /profile

Quick start: integrate in minutes

~/terminal
# Ask a question
curl -X POST https://hmuapi.com/api/u/jamestannahill/ask \
_

FAQ: why an API inbox?

What's an API?

An API (Application Programming Interface) is a structured way for software to talk to other software. Instead of writing a free-form email, you send a JSON message to a specific URL with labeled fields. Think of it like a perfectly organized form, except it's also machine-readable and automatable.

I already have multiple email addresses, why do I need this?

That's exactly the problem. People create separate emails for each project, company, or role, then juggle logins, filters, and forwards to keep it all straight. HMU API replaces that with one URL and multiple endpoints. A /pitch for your fund, a /hire for your startup, a /collab for your side project, all routed, prioritized, and triaged in one dashboard. One identity, many channels, zero inbox switching.

Why not just use email?

Email dumps everything into one inbox, a $10M deal, a podcast invite, and a cold pitch all land in the same place with the same priority. You sort it manually. With HMU API, each message type has its own endpoint with required fields, so nothing important gets buried. Messages are scored and prioritized before you ever see them. And unlike email, bots and automations can integrate natively, no scraping, no parsing, no guessing.

How is this different from AI inbox tools?

Tools like Gmail AI, Superhuman, SaneBox, and smart routing platforms all do the same thing, they take unstructured messages and try to guess what matters after the fact. Summarize, label, snooze, prioritize. But they're still retrofitting intelligence onto a system that was never designed for it. HMU API flips the model: structure happens at the point of submission, not after. Senders choose an endpoint, fill required fields, and the message arrives pre-classified, pre-scored, and machine-readable. No AI has to parse a wall of text to figure out if it's a pitch or a meeting request. And unlike any email tool, HMU API is natively accessible to bots, agents, webhooks, and automations, not just humans with inboxes.

Isn't this just another layer on top of my existing communications?

It's a replacement, not an addition. Put your HMU API link where your email used to be, your website, your LinkedIn, your business card. Inbound messages stop scattering across Gmail, DMs, and contact forms, and start arriving in one structured dashboard. You don't check more places. You check one. The difference is that what arrives is already sorted: a /pitch has deal size and a deck link, a /meet has a purpose and preferred time, a /hire has a role and comp range. You stop being the router and start being the decision-maker.

What happens when I submit?

Your message is validated, scored for priority, and stored. The inbox owner is notified instantly. You get an auto-reply confirming receipt. High-priority messages get flagged.

Do I need to know how to code?

No. Click any endpoint and you'll get a form. The API and curl examples are there for developers who prefer to integrate programmatically.

How do I get a faster response?

Be specific. Use the right endpoint. Include numbers and context. Each inbox owner configures their own priority sectors, check their profile for details.

How do I use this from the terminal?
Open your terminal and send a JSON request with curl:
curl -X POST https://hmuapi.com/api/u/jamestannahill/ask \
  -H "Content-Type: application/json" \
  -d '{"name":"Your Name","email":"you@example.com","question":"What are you working on?"}'
Replace jamestannahill with any username. Swap /ask for any endpoint, /pitch /meet /intro /hire /collab /advise /press, and include the required fields.
Is there a rate limit?

10 per sender per endpoint per 30 days. One well-crafted message beats ten lazy ones.

Can this integrate with my existing stack?

Yes, and you don't need to rip anything out. Replace a mailto link or contact form with your HMU API URL and inbound messages arrive pre-sorted. Connect it to Zapier, Make, or n8n to push messages into your CRM, Slack, or project tracker. Developers can POST JSON from any language, Python, JavaScript, cURL, whatever you already use. No API key, no SDK, no OAuth. If your tool can make an HTTP request, it works.

What's the tech stack?

Cloudflare Workers, D1, KV, Resend, Astro. Runs at the edge, sub-50ms response times globally. Zero servers.

Can AI agents use this?

Yes. Every HMU API profile is a set of structured REST endpoints. Any LLM or agent framework that makes HTTP requests can discover your endpoints via GET /api/u/you/endpoints, read the schema, and submit messages. No API key needed. The llms.txt file makes your inbox discoverable by AI crawlers automatically.

Is this HMU university email or webmail?

No. HMU API is a structured inbox product at hmuapi.com. It is not Hellenic Mediterranean University webmail (hmu.gr), not Hong Kong Metropolitan University email, and not a login page for any campus mail system. If you are looking for university webmail, use your school's official mail URL.

Is this related to H&M, MuAPI, or hmu.ai?

No. HMU here means Hit Me Up: a typed way to reach a person. It is not the H&M retail catalog API, not MuAPI (muapi.ai) image generation, and not hmu.ai or hmu.co. If you want a programmable inbox with /pitch, /meet, and /press channels, you are in the right place.

Built by

James Tannahill , founder

Investor who codes. Runs Plocamium Holdings, builds healthcare AI tools, and replaced his own email with these endpoints. Cornell MBA. Updated .