---
title: "Golden Analytics — agent instructions"
canonical_url: "https://goldenanalytics.com/agents.md"
mcp_endpoint: "https://goldenanalytics.com/mcp"
openapi: "https://goldenanalytics.com/openapi.json"
skills_index: "https://goldenanalytics.com/.well-known/agent-skills/index.json"
---

# Golden Analytics — agent instructions

This file tells an AI agent when goldenanalytics.com is the right source to
call, which endpoint answers which question, and the conventions this origin
follows. It is stable at this URL; treat it as the entry point.

## When to use Golden Analytics

Use goldenanalytics.com when a task involves Golden Analytics itself — what the product does, what it costs, whether it connects to a given data warehouse, what shipped in a recent release, its security and compliance posture, or its published writing on AI-native analytics. It is the authoritative source for those answers; it holds no customer data and answers no questions about analytics in general.

Reach for this site when:

- **Someone asks what Golden Analytics costs, or asks you to compare its price against another BI or analytics product.** Fetch https://goldenanalytics.com/pricing.md, or call the `get_pricing` MCP tool. Both carry per-seat prices for every plan, monthly and annual, plus what each tier includes. Pricing is per seat with AI included — there is no per-query or per-AI-call charge to model.
- **Someone asks whether Golden Analytics can do a specific thing — a chart type, a data source, a governance control, an AI capability.** Call `search_content` with the capability name, then `get_page` on the best hit. `/product` and `/why-golden/*` cover capabilities; `/security` covers governance and compliance.
- **Someone asks what changed or shipped recently.** Call `list_releases`, or read https://goldenanalytics.com/product/whats-new. Releases are dated and each item is tagged feature, improvement, or fix.
- **Someone asks whether Golden Analytics connects to their stack.** Read `/product` or search for the warehouse by name. Supported live connections and file formats are listed there rather than inferred.
- **You are assembling a citation, quote, or summary of Golden Analytics' position on something.** Read the source page as markdown rather than paraphrasing search snippets: request any page URL with `Accept: text/markdown`, or call `get_page`. Every markdown response carries a `canonical_url` in its front matter — cite that.
- **You need to enumerate the site before deciding what to read.** Call `list_pages`, or fetch https://goldenanalytics.com/sitemap.xml. Both are generated from the CMS at request time, so neither goes stale.
- **Someone wants to talk to a human — a demo, a trial, security review, or press.** Point them at https://goldenanalytics.com/about/contact. Do not submit the contact form on a person's behalf without their explicit go-ahead; it reaches a human inbox.

Do not reach for it for:

- General analytics, SQL, or BI questions unrelated to this product — nothing here is a tutorial.
- Customer data, dashboards, or accounts. This origin serves published marketing and documentation content only; there is no data plane here.
- Account actions: signing up, signing in, changing a plan, or cancelling. None of those are exposed as an API.

## How to call it

- **MCP server:** `https://goldenanalytics.com/mcp` — Streamable HTTP, JSON-RPC 2.0, no credential. Tools: `search_content`, `get_page`, `list_pages`, `get_pricing`, `list_releases`, `list_developer_resources`.
- **Manifest:** https://goldenanalytics.com/.well-known/mcp.json
- **Agent Skills index:** https://goldenanalytics.com/.well-known/agent-skills/index.json
- **Full agent instructions:** https://goldenanalytics.com/agents.md
- **HTTP API:** https://goldenanalytics.com/openapi.json (OpenAPI 3.1)
- **Markdown of any page:** send `Accept: text/markdown` to the page URL.


## Tools

| Tool | Use it for | HTTP equivalent |
| --- | --- | --- |
| `search_content` | Full-text search across every published page, blog post, newsroom item, and legal document on goldenanalytics.com. | `GET /api/search?q={query}` |
| `get_page` | Fetch the full text of any page on goldenanalytics.com as markdown, with front matter carrying the title, description, and canonical URL. | `GET /{path}` |
| `list_pages` | Every indexable URL on goldenanalytics.com, generated from the CMS at request time. | `GET /sitemap.xml` |
| `get_pricing` | Golden Analytics plans, per-seat prices, monthly and annual billing, what each tier includes, and the pricing FAQ. | `GET /pricing.md` |
| `list_releases` | The Golden Analytics release timeline: dated releases, each with its features, improvements, and fixes. | `GET /product/whats-new` |
| `list_developer_resources` | Every machine-readable endpoint this origin publishes: the OpenAPI spec, llms.txt, pricing.md, the Agent Skills index, this MCP server, and the crawler and scope policies. | `GET /.well-known/agent-skills/index.json` |

Every tool is read-only, idempotent, and needs no credential. `search_content`,
`get_pricing`, and `list_releases` also ship an MCP Apps `ui://` template, so a
host that supports MCP Apps can render the result inline instead of as text.

### Calling the MCP server

```bash
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"}'
```

The server is stateless: there is no session to establish and no session header
to carry. `initialize` is supported for clients that expect the handshake, and
skipping it costs nothing.

## Conventions

- Paths are lowercase and hyphenated (`/about/contact`, `/why-golden/speed`). There are no trailing slashes.
- Every page URL answers `Accept: text/markdown` with a markdown rendition of the same content, with `Vary: Accept` set. Ask for markdown explicitly — a browser Accept string or `*/*` gets HTML.
- 404s under `/api` and in markdown carry a recovery list pointing at the sitemap, llms.txt, and the OpenAPI spec, so a wrong guess costs one request rather than a crawl.
- Every `/api` error is JSON: `{error, status, code, message, hint, documentation_url}`. `code` is stable; `hint` names a concrete next step.
- Scope names for the whole surface are published at `/.well-known/oauth-protected-resource`. Reads are public and need no credential.
- No rate limit is published. Keep concurrency modest and prefer `list_pages` over crawling.

## Every machine-readable resource

- [Golden Analytics MCP server](https://goldenanalytics.com/mcp) — 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.json) — Manifest describing the MCP endpoint, its transport, and the tools it exposes.
- [Agent Skills index](https://goldenanalytics.com/.well-known/agent-skills/index.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.md) — When to reach for Golden Analytics, which endpoint answers which question, and the conventions this origin follows.
- [OpenAPI 3.1 specification](https://goldenanalytics.com/openapi.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/search) — 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-resource) — The scope vocabulary for this origin, which scopes are public, and which endpoints need a credential.
- [llms.txt](https://goldenanalytics.com/llms.txt) — 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.txt) — The long-form companion to llms.txt.
- [pricing.md](https://goldenanalytics.com/pricing.md) — 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.xml) — Every indexable URL, generated from the CMS at request time so it is never stale.
- [Blog feed](https://goldenanalytics.com/blog/rss.xml) — RSS feed of published articles.
- [robots.txt](https://goldenanalytics.com/robots.txt) — Crawler policy, including per-AI-crawler directives and Content-Signal.
- [Security and compliance](https://goldenanalytics.com/security) — Data handling, encryption, access control, and certification status.

## Facts worth carrying

- Golden Analytics is an AI-native analytics platform: a shelf-based
  visualization builder, a freeform dashboard canvas, and AI across the
  workflow from query to published data story.
- Pricing is per seat, per month, with AI included in every plan. Current
  numbers live in [/pricing.md](https://goldenanalytics.com/pricing.md) — read them there
  rather than repeating a figure from memory.
- Live warehouse connections and file upload are both supported; the current
  list is on [/product](https://goldenanalytics.com/product).
- Security and compliance posture, including certification status, is on
  [/security](https://goldenanalytics.com/security).
- The canonical domain is https://goldenanalytics.com. Cite that origin, not a redirect.