Golden Analytics developer and agent resources

Golden Analytics MCP server

The MCP server at https://goldenanalytics.com/mcp speaks JSON-RPC 2.0 over Streamable HTTP. It is stateless — there is no session to establish and no credential to send — so a single POST is the whole conversation. Point Claude, ChatGPT, or any MCP client at it and the tools below become callable.

{
  "mcpServers": {
    "golden-analytics": {
      "type": "http",
      "url": "https://goldenanalytics.com/mcp"
    }
  }
}

Or call it directly:

curl -X POST https://goldenanalytics.com/mcp \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json, text/event-stream' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

Three of those tools ship an MCP Apps template — a ui:// resource named in the tool’s _meta.ui.resourceUri — so a host that supports MCP Apps renders the result inline instead of as text: ui://golden-analytics/search-results.html, ui://golden-analytics/pricing-table.html, ui://golden-analytics/release-timeline.html.

Agent interface

• Golden Analytics MCP server

  https://goldenanalytics.com/mcpapplication/json

  Model Context Protocol endpoint over Streamable HTTP. Exposes site search, page markdown, pricing, and the release timeline as callable tools, plus ui:// resources for in-conversation rendering. POST JSON-RPC 2.0; no credential required.

• MCP server manifest

  https://goldenanalytics.com/.well-known/mcp.jsonapplication/json

  Manifest describing the MCP endpoint, its transport, and the tools it exposes.

• Agent Skills index

  https://goldenanalytics.com/.well-known/agent-skills/index.jsonapplication/json

  Every capability this site offers an agent, each with a name, description, and the endpoint that serves it.

• Agent instructions

  https://goldenanalytics.com/agents.mdtext/markdown

  When to reach for Golden Analytics, which endpoint answers which question, and the conventions this origin follows.

API

• OpenAPI 3.1 specification

  https://goldenanalytics.com/openapi.jsonapplication/json

  Every public HTTP operation on this origin, with request and response schemas, error codes, and per-operation scope requirements. Also served as YAML at /api/openapi.yaml.

• Search API

  https://goldenanalytics.com/api/searchapplication/json

  Full-text search across published pages, blog posts, and newsroom items. GET with ?q=; returns JSON.

• Protected-resource metadata (RFC 9728)

  https://goldenanalytics.com/.well-known/oauth-protected-resourceapplication/json

  The scope vocabulary for this origin, which scopes are public, and which endpoints need a credential.

Content

• llms.txt

  https://goldenanalytics.com/llms.txttext/plain

  Condensed site guide for language models: what the product does, who it is for, and where each section lives.

• llms-full.txt

  https://goldenanalytics.com/llms-full.txttext/plain

  The long-form companion to llms.txt.

• pricing.md

  https://goldenanalytics.com/pricing.mdtext/markdown

  Plans, per-seat prices, what each tier includes, and the pricing FAQ, as plain markdown. Generated from the same CMS content as the /pricing page.

• Sitemap

  https://goldenanalytics.com/sitemap.xmlapplication/xml

  Every indexable URL, generated from the CMS at request time so it is never stale.

• Blog feed

  https://goldenanalytics.com/blog/rss.xmlapplication/rss+xml

  RSS feed of published articles.

Policy

• robots.txt

  https://goldenanalytics.com/robots.txttext/plain

  Crawler policy, including per-AI-crawler directives and Content-Signal.

• Security and compliance

  https://goldenanalytics.com/securitytext/html

  Data handling, encryption, access control, and certification status.

Conventions

• Markdown for any page

  Send Accept: text/markdown to any page URL and the response is that page as markdown, with front matter carrying its title, description, and canonical URL. Responses set Vary: Accept. Markdown has to be named explicitly — a browser Accept header still gets HTML.

• JSON errors

  Every error under /api is JSON: {error, status, code, message, hint, documentation_url}. code is stable and hint names a concrete next step. 404s carry a recovery list, so a wrong URL costs one request rather than a crawl.

• Scopes

  The scope vocabulary for this origin is published as RFC 9728 protected-resource metadata at /.well-known/oauth-protected-resource, and per-operation in the OpenAPI spec as x-required-scopes. Reads are public.

• Questions

  Something missing, or an endpoint behaving oddly? Get in touch.