BrandGhost for agents

Read public information about BrandGhost without an account or API key. These interfaces do not access customer accounts, private campaigns, or authenticated application tools.

Site discovery OpenAPI API discovery catalog JSON tool catalog Hosted-blog discovery

Read canonical pages

Request the homepage, /pricing, or /launchpad with Accept: text/markdown. Ordinary browser requests receive HTML. Both representations use the same canonical URL. Follow the blog's own discovery document for its article inventory and supported representations.

Public HTTP operations

All operations use GET and return JSON. Successful results may be cached for five minutes. A best-effort, per-instance limit allows 30 requests per client in 60 seconds across agent endpoints. HTTP 429 includes Retry-After; errors are not cached. This is not a guaranteed global quota.

Understand BrandGhost

GET /api/agent/overview

Get BrandGhost's public company positioning, products, capabilities, and intended customers.

BrandGhost Products

GET /api/agent/products

List BrandGhost's current public products and product areas.

BrandGhost Product Details

GET /api/agent/product

Look up a product by id or loose name. Unknown or empty queries return HTTP 200 with found: false and availableProducts.

product: Product id or name, such as launchpad. The server truncates to 120 characters; omitted input is an empty query.

Find BrandGhost Use Case

GET /api/agent/use-case

Find deterministic informational guidance for a business type. Unmatched or empty input returns HTTP 200 with matched: false, not a validation error.

business_type: Industry or company type. The server truncates to 200 characters; omitted input is empty.

problem: Optional business problem. The server truncates to 400 characters.

BrandGhost Pricing

GET /api/agent/pricing

Get current public plans, prices, limits, and plan-selection guidance. Custom pricing has a null numeric price, not zero.

Browser WebMCP

In secure, supported browsers, BrandGhost progressively registers these read-only operations using the experimental document.modelContext API. Tools are enabled unless the deployment explicitly disables them. Unsupported browsers retain the ordinary website without a polyfill. Registration is asynchronous and failed registrations are reported, not counted as success.

The JSON catalog documents the public HTTP operations; it is not a remote MCP server. Browser-native support is experimental and does not guarantee that an external agent will discover, invoke, rank, or cite this website.