# Fly in Public for developers

Fly in Public can be driven from the app, Telegram, scripts, or AI assistants. The docs are split into human-readable pages and Markdown endpoints that AI clients can read directly.

## Start here

1. Create your flight from the app.
2. Add proofs from the web app, Telegram, the REST API, or an MCP-compatible assistant.
3. Use API tokens when a trusted tool needs to check your flight or add proofs without opening the app.

## Choose your path

| Need | Use | Link |
| --- | --- | --- |
| Connect an AI assistant without managing API keys | Fly in Public skill | https://flyinpublic.com/docs/skills |
| Query flight status, proofs, leaderboard, or post proofs from a script | REST API | https://flyinpublic.com/docs/api |
| Connect Claude, Cursor, OpenClaw, or another MCP client | MCP server | https://flyinpublic.com/docs/mcp |
| Give an AI assistant the full docs context | LLM docs | https://flyinpublic.com/llms.txt |
| Read everything as one text bundle | Full context | https://flyinpublic.com/llms-full.txt |

## What you can automate

- Check whether your current flight is safe, chilling, flying, or crashed.
- Post proofs from a CLI, cron job, Telegram workflow, or assistant.
- Pull recent proofs and leaderboard position into another workspace.
- Let an AI assistant inspect proof activity and help you decide what to share next.

## Agent-friendly docs

Every docs page has a Markdown version, plus actions to copy the page or open it in ChatGPT or Claude. Prefer Markdown endpoints for AI clients because they avoid navigation, styling, and hidden UI noise.

## Access tokens

Create API tokens from https://flyinpublic.com/settings/profile. Tokens are shown once, start with `fip_`, and can be revoked any time. Treat them like passwords.

## Read next

- REST API reference: https://flyinpublic.com/docs/api
- Skill setup: https://flyinpublic.com/docs/skills
- MCP setup: https://flyinpublic.com/docs/mcp
- LLM index: https://flyinpublic.com/llms.txt