BrewPage
BrewPage is a free, no-registration instant hosting service for HTML pages, Markdown documents, AI-agent artifacts, files, and multi-file static sites. It also offers a namespaced key-value store and a JSON document store. The REST API returns short, shareable HTTPS links (https://brewpage.app/{ns}/{id}) and an owner token used to update or delete content in place. BrewPage is designed to be AI-agent friendly: it provides an MCP server (brewpage-mcp), a Claude Code skill (brewdoc:publish), and a llms.txt manifest, and it requires a self-identifying User-Agent header on every request.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles BrewPage the way a machine reads it — 68 machine-readable artifacts across 13 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — BrewPage scores 57.2/100 (developing), with a separate agent-readiness read of 48/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile BrewPage
Each block below is one kind of artifact we hold for BrewPage. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 13
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
BrewPage Files API
File hosting up to 5 MB per file, 1000 files per namespace
BrewPage Gallery API
Browse public content from the 'public' namespace without password protection
BrewPage HTML API
HTML page hosting with markdown support
BrewPage JSON API
JSON document store with up to 10,000 docs per collection
BrewPage KV API
Key-Value store with up to 1000 keys per namespace
BrewPage Namespace API
Fresh, collision-free namespace suggestions
BrewPage Owner Check API
Lightweight owner-token probe; never increments views or returns content
BrewPage preview API
OpenGraph metadata for social bots
BrewPage Reports API
Abuse reports for hosted content
BrewPage SEO API
Search engine optimization endpoints
BrewPage Short Links API
Short URL resolver for sharing
BrewPage Sites API
Multi-file HTML site hosting via ZIP or folder upload
BrewPage Stats API
Platform-wide usage statistics
Scroll within the panel for all 13 ·
Open Collections 1
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
BrewPage API
OPEN COLLECTIONPricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Rate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Brewpage Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Brewpage Finops
FINOPSFeatures 17
The notable capabilities this provider advertises, captured as structured features so they can be searched and compared instead of read one landing page at a time.
Notable capabilities this provider offers.
Instant HTML Hosting
POST raw HTML or a JSON body to /api/html and receive a 10-char short URL at /{ns}/{id} with no signup.
Markdown Rendering
Pass `format=markdown` to publish Markdown that BrewPage renders to styled HTML at view time.
Multi-File Site Hosting
Upload a ZIP archive or files+paths multipart to /api/sites; entry point auto-detected (index.html preferred); 20 MB / 100 files / 5 MB each.
File Hosting
Upload binary or text files via /api/files (5 MB max). Images, PDFs, video, and audio display inline; ?dl=1 forces download.
Key-Value Store
1000-key namespaced KV stores via /api/kv with per-key PUT/GET/DELETE and per-store enumeration.
JSON Document Store
10,000-document collections via /api/json with PUT-in-place semantics on stable short URLs.
Update In Place
PUT to /api/html, /api/json, and /api/kv replaces content while keeping the short URL — agents can iterate without breaking shared links.
Owner Token Grouping
Save the `ownerToken` returned at creation and reuse it via `X-Owner-Token` to group resources under one owner and scope list endpoints.
Password Protection
Set `X-Password` (min 4 chars) at creation to require the same header (or `?p=...`) for reads; passworded items are excluded from the gallery and sitemap.
Public Gallery
GET /api/gallery surfaces content posted to the default `public` namespace without a password — searchable, social-bot friendly, OG-image generated.
OpenGraph Preview Images
Per-content 1200×630 PNG at /preview/{ns}/{id}.png plus an /preview-html stub for social media unfurlers.
Short Link Resolver
GET /{ns}/{id} returns the hosted content; GET /{ns}/{id}/{sub} resolves sub-paths inside multi-file sites.
Idempotent Owner Re-POST
A byte-identical POST /api/html to `public/` within 24h returns the existing id (X-Existing-Resource header set) so retries do not duplicate gallery entries.
Abuse Reports
POST /api/reports lets readers report inappropriate or harmful content for moderation.
Random Namespace Suggestion
GET /api/namespace/random returns a fresh, collision-free kebab-case namespace suggestion.
Platform Stats
GET /api/stats exposes platform-wide usage statistics; GET /api/sitemap.xml exposes a dynamic sitemap of public content.
AI-Agent Friendly
llms.txt and llms-full.txt manifests, an MCP server, a Claude Code skill, and required identifying User-Agent headers make BrewPage first-class for autonomous agents.
Scroll within the panel for all 17 ·
Semantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Brewpage Context
JSON-LDSpectral Rules 2
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
BrewPage API Rules
SPECTRALBrewPage API Rules
SPECTRALJSON Schema 5
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
BrewPage File
JSON SCHEMABrewPage HTML Page
JSON SCHEMABrewPage JSON Document
JSON SCHEMABrewPage KV Store
JSON SCHEMABrewPage Multi-File Site
JSON SCHEMAJSON Structure 2
JSON Structure captures the data shapes in a form built for tooling — a complement to JSON Schema that keeps the model machine-legible.
JSON Structure definitions describing this provider's data shapes.
Brewpage Html Page Structure
JSON STRUCTUREBrewpage Kv Store Structure
JSON STRUCTUREExamples 5
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
Brewpage Create Html Example
EXAMPLEBrewpage Upload File Example
EXAMPLEBrewpage Upload Site Example
EXAMPLEBrewpage Upsert Kv Example
EXAMPLESecurity Posture 1
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Use Cases 7
What developers actually build with this provider — captured so the catalogue answers 'what is this for', not just 'what does this expose'.
What developers build with this provider.
Share AI-Agent Output
Drop a Markdown report, generated HTML page, or JSON artifact and share a short URL with a teammate or end user.
Iterate On A Stable Link
Use PUT to refine content at the same short URL across multiple agent iterations without breaking previously shared links.
Stand Up A One-Off Microsite
Upload a ZIP of a static site (docs, demo, status page) and get a 30-day-max hosted URL with relative links between files.
Ephemeral File Drop
Send a PDF, image, or archive (≤5 MB) to a recipient who shouldn't need to sign up — URL expires automatically.
Scratch KV Storage For Agents
Use /api/kv as a free, server-side scratchpad for feature flags, session state, or memoized tool outputs (≤1000 keys per store).
Public Knowledge Drop
Post to the default `public` namespace and let the gallery + sitemap + OG image expose your content to search engines and social.
Password-Gated Share
Apply X-Password to a hosted page or file for lightweight access control without user accounts.
Scroll within the panel for all 7 ·
Integrations 6
Pre-built integrations with other platforms tell you where this provider already fits in a stack.
Pre-built integrations with other platforms and tools.
Model Context Protocol (MCP)
Official MCP server `brewpage-mcp` exposes BrewPage to any LLM/agent (Claude, Codex, Gemini, Cursor) via the Model Context Protocol.
Claude Code
Claude Code skill `brewdoc:publish` lets users publish from inside Claude Code via a slash command (claude-brewcode marketplace).
IndexNow
BrewPage submits public content to IndexNow for search engine discovery; PUT-based republish is recommended to preserve quota.
OpenGraph / Social Bots
Every short URL exposes `/preview/{ns}/{id}.png` (1200×630) and a `/preview-html/{ns}/{id}` OG stub for link unfurling.
Prism.js
Client-side syntax highlighting for known code/data file previews (JSON, XML, SVG, HTML, CSS, JS, TS, YAML, TOML, Markdown).
llms.txt
BrewPage publishes a /llms.txt and /llms-full.txt manifest for LLM-friendly discovery of the API surface.
Solutions 4
Packaged solutions the provider offers on top of the raw API surface.
Packaged solutions this provider offers.
Hosted Web Page
Free HTML/Markdown publishing with short URL, OG images, and password gating.
Hosted Files And Sites
5 MB files and 20 MB multi-file sites with TTL up to 30 days.
Agent State And Documents
KV stores (1000 keys) and JSON collections (10,000 docs) for stateful agent workflows.
AI-Agent Integration
MCP server, Claude Code skill, llms.txt manifests, and identifying User-Agent contract.
Resources
Every other property we hold for BrewPage — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 3
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 3
Pagination, idempotency, versioning, errors, and events
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Operate 1
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
← All providers · Data indexed from github.com/api-evangelist/brewpage · machine-readable index on apis.io