Documentation

Getting started

Base URL

Also accessible via https://hitmyapi.com

Multi-tenant URL structure

Every user on HMU API gets their own namespaced routes under /api/u/<username>.

Identity endpoints

Public profile data is available without authentication.

{
  "username": "janedoe",
  "name": "Jane Doe",
  "bio": "Founder & investor",
  "endpoints": ["pitch", "ask", "meet"],
  "status": "open"
}

Counter-API — pitch scoring

The scoring endpoint evaluates a message payload in real time and returns a numeric score with structured feedback. No submission is created — this is a dry-run evaluation only.

{
  "score": 82,
  "label": "Strong",
  "dimensions": {
    "clarity": 90,
    "relevance": 75,
    "urgency": 80
  },
  "feedback": "Strong one-liner. Add deal size to improve relevance."
}

{
  "message_id": "uuid-here",
  "status": "delivered",
  "read": false,
  "submitted_at": "2026-03-12T10:00:00Z"
}

Auth model

Legacy aliases

The original short-form routes still work and are permanently routed to jamestannahill. Existing integrations do not need to update.

Quick start

curl -X POST https://hmuapi.com/api/u/jamestannahill/ask \
  -H "Content-Type: application/json" \
  -d '{"name":"Jane","email":"jane@example.com","question":"What are you building?"}'

const res = await fetch("https://hmuapi.com/api/u/jamestannahill/ask", {
  method: "POST",
  headers: { "Content-Type": "application/json" },
  body: JSON.stringify({
    name: "Jane",
    email: "jane@example.com",
    question: "What are you building?"
  })
});

const data = await res.json();

import requests

res = requests.post("https://hmuapi.com/api/u/jamestannahill/ask", json={
    "name": "Jane",
    "email": "jane@example.com",
    "question": "What are you building?"
})

print(res.json())

Response format

{
  "success": true,
  "message_id": "uuid-here",
  "auto_response": "Thanks for reaching out..."
}

Endpoints

All POST endpoints require Content-Type: application/json. Rate limit: 10 per sender per endpoint per 30 days.

GET endpoints (per user)

Error codes

Agent discovery flow

Any LLM, agent framework, or automation that makes HTTP requests can integrate. No API key, OAuth, or SDK needed.

1. 1
   GET /api/u/:username

   Discover who this person is, what they care about

2. 2
   GET /api/u/:username/endpoints

   Read available endpoints, schemas, required fields

3. 3
   POST /api/u/:username/:endpoint

   Submit a structured message with the right fields

4. 4
   GET /api/status/:token

   Track if the message was received, viewed, or replied to

Email is human-to-human. HMU API is anything-to-human.

Integration ideas

Webhooks

Get notified in real time when messages arrive. Webhooks fire on message.created events and can be filtered by endpoint.

{
  "url": "https://hooks.slack.com/services/...",
  "format": "slack",
  "events": ["message.created"],
  "endpoint_filter": "pitch"
}

const crypto = require("crypto");
const expected = crypto
  .createHmac("sha256", WEBHOOK_SECRET)
  .update(rawBody)
  .digest("hex");

if (expected !== req.headers["x-hmu-signature"])
  return res.status(401).send("Invalid");

Dashboard API

Authenticated endpoints for managing your inbox. Requires Authorization: Bearer <token> or an active session cookie.

Auto-replies

Every endpoint sends an automatic confirmation email to the sender. Customize per endpoint in Settings.

Email digest

Get a summary of new messages delivered to your email on a schedule. Configure in Settings.

Includes: message table sorted by priority, stats summary (total/unread/replied), and a link to your dashboard.

Machine-readable docs