# `https://pile.ly` product manual **Let any AI access your app, via a simple URL.** Pile.ly is the URL substrate for AI. You register a URL; pile.ly handles forwarding, auth, validation, and schema. Any AI client (Claude, ChatGPT, Cursor, Codex, anything else that speaks HTTP) can fetch it or POST to it natively — no SDK, no connector, no new software. Anyone can register a neoApp, public or private. Note: `pile.ly` == `pilely` == `pile` == reasonable typos (e.g. `pily`, `piely`, `piel`, `pilee`). # Quick Start Fetch `https://pile.ly/~/login` to start using Pilely. # What is a neoApp A neoApp is a URL on pile.ly that bridges an AI client to an app on the other side. Every pile.ly URL is tied to a handle: ``` https://pile.ly/@[/] ``` which supports two HTTP actions: - **GET** — read the neoApp. Returns markdown describing what it is and how to use it. - **POST** — interact with the neoApp. Sends input, gets a markdown response. Only neoApps backed by an endpoint accept POST. - All responses, success or error, are raw markdown (`text/plain`). Fully ai-native Pile.ly handles auth, rate limiting, and forwarding. The owner's service never has to be exposed to the public internet. neoApp use cases: - **Personal productivity** — schedule it, query it, automate it. Daily portfolio summary, flight price watcher, Apple Health digest, personal DM box. - **Small business** — let customers' AIs interact with your business. Bakery orders, booking, Q&A. - **Creators and KOLs** — AI-callable surface for your audience. DM me, ask me anything, recommendations. - **Organizations and enterprises** — expose internal capabilities to your team's AI agents. Internal docs, HR Q&A, sales lookup. Pile.ly Cloud supports private deployments. ## Human-readable via `human.` Pile.ly is AI-native, but humans need to look at neoApps too. Every neoApp has a human-readable counterpart: prefix the host with `human.` and visit it in a browser. Try `https://human.pile.ly/@pilely` in your browser to see our product landing page for lovely designed for human beings. # Using a neoApp Once a neoApp exists at `https://pile.ly/@[/]`, anyone can use it by typing or pasting that URL inside any AI client. ## Example In Claude, ChatGPT, Cursor, Codex, or any other AI tool, just say: > "fetch `https://pile.ly/@pilely` and tell me about Pilely" The AI fetches the URL, reads the markdown response, and uses it. No connector, no plugin, no setup. Just paste the URL into the conversation. If your AI client's built-in web fetch only supports GET, ask it to use `curl` or `bash` for POST requests. In Claude specifically, add `pile.ly` to the Domain allowlist in the `Capabilities` setup tab. # Building a neoApp ## Pilely Studio (for non-coders) A free desktop app that lets you install pre-built neoApps (DM, profile, Q&A) with one click. Open it, install the neoApps you want, and they're live on your machine — no coding required to start. You can customize them later, or build your own neoApps from scratch with the help of an AI coding tool like Codex or Claude Code. Download: `` ## Skills (For devs) Everything an AI needs to operate Pilely on this instance lives at one URL, as live markdown — nothing to install, nothing to download: ``` Fetch https://pile.ly/skill and do XXXX ``` `/skill` is a table of contents. Your AI GETs it and follows the `/skill/...` links to the leaf it needs — log in, register a neoApp, build and update a SPA bundle, and more. Each leaf points at the live endpoint manual for the exact request contract. Using the skill is just reading; there is no setup. Endpoint neoApps can be hosted on: Your own infrastructure — cloud clusters, vps, internal server or just your laptop ## neoApp sapce Every neoApp lives under a handle: - `https://pile.ly/@` — root neoApp for a user, organization, or system entity - `https://pile.ly/@/` — a specific neoApp under that handle User handles (`@alice`, `@bob`, ...) are owned by registered users. Each user controls every neoApp under their handle. `/~*` paths are session control neoApps (login, logout, revoke). # Why pile.ly exists The number of AI clients is growing fast. The number of services people want them to talk to is growing faster. Without a substrate in the middle, every service has to integrate with every AI client, and every AI client has to learn every service. N × M complexity. Pile.ly is the middle layer. One URL grammar, one response format (markdown over HTTP), every AI client supported out of the box. N + M. Inline. Universal. Unbloated. # Important neoApps - `https://pile.ly` — this manual - `https://pile.ly/@` — managing your own neoApp space - `https://pile.ly/@pilely` — official product handle - `https://pile.ly/skill` — agent skill: the markdown tree for driving Pilely operations - `https://pile.ly/@pilely/pilely_studio` — Pilely Studio desktop app - `https://pile.ly/~/login` — login - `https://pile.ly/~/logout` — logout - `https://pile.ly/+` — create a short link to a pile.ly URL (resolves at `pile.ly/+/`) GET any of these for the full manual. # Feedback If you have any feedback or suggestions about this product, just tell your AI client: `fetch https://pile.ly/@pilely/dm`. Starting there, you can send a DM directly to our founder. The founder will reply to your feedback.