Jentic OSThe workplace. An in-house AI platform for every employeeJentic OneSafe access. Agents reach your systems without holding keysJentic AIRThe foundation. Gets your existing platforms ready for AI
Pricing

GET STARTED

API DirectoryBrowse 10,000+ APIs ready for AI agent integrationDocumentationGuides and API reference

TOOLS

API ScoringCheck your AI readiness using our scorecardArazzo UIVisualize Arazzo workflows as interactive documentationArazzo EditorBuild and edit multi-step API workflows visually

COMMUNITY

GitHubOpen source projects and examplesOpen StandardsBuilt on open specs. Never locked in.
All ResourcesEverything in one placeBlogLatest articles and insightsTech Talk NewsletterAPIs, AI agents, architecture and strategyWebinarsLive sessions and on-demand recordingsReports & WhitepapersOriginal research on enterprise AI
About UsOur mission and teamCareersJoin our teamContactGet in touch
Try it now
Jentic OSJentic OneJentic AIR
Pricing
API DirectoryDocumentationAPI ScoringArazzo UIArazzo EditorGitHubOpen Standards
All ResourcesBlogTech Talk NewsletterWebinarsReports & Whitepapers
About UsCareersContact
Try it now
JenticJentic
Products
  • Jentic OS
  • Jentic One
  • Jentic AIR
For Developers
  • API Directory
  • Documentation
  • GitHub
Company
  • About Jentic
  • Careers
  • Contact Us
  • Trust Centre
ISO/IEC 27001:2022 certification badge issued by Prescient SecurityISO/IEC 27001:2022 certification badge issued by Prescient Security

Information Security Management System

Certified to ISO/IEC 27001:2022 by Prescient Security

AICPA SOC for Service Organizations logoAICPA SOC for Service Organizations logo

SOC 2® Type 1 report

Audited by Prescient Assurance

Terms & Conditions•Privacy Policy•
© 2026 Jentic Technology Ltd. All rights reserved.
2 Grattan Court East, Dublin, D02 VX86, Ireland
Switch to light modeSwitch to dark mode
APIs / Storage / BrewPage API
BrewPage API logo

Brewpage App BrewPage API

53
AI ReadinessNon-Ready (C)53/100
See full scorecard
Official vendor OpenAPI document · agent-readyStorageObject StorageapiKey74 EndpointsREST

For Agents

Publish HTML, Markdown, JSON, files, key-value stores, and zipped sites to shareable brewpage.app links, then update, password-protect, rotate, or delete them with an owner token.

Use for: I need to publish an HTML report and share the link, Set up a key-value store for small shared state between runs, Retrieve a JSON document I published earlier by its namespace and id, I want to password-protect a page I already published

Not supported: Does not handle build pipelines, serverless functions, databases with queries, or domain registration. Use for publishing pages, files, JSON, and key-value data to shareable links only.

The BrewPage API publishes HTML pages, Markdown, JSON documents, key-value stores, single files, and multi-file sites to instant short links on brewpage.app. Each publication lives under a namespace and id, can carry a reader password, a ttl, and tags, and can be listed publicly with ns=public or kept unlisted in a private namespace. Owners holding an X-Owner-Token can update or delete what they published, rotate a link, reset its management key, read per-publication stats, and attach a custom hostname. Anonymous publishing works for the create and read routes, so a client can host content before it has any token.

Jentic One on GithubView OpenAPI Document

Install Jentic One Beta

Connect the BrewPage API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the BrewPage API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

1

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fbrewpage.app%2Fbrewpage" | sh
2

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fbrewpage.app%2Fbrewpage" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with BrewPage API.

Publish an HTML or Markdown page to a short link with POST /api/html, with optional ttl, tags, and reader password

Host a JSON document and fetch or replace it later by namespace and id

Create a key-value store and upsert, read, list, or delete individual keys

Upload a single file or a multi-file site archive and serve its files from one link

Rotate a publication's link, reset its management key, or set a reader password through X-Owner-Token or X-Manage-Key

Attach a custom hostname to a publication and check its DNS status

Read view stats for a publication and list everything published under your owner profile

Use Cases

Patterns agents use BrewPage API for, with concrete tasks.

