Your API. Your inbox.
Your rules.

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.

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.

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.

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.

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.

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

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

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

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.

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

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.