For LLMs & agents

Hep.gg publishes plain-text, machine-readable API references at /llms.txt and /llms/<app>.txt, built for LLMs, coding agents, and RAG indexers.

For LLMs & agents

Alongside these human docs, Hep.gg publishes a set of plain-text, machine-readable API references built for large language models, coding agents, and retrieval pipelines. They cover the same APIs documented here, but dense and stripped of styling: short prose, tight endpoint listings, example payloads, and error codes. Point a model or an agent at them and it can integrate a Hep.gg app without scraping the rendered site.

Start here

https://hep.gg/llms.txt is the index: it lists every per-app file and the conventions shared across them. Fetch it first, then pull whichever app file you need.

curl
# The index of every machine-readable doc
curl https://hep.gg/llms.txt
 
# A single app reference
curl https://hep.gg/llms/database.txt

The directory

Every app reference is one text/plain file at https://hep.gg/llms/<app>.txt.

AppReferenceWhat it covers
Uploaderuploader.txtShareX-style file uploads and the /:id file serve.
URL Shortenershorten.txtCreating shortlinks.
SMSsms.txtSending outbound SMS at sms.hep.gg.
Emailemail.txtThe transactional email send API.
Musicmusic.txtDownload, search, and stream tracks.
ID Generatoridgen.txtGenerating UUIDs, nanoids, snowflakes, and more.
AI Gatewayai.txtThe Anthropic-compatible AI proxy.
Cloud Storagestorage.txtS3-compatible object storage.
Databasedatabase.txtProvisioning and managing databases with a bearer key.
Formsforms.txtThe public form-fetch and submission API.
Snippetssnippets.txtCreating pastes (CLI / ShareX) and reading them raw.
Profilesprofiles.txtThe public profile, presence, and contact endpoints.
Login (OIDC)login.txtSign in with Hep.gg: the full OAuth2 / OIDC flow.

Conventions

Every reference follows the same rules, so a model only has to learn them once:

  • Base URL is https://hep.gg unless the file names a per-app host (for example sms.hep.gg, music.jakeypri.me, paste.hep.gg).
  • Auth is per-app and stated at the top of each file: a bearer key, an API key, or OAuth tokens. Cookie-authenticated endpoints exist for the dashboard and are listed only for completeness, marked as not for programmatic use.
  • Responses are JSON envelopes: { "ok": true, "data": ... } on success and { "ok": false, "error": "<message>", "code"?: "<token>" } on failure. A few legacy endpoints predate the envelope and say so.
  • Timestamps are ISO 8601 UTC.
  • Rate limits, where present, are documented per endpoint and return HTTP 429 with Retry-After.

The files are cached for a few minutes and are safe for crawlers and RAG indexers to fetch on a schedule.