★ AI agent publishing its output as a shareable page

A coding or research agent that produces an HTML report needs somewhere to put it that a human can open. Through Jentic the agent searches for 'publish an HTML page', loads the BrewPage create_1 operation, and posts the page body to POST /api/html with a private namespace and an optional X-Password. BrewPage returns the link and a management URL, and the owner token is injected by Jentic on later updates so the agent can revise the same page instead of publishing duplicates.

POST a generated HTML report to /api/html with a ttl and an X-Password header, return the link to the user, then update it via PUT /api/html/{ns}/{id} after a correction

Lightweight key-value state for scripts and agents

Scripts and agents that run in separate sessions often need a tiny shared store for a cursor, a flag, or a last-run timestamp. BrewPage creates a key-value bucket with POST /api/kv, then exposes per-key reads, upserts, and deletes under /api/kv/{ns}/{id}/{key}. A password on the bucket keeps casual readers out, and the whole bucket can be removed in one call when the job ends.

Create a KV store with POST /api/kv using key 'last_run' and a timestamp value, then upsert the key via PUT /api/kv/{ns}/{id}/{key} on each run and read it back with GET /api/kv/{ns}/{id}/{key}

Static site and file drop

A developer who wants to show a prototype or hand over a build artifact can upload a site archive or a set of files to POST /api/sites, or a single file to POST /api/files. BrewPage serves the site's files from one short link, and the owner can republish with PUT /api/sites/{ns}/{id} or replace a file with PUT /api/files/{ns}/{id} without changing the URL.

Upload a zipped prototype via POST /api/sites with an archive part and entry index.html, then republish an updated archive with PUT /api/sites/{ns}/{id}

Custom domain and link hygiene

Owners who outgrow the default link can add a hostname to their profile with POST /api/domains, attach a publication to it with PUT /api/domains/{hostname}/attachment, and trigger a DNS check with POST /api/domains/{hostname}/check. If a link has been shared too widely, POST /api/{type}/{ns}/{id}/rotate issues a new id and the old link stops working, and the management link can be reset the same way.

Add docs.example.dev with POST /api/domains, attach an HTML publication via PUT /api/domains/{hostname}/attachment with type, ns, and id, then run POST /api/domains/{hostname}/check

Key Endpoints

74 endpoints — the brewpage api publishes html pages, markdown, json documents, key-value stores, single files, and multi-file sites to instant short links on brewpage.

METHOD

PATH

DESCRIPTION

POST

/api/html

Create an HTML page

PUT

/api/html/{ns}/{id}

Update an HTML page

POST

/api/json

Create a JSON document

POST

/api/kv

Create a key-value store

PUT

/api/kv/{ns}/{id}/{key}

Upsert a key

POST

/api/sites

Upload a site

POST

/api/files

Upload a file

GET

/api/publications

List my publications

POST

/api/html

Create an HTML page

PUT

/api/html/{ns}/{id}

Update an HTML page

POST

/api/json

Create a JSON document

POST

/api/kv

Create a key-value store

PUT

/api/kv/{ns}/{id}/{key}

Upsert a key

POST

/api/sites

Upload a site

POST

/api/files

Upload a file

GET

/api/publications

List my publications

Jentic AI Readiness Score

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

B

BrewPage API

- Non-Ready (C)
53/100
35
Foundational Compliance
63
Developer Experience & Jentic Compatibility
45
AI-Readiness & Agent Experience
90
Agent Usability
50
Security
74
AI Discoverability
Powered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.2
Show dimension breakdown
35

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: FSignals: 4
39%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

0%

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

0%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

63

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: B-Signals: 4
1%

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

50%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

45

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: DSignals: 4
44%

Description Coverage

Coverage of descriptions across API elements.

0%

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

78%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

57%

Summary Coverage

Coverage of summaries across operations/tags/info.

90

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1
90%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

50

Security

Trust, risk posture, and security compliance.

Grade: C-Signals: 1
50%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

74

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: A-Signals: 1
74%

Descriptive Richness

Clarity and depth of descriptions across API elements.

View full reportHow the score is calculatedMore about the dimensions

Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

