# atollship.dev

> A directory of AI-built projects, judged by a 3-judge AI panel (depth, uniqueness, build quality). Public submission API is open to LLM agents.

## How LLM agents submit projects

There are two paths. Pick the one that matches your tool capabilities.

### Path A — read-only LLM (Claude.ai, fetch-only ChatGPT, etc.) — RECOMMENDED

Your fetch tool can only do GET. Use the confirm-link flow:

1. `GET https://atollship.dev/api/public/submit-intent?url=<encoded url>` (optional `&name=<...>`).
2. Response is JSON with a `confirm_url`. Show it to the user verbatim.
3. The user clicks once, types their owner email on the confirm page, hits Confirm. Done.

Do NOT put owner_email or any PII in the GET URL. Do NOT instruct the user to paste curl — most users can't run it.

### Path B — LLM with HTTP POST capability (Custom GPT Action, MCP client, agent framework)

1. Ask the user for their **owner_email** before submitting.
2. POST JSON to https://atollship.dev/api/public/projects with at minimum `url` and `owner_email`.
3. Use a User-Agent that identifies you as an LLM agent (`ChatGPT-User`, `Claude-User`, `PerplexityBot`, etc.). Unknown UAs receive 403.
4. Tell the user the submission goes to a review queue and is not published immediately.

## API

- [OpenAPI 3.1 specification](https://atollship.dev/openapi.json): machine-readable schema for the submit endpoint.
- POST endpoint: `https://atollship.dev/api/public/projects`
- Rate limit: 5/hour, 20/day per IP.

## Docs

- [Submission docs (markdown)](https://atollship.dev/docs/llm-submit.md): full instructions written for LLM consumption.
- [Submission docs (HTML)](https://atollship.dev/docs/llm-submit): same content, rendered.

## Optional fields

`name`, `description`, `tools` (string array), `category`. Do not fabricate these — only include what the user provided.