tinylaunch.com valid

TinyLaunch — Agent Guide

You are launching a startup on TinyLaunch on behalf of a user, end-to-end, without a browser. Read this guide once, then execute. Don't probe other endpoints or guess values — everything you need is below.

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-21T03:50:26.771Z. Cached copy · Source on tinylaunch.com

# TinyLaunch — Agent Guide

You are launching a startup on TinyLaunch on behalf of a user, end-to-end,
without a browser. Read this guide once, then execute. Don't probe other
endpoints or guess values — everything you need is below.

**Before anything else:** find your host's structured-question tool
(Claude Code: `AskUserQuestion` — you have it; Codex CLI:
`ask_user_question`; Cursor: `AskQuestion`; others under similar
names — see §"Asking the user"). You must **invoke that tool** for
every `[choose]` step below. Writing options as a bulleted list in
your text response, or asking the question as a free-text sentence, is
the single most common way agents break this flow. Don't do it.

API base: `https://www.tinylaunch.com/api/v1` (use this exact host — calling a different
subdomain or the apex can trigger a 307 redirect that costs a round-trip).
Content-Type: `application/json` on every POST/PATCH.
Token handling: if your runtime gives you fresh shells per command,
`export TL_TOKEN=…` won't persist — pass the token literal in the same
command, or pipe it via stdin. Don't rely on environment variables
surviving between calls.
Errors share `{ "error": "<machine_code>", "detail"?: "<human msg>", ... }`.
Branch on the `error` code — the codes are stable, the wording isn't.

### Endpoint cheat sheet — when, what, and what auth

The full flow only needs these eight endpoints. Don't probe anything
else, don't fetch arbitrary site URLs, don't curl /api roots.

| Phase | Step | Endpoint | Auth | Purpose |
| ----- | ---- | -------- | ---- | ------- |
| 1 | 6 (optional) | `GET /api/v1/categories` | **none** | Fresh category list; already embedded in §Categories — only call if you want JSON. |
| 1 | 9 | `GET /api/v1/launch-dates` | **none** | Available launch windows. |
| 2 | 9 | `POST /api/v1/auth/request-code` | **none** | Send 6-digit OTP to user's email. |
| 2 | 10 | `POST /api/v1/auth/verify` | **none** | Exchange code for `access_token`. |
| 2 | 11 | `GET /api/v1/maker` | Bearer | Check for existing maker profile. |
| 2 | 11 | `POST /api/v1/maker` | Bearer | Create maker (only if GET returned 404). |
| 2 | 12 | `POST /api/v1/startups` | Bearer | Create the startup. |
| 2 | 13 | `POST /api/v1/launches` | Bearer | Schedule the launch (free, or premium with `payment_url` returned). |

Bearer header format: `Authorization: Bearer <access_token>`. Tokens
last ~1 hour; on `401 invalid_token` redo steps 9-10.

**Auth is binary per endpoint.** If the cheat sheet says "none," don't
send a Bearer; if it says "Bearer," don't omit it. The two public reads
above are safe to call before the user has even given you their email.

---

## Asking the user — the single most important rule

**Two laws. Apply both, always:**

### Law 1: Invoke your host's structured-question tool. Don't print options as text.

Before you ask the first Phase 1 question, **look at your available
tools** and find the one for asking the user a structured question.
Common names across hosts:
…

Machine-readable: GET /v1/resolve?q=tinylaunch.com · GET /v1/domain/tinylaunch.com · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for tinylaunch.com:
1. POST https://agentwebmap.com/v1/sites/tinylaunch.com/claims and keep claim_id and claim_secret private.
2. Publish the proof: add the line "AgentWebMap ownership: <token>" (token from step 1) to https://tinylaunch.com/llms.txt, or use the DNS, meta-tag or well-known method the response describes.
3. POST https://agentwebmap.com/v1/sites/tinylaunch.com/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/tinylaunch.com).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.