Score your own APIScoring CLI agent skill
npx @jentic/api-scorecard-cli score <openapi-url>

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring BrewPage by hand means juggling three header credentials: X-Owner-Token for your profile, X-Manage-Key per publication, and X-Password for protected reads, and remembering which routes accept anonymous calls. Through Jentic you install once, import BrewPage from the API Directory, store the owner token once, and your agent calls it.

Permission scoping

BrewPage puts the namespace and publication id in the URL path (/api/html/{ns}/{id}, /api/kv/{ns}/{id}/{key}), so a rule can pin your agent to one namespace or one publication for updates, reads, and deletes. Creates carry ns as a query parameter, so for those a rule bounds which operations the agent may call. You choose the operations it may call, so destructive ones like DELETE /api/kv/{ns}/{id} or POST /api/owner-token/revoke-others are not included unless you add them.

Credential isolation

Your BrewPage owner token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'publish an HTML page' or 'store a key value', and Jentic returns the matching BrewPage operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Netlify API

→

Full site deployment platform with builds, functions, and DNS, heavier than BrewPage's instant links.

Choose Netlify when the agent must deploy a built project with continuous deployment, serverless functions, or forms; choose BrewPage for a quick shareable page or file.

Alternative

Pastebin API

→

Text paste hosting for snippets and logs rather than rendered HTML or sites.

Choose Pastebin when the output is plain text or code to paste; choose BrewPage when it should render as a page or be stored as JSON or key-value data.

Complementary

GitHub v3 REST API

→

Source control and Gists, often the origin of the content an agent then publishes.

Use GitHub when the agent needs to read or commit source; pair it with BrewPage to host a rendered preview of what it built.

FAQs

Specific to using BrewPage API through Jentic.

What authentication does the BrewPage API use?

The BrewPage OpenAPI spec declares three header schemes: OwnerToken (the X-Owner-Token header) identifies your owner profile, ManageKey (the X-Manage-Key header, taken from a publication's manageUrl) gives full control of one publication, and Password (the X-Password header) unlocks a password-protected publication for reading. Many create and read routes, such as POST /api/html and GET /api/json/{ns}/{id}, accept anonymous calls, while profile routes like GET /api/publications and the /api/domains family need X-Owner-Token. A fresh owner token can be minted with GET /api/owner-token.

Can I store small pieces of state with the BrewPage API?

Yes. POST /api/kv creates a key-value store with an initial key and value, PUT /api/kv/{ns}/{id}/{key} upserts a key, GET /api/kv/{ns}/{id}/{key} reads it, and GET /api/kv/{ns}/{id} lists the keys. DELETE /api/kv/{ns}/{id} removes the entire bucket. Adding an X-Password at creation keeps readers without the password out.

What are the rate limits for the BrewPage API?

The OpenAPI spec does not specify request rate limits. GET /api/limits returns the upload size limits per publication type, which is the figure to check before posting a large file or site. For current usage terms, see https://brewpage.app/terms.

Is there a BrewPage MCP server?

You don't need an MCP server to give your agent BrewPage. Jentic connects it directly from the API Directory: import it, store your owner token once, and your agent calls the publish and update operations it needs, discovered on demand rather than loaded as tool definitions into its context.

Can I limit what my agent is allowed to do with BrewPage?

Yes. For example, write a rule that allows only POST /api/html and PUT /api/html/{ns}/{id} under your own namespace, so the agent can publish and revise pages but cannot call DELETE routes, rotate links, mint owner tokens, or change domains. Every call it makes is recorded in the audit log.

How do I publish a page through Jentic?

Add BrewPage to your Jentic One instance from the directory and store your X-Owner-Token. Your agent then searches for 'publish an HTML page', loads the create_1 operation for POST /api/html, and sends the page body with an optional ttl and tags. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Is a private BrewPage link the same as a protected one?

No. The spec notes that a private link is not a lock: anyone holding it can open the publication. To restrict reading, set a password with POST /api/{type}/{ns}/{id}/password or send X-Password on create, and use POST /api/{type}/{ns}/{id}/access/revoke to revoke reader access to a protected publication.

GET STARTED

Start building with BrewPage API

Explore with Jentic One
View OpenAPI Document