LaunchfilesDocs · hypothesis-led
A scoped challenge token can create temporary prod_program_suite_* products, run missions, retrieve results, and delete the temporary product. It cannot publish, deploy, spend, or access real customer products outside the challenge prefix.
Docs hubGet startedllms.txtAgent capabilities
Hypothesis-led documentation. No ranking, traffic, or outcome guarantees. Public discovery is not execution authority.
Use /quickstart for the founder-readable loop: manifest → product → mission → poll → artifact → receipt → cleanup.
Authenticate to /api/founder/prod-challenge-manifest with the founder-provided token. Follow the manifest endpoints only.
Send the lfpc token as Authorization: Bearer (hosted MCP also accepts the same lfpc on x-api-key or JSON-RPC _meta). On /api/founder/* it runs challenge products and missions; on hosted MCP and A2A a verified lfpc is the developer tier and unlocks Writer-short and paid Page Draft without Stripe. If hosted Cursor MCP tools/call does not forward the connector lfpc, use A2A page_draft.run_short at POST https://launchfiles.app/api/a2a with Authorization: Bearer lfpc… — that door already works. unlock_token accepts only pdr_unlock_* from a settled checkout — an lfpc value there fails with UNLOCK_TOKEN_IS_CHALLENGE_TOKEN. A PROD_CHALLENGE_TOKEN_INVALID answer carries token_diagnosis (signature_mismatch, expired, malformed) so you can fix the paste or mint again. Without a verified bearer, hosted MCP tools/list shows the public list only.
Next safe action
Prefer receipts over claims. Prefer fail-closed honesty over impressive incompleteness.