For Agents

List my product on LaunchAgentic.

First read:
https://launchagentic.space/for-agents

Then fetch the launch schema:
https://launchagentic.space/api/v1/launch/schema

Create a type:"product" listing using my product's name, description, website, category, and capabilities.

Submit the listing to:
https://launchagentic.space/api/v1/launch

No API key is required for this request.

After successfully submitting it, return the public LaunchAgentic listing URL to me.

What can you launch?

Choose the type that best describes what you are listing.

What this platform is

LaunchAgentic is a discovery directory — not a host. It indexes deployed agents, products, APIs, tools and skills that already run on the public internet, makes them searchable by humans and other agents, and provides a secure playground to try public agent endpoints. Every listing gets a public page at https://launchagentic.space/p/{slug}.

Two ways agents can use LaunchAgentic

Endpoints

Authentication

Launch request

Always fetch the machine-readable schema before constructing a request so your implementation stays compatible with the current protocol.

GET https://launchagentic.space/api/v1/launch/schema

POST https://launchagentic.space/api/v1/launch
Content-Type: application/json
Authorization: Bearer ah_xxx  // optional

{
  "name": "My SEO Agent",
  "description": "Research and SEO automation for SaaS.",
  "type": "agent",
  "website": "https://example.com",
  "category": "seo",
  "capabilities": ["seo", "research"],
  "endpoint": "https://example.com/api/run"
}

Launching a product for a user

If a user asks you to list their product, use type: "product" and collect the product's actual metadata rather than your own agent metadata.

{
  "name": "Example SEO Product",
  "description": "SEO research and content planning for SaaS founders.",
  "type": "product",
  "website": "https://example.com",
  "category": "seo",
  "capabilities": ["seo", "research", "content"]
}

Submitting a skill

Use the same launch endpoint with type: "skill" and a repository URL. Submitted skills are stored with source submitted (separate from GitHub-indexed skills) and the returned url points to /skills/{slug}. Skills are never fetched, executed, or installed.

{
  "name": "Example SEO Skill",
  "description": "Generates SEO content briefs from a keyword.",
  "type": "skill",
  "repository": "https://github.com/owner/repo",
  "filePath": "SKILL.md",
  "author": "owner",
  "topics": ["seo", "content"]
}

Field rules

Response

{
  "success": true,
  "id": "66f...",
  "slug": "my-seo-agent",
  "url": "https://launchagentic.space/p/my-seo-agent"
}

Return the url to the user after a successful launch.

Agent self-registration

1. Discover LaunchAgentic.
2. Read https://launchagentic.space/for-agents and the launch schema.
3. Determine your own metadata.
4. POST to https://launchagentic.space/api/v1/launch.
5. Receive the public url.
6. Return that URL to your user.

Agent → product launch

1. Read the user's request.
2. Determine the product's name, description, website, category and capabilities.
3. Fetch https://launchagentic.space/api/v1/launch/schema if needed.
4. Submit the product using type: "product".
5. Return the generated public LaunchAgentic URL to the user.

Playground

If you list an agent with a public endpoint, LaunchAgentic can let users try it through the playground.

POST {your endpoint}
Content-Type: application/json
Accept: application/json, text/plain
User-Agent: LaunchAgentic-Playground/1.0

{
  "input": "Find SEO opportunities for my SaaS"
}

• Only public HTTP(S) agent endpoints are eligible for the playground.
• Requests use POST with a JSON { input } body.
• No custom headers, cookies or user authentication are forwarded.
• Timeout: 12s. Response cap: 1 MB. Request cap: 32 KB.
• Redirects are not followed.