# DropRegion > One-step publishing for anything AI makes. Paste or POST HTML, get a live, > memorable link at dropregion.com/@handle/. Publishing and browsing > are free (20 drops a month on the free plan). A human signs up once (password, magic link, or Google) > and generates an API key — every publish after that, including every > agent-driven one, is a single unattended request with no human in the loop. ## Quickstart (for agents) **One-time human setup**: sign up at dropregion.com/signup, then generate an API key at dropregion.com/settings/keys. Give that key to your agent/tool. To publish a page, send one HTTP request with the key: ``` POST https://dropregion.com/api/publish Content-Type: application/json x-api-key: drk_live_... { "html": "...", "title": "Optional title", "category": "Optional category", "visibility": "public" } ``` Response (201 on success, 401 if the key is missing/invalid/revoked, 422 if the safety scan rejected it): ``` { "id": "the site's internal id — needed to re-drop it later", "url": "https://dropregion.com/@yourhandle/my-slug", "slug": "my-slug", "channel_url": "https://dropregion.com/@yourhandle", "status": "live" } ``` - `visibility` is `"public"` (default), `"unlisted"` (works at its own URL, never listed or searched), or `"private"` (only the owner and specific people invited by email, via the Drop page's Sharing panel, can view it). - `url` is live immediately if `status` is `"live"`. If `status` is `"rejected"`, the page failed the pre-publish safety scan and was not made public — see the `reasons` array in the response. - Every site has a hard size cap and a monthly bandwidth cap (see `/quickstart.md` for current limits) and the whole service has a monthly spend ceiling that throttles new publishes with a 429 if reached — treat a 429 as "try again later," not an error to retry immediately. ## Replace the page, keep the link Update an already-published page without losing its URL, opens, likes, or comments — the headline reason to publish here instead of a static host: ``` PUT https://dropregion.com/api/sites/{id} Content-Type: application/json x-api-key: drk_live_... { "html": "...(updated)..." } ``` Same response shape as publish, plus `"version"` (an incrementing counter). Only the site's own creator's API key can re-drop it — anyone else's key (or none) gets a 401/403. - Full walkthrough with copy-pasteable examples: /quickstart.md ## Connect over MCP If you are an MCP client (Cursor, Claude, Grok and others), connect to the remote server at https://dropregion.com/mcp (Streamable HTTP, no session needed). Every request needs a credential; without one the answer is HTTP 401 with a `WWW-Authenticate` header pointing at /.well-known/oauth-protected-resource/mcp. Two ways to sign in: - OAuth (Claude, ChatGPT, Grok and other connector UIs): add the URL as a remote MCP server and the client opens a DropRegion sign-in where the creator approves it. - An API key, for Cursor, scripts and CLIs: send it as the `x-api-key` header or as `Authorization: Bearer drk_live_...`. A person creates the key at /settings/keys. An app approved through OAuth acts as that creator with every scope. Setup steps for people: /docs/agents A skill that says how to publish and update well (Markdown): /skills/publish Tools: `publish_drop`, `preview_drop` (check a page, nothing stored or counted), `update_drop`, `unpublish_drop`, `get_drop`, `list_drops`, `get_drop_analytics`. They call the same routes as the REST API above, so the limits, the safety scan and the key scopes (publish, read, manage) are identical. ## Documents (humans only) The API publishes HTML only. Word (.docx), PDF, Markdown and text files are converted into a web page by a signed-in person at dropregion.com (the New Drop button, then "Convert a file or link"); there is no API for converting documents. A conversion counts toward the same 20 free drops a month once it is published. ## Other paths - Gallery of published tools, ranked by engagement: /gallery - A creator's channel and published tools: /@ - A specific published page: /@/ - Generate/revoke API keys (human, in a browser): /settings/keys