> ## Documentation Index
> Fetch the complete documentation index at: /docs/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Assistants connect to Parse over MCP at [https://agent.parse.gl/mcp](https://agent.parse.gl/mcp) (Streamable HTTP). With no sign-in it answers from Parse's public view (the numbers parse.gl's public pages show, up to 5 rows a list), starting with `check_brand`. Signed in with Parse, or sent a workspace key (`parse_mcp_…`), it works in the person's workspace, starting with `get_brief`. Scripts call the same tools over REST at `https://agent.parse.gl/v1/tools/<tool>`.
>
> ```bash
> npx parse-gl init
> ```
>
> To install just the skills: `npx skills add Parsegl/skills`.
> Every tool is also a POST to https://agent.parse.gl/v1/tools/<tool>; its OpenAPI description is https://agent.parse.gl/openapi.json.

# Check a brand: who it is, where it stands, what comes next

> check_brand: a tool that also answers without a key on Parse for agents (agent.parse.gl). Arguments, price, and a call over REST and MCP.

Look up how AI answers talk about a brand, who it loses to, verified product facts, and AI crawler blocks. Call this first for brand positioning, competitor research, AI visibility, or before writing copy about a brand. Takes a website (best), brand name, or brd\_ id. Returns data.kind (measured, thin, unplaced, which, unseen): for measured brands, Recommended share (with share\_named detail) per market, top rivals, weakest topic, and where recommendation share falls short; for ambiguous names (which), the candidate list without reading; for thin/unseen, coverage status and next steps. Up to three query\_metrics reads. No brand score. Free.

## Who may call it, and what it costs

| Name | Access | Effect |
| - | - | - |
| `check_brand` | No key needed over REST, at the free level; a workspace key or sign-in reads in full. | Reads only |

**Price.** Free. Every reply says what the call cost in `meta.costCredits`. The prices are on [Spending, tracking and stopping](/docs/credits.md).

## Arguments

**subject** `string` *required*

the brand's website (best: it settles which company), its name, or a brd\_ id

Every argument the tool takes, as `GET /v1/tools` serves it, every shared object written out; `https://agent.parse.gl/openapi.json` serves the same schema with the filter and the window named once under `components` and pointed to by `$ref`. MCP `tools/list` leaves out the arguments few calls send, and says the filter and the window once, under `search_answers`; `resolve_ids {"kinds": ["argument"]}` lists what it left out, and a call with any of them runs:

```json theme={null}
{
  "type": "object",
  "properties": {
    "subject": {
      "type": "string",
      "minLength": 2,
      "maxLength": 253,
      "description": "the brand's website (best: it settles which company), its name, or a brd_ id"
    }
  },
  "required": [
    "subject"
  ],
  "additionalProperties": false
}
```

## Example call

Answer a first question about a brand in one call: its Recommended share in each of its markets and the brands recommended most beside it. Over REST:

```bash theme={null}
curl -s -X POST https://agent.parse.gl/v1/tools/check_brand \
  -H 'content-type: application/json' \
  -d '{"subject":"notion.so"}'
```

Over MCP, the assistant calls the tool by name with the same arguments:

```json theme={null}
{
  "method": "tools/call",
  "params": {
    "name": "check_brand",
    "arguments": {
      "subject": "notion.so"
    }
  }
}
```

More calls:

* For a name several companies share, get the list to ask the person about: `{"subject":"Mercury"}`

The reply has `data`, `context`, `next`, `page` and `meta`; follow `next` for the calls that come after. A refused call returns `{ code, message, fix }`: see the [error table](/docs/mcp-reference.md#errors).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.