Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the boomurl Publishing 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.
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%2Fboomurl.com%2Fboomurl" | shStep 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%2Fboomurl.com%2Fboomurl" | sh
jentic register # connects your agent to your Jentic One instanceJentic 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.
What an agent can do with boomurl Publishing API.
Publish or update a static website with a single idempotent request
Mint and revoke bearer API keys after email verification
List and read the status and public URL of the sites a key owns
Attach apex or subdomain custom domains to a site
Track custom-domain nameserver delegation and TLS readiness
GET STARTED
Delete a site or disconnect a custom domain
Patterns agents use boomurl Publishing API for, with concrete tasks.
★ AI Agent Site Publishing via Jentic
An agent that generates a web page or report can publish it with boomurl through Jentic without wiring the bearer key or walking the email-verification bootstrap. The agent searches by intent, receives the operation schema, and publishes a site to get a public URL back. This fits agents that produce a document and need to share it at a live address.
Search Jentic for 'publish a static site', load the operation schema, and publish the files to get a public URL
Static Site Publishing
Push static files and get an instant public URL. boomurl creates or updates a site with one idempotent request, so an agent can republish on each change without tracking whether the site already exists, and read the site's status and URL afterward.
Call PUT /api/v1/sites/{name} to publish a static site and receive its public URL
Custom Domain Management
Put a published site on your own domain. boomurl attaches an apex or subdomain to a site and reports nameserver delegation and TLS readiness, so an agent can wire up a custom domain and poll until it is live, then disconnect it when no longer needed.
Call POST /api/v1/sites/{name}/domains to attach a custom domain, then GET /api/v1/sites/{name}/domains/{domain} to check TLS readiness
Site Lifecycle Management
Keep a key's set of sites tidy. boomurl lists the sites a key owns, reads one site's status, and deletes a site when it is retired, so an agent managing many short-lived pages can clean up after itself.
Call GET /api/v1/sites to list your sites, then DELETE /api/v1/sites/{name} to remove one
12 endpoints — the boomurl publishing api publishes static websites and returns an instant public url.
METHOD
PATH
DESCRIPTION
/api/v1/keys/request
Email a code to begin minting a key
/api/v1/keys
Confirm the code and mint an API key
/api/v1/sites
List the sites owned by your key
/api/v1/sites/{name}
Create or update a site (idempotent)
/api/v1/sites/{name}
Get site status and public URL
/api/v1/sites/{name}
Delete a site you own
/api/v1/sites/{name}/domains
Attach a custom domain to a site
/api/v1/sites/{name}/domains/{domain}
Status of one custom domain
/api/v1/keys/request
Email a code to begin minting a key
/api/v1/keys
Confirm the code and mint an API key
/api/v1/sites
List the sites owned by your key
/api/v1/sites/{name}
Create or update a site (idempotent)
/api/v1/sites/{name}
Get site status and public URL
/api/v1/sites/{name}
Delete a site you own
/api/v1/sites/{name}/domains
Attach a custom domain to a site
/api/v1/sites/{name}/domains/{domain}
Status of one custom domain
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the boomurl API by hand means verifying your email to mint a bearer key, publishing with an idempotent PUT, and polling custom-domain delegation and TLS status yourself. Through Jentic you install once, import boomurl from the API Directory, store the key once, and your agent calls it.
Permission scoping
boomurl puts the site name and domain in the URL path (/api/v1/sites/{name}, /api/v1/sites/{name}/domains/{domain}), so a rule can pin your agent to one site and the operations you pick. You choose the operations it may call, so destructive ones like deleting a site or revoking a key are not included unless you add them.
Credential isolation
Your boomurl API key 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 a static site' or 'attach a custom domain', and Jentic returns the matching boomurl operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Alternatives and complements available in the Jentic catalogue.
Specific to using boomurl Publishing API through Jentic.
Is there a boomurl MCP server?
Yes, boomurl offers a hosted Model Context Protocol connector, and you can also connect it directly through Jentic from the API Directory: import it, store your bearer key once, and your agent publishes sites and manages domains without loading another server's tool definitions into its context.
Can I limit what my agent is allowed to do with the boomurl API?
Yes. The site name and domain sit in the URL path, so you write a rule that allows publishing and reading one site, and the agent can republish and check status while deleting a site or revoking a key stays out of reach. Every call is logged by your self-hosted instance.
What authentication does the boomurl API use?
The boomurl API authenticates with a bearer API key, minted after email verification and sent in the Authorization header, per its OpenAPI spec. The key-request and key-mint endpoints are public and need no credential so an agent can bootstrap its first key. Through Jentic the key is stored encrypted by your own Jentic One instance and injected at call time.
Can I attach a custom domain with the boomurl API?
Yes. Attach an apex or subdomain to a site, then read the domain's status to track nameserver delegation and TLS readiness. You can also disconnect a domain later.
What are the rate limits for the boomurl API?
The OpenAPI spec does not specify rate limits. Check the vendor's documentation at https://boomurl.com for current limits.
How do I publish a static site with the boomurl API through Jentic?
Search Jentic for 'publish a static site' and it returns the boomurl publish operation with its input schema; the agent sends the files with one idempotent request and gets a public URL back. To run it on your own infrastructure, install Jentic One from its GitHub repo.
For Agents
Publish static sites and get a public URL, mint and revoke API keys, and attach custom domains with delegation and TLS status. Returns JSON over a bearer-authenticated REST API with public key-bootstrap endpoints.
Use for: I want to publish a static website and get a public URL, Mint an API key after verifying my email, List the sites my key owns, Attach a custom domain to a site
Not supported: Does not build or compile source code, run servers, or store databases. Use for publishing static sites and managing their custom domains only.
The boomurl Publishing API publishes static websites and returns an instant public URL. An agent mints a bearer API key after email verification, then creates or updates a site with a single idempotent request. It also lists and reads the sites a key owns, attaches apex or subdomain custom domains, and tracks nameserver delegation and TLS readiness for each domain.
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.
Base layer of spec validity and structural soundness.
Aggregated quality score from linter diagnostics, weighted by severity.
Percentage of `$ref` references that resolve successfully.
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
Structural correctness score based on schema issues using logarithmic dampening.
Clarity, completeness, and ingestion readiness for developers and tooling.
How richly the API is illustrated with examples.
Percentage of examples that conform to their schemas.
Percentage of operations with complete response definitions (success, client error, server error).
Health of API ingestion, bundling, and resolution within Jentic pipelines.
Semantic breadth, depth, and agent comprehension for AI systems.
Coverage of descriptions across API elements.
Coverage of RFC 9457 Problem Details for error responses.
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
Coverage of summaries across operations/tags/info.
Functional utility, complexity comfort, and AI orchestration readiness.
Agent comfort level based on API operational and structural complexity.
Trust, risk posture, and security compliance.
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
Findability, semantic richness, and reasoning readiness.
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>