> ## 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.

# Data and trust

> What Parse collects and stores, how an assistant reaches a workspace, how long records are kept, what Parse is certified for, and whom to contact.

The [Privacy Policy](https://parse.gl/privacy) and [Terms of Service](https://parse.gl/terms) are the binding texts. This page says what they mean for a team evaluating Parse or connecting an assistant to it.

## What Parse collects

* Parse asks AI engines the questions in its index and records their answers, the brands they name and the pages they cite. It does not read anyone's private AI conversations.
* The questions it tracks, and the brand information needed to ask them, go to third-party AI providers to collect the answers.
* A brand's own topics (Custom topics) are kept out of the public index. That does not keep them inside Parse alone: they are sent to the AI providers too.
* Parse uses AI to write question wording, extract and classify brands, and summarize answers. Summaries are labelled AI summary; numbers are counted, not written.

## How an assistant reaches a workspace

* Without a key or a sign-in, `https://agent.parse.gl/mcp` and the REST routes answer Parse's public view only: what the public pages show, no workspace, no contacts. Anything else asks the assistant to sign in.
* A workspace key, made by a person on [Connect](https://parse.gl/app/settings/agents), reaches that one workspace. Revoking it on Connect stops it within a minute; every call is logged with the key that made it.
* Signing in from an assistant reaches the workspace the person picks: reading only with `parse:dashboard:read`, changes and spending also with `parse:dashboard:write`.
* An assistant spends credits within the monthly budget the person sets and asks the person past it; only a person raises the budget. Adding credits, billing, members, keys and removing a brand stay with a person.

## What the agent service stores

Each call to `https://agent.parse.gl/mcp` writes one request record: the tool, the time, the client, the key's label, the status, the duration, the arguments with secrets redacted, and a bounded copy of what came back. Request records are kept for 30 days and read only by Parse's administrators. Keys and bearer tokens are redacted.

* [`get_account`](/docs/mcp/tools/get_account) with `view: "receipt"` lists the workspace's own calls in a time range, with each call's arguments, cost, the data snapshot it read and the rows it returned. It never contains replies.
* Parse also keeps, for the workspace: what it bought (asks, baselines, live fetches, rubric runs) and the jobs that ran; the questions and pages it tracks; its saved topics; the actions it logged; its credit ledger; and every settings change an agent or a person made, with the key or person.
* A count of what the service returned to the workspace each day, so that unusual bulk reading can be seen.
* A live fetch ([`fetch_live_pages`](/docs/mcp/tools/fetch_live_pages)) stores the page privately for the workspace.

## Who can read what a workspace buys

The answers and lists a workspace buys are private to it. A baseline's answers ([`ask_ai_engines`](/docs/mcp/tools/ask_ai_engines) with `baseline`) stay private whatever the switch says. Answers bought with [`ask_ai_engines`](/docs/mcp/tools/ask_ai_engines) are shared only while "Share AI answers with other workspaces" is on, which takes 25% off every check; a ranked list stays the workspace's own. The switch is off to start. The first top-up's screen states the choice as two prices, shared and private, with shared selected, and the person paying may change it before they pay; after that a person changes it in Settings. No agent changes it. Other workspaces can then read what the agents bought and the answers to the workspace's Custom topics, never who asked. After the switch is turned off, answers already bought stay shared; answers to Custom topics are no longer shared.

A reply marks an answer another workspace shares as shared; it is evidence to read, counted in no other workspace's numbers until Parse admits it to its public numbers. Parse admits a shared web-search answer (ChatGPT, Google AI Mode, Perplexity, Gemini, or Claude) to a buyer question its own judges place in a public topic, asked the way Parse asks, and only while shared answers stay within Parse's topic and workspace balance limits; its question's wording can then appear wherever Parse's own wordings do, never who asked.

## Records kept

What Parse keeps about each MCP request, for how long and who can read it is in the [Privacy Policy](https://parse.gl/privacy), under MCP request records, with the rest of Parse's retention and your choices.

Parse keeps a record of each export for 24 months: who read what in bulk, the rows included that month and what the file charged. The record stays after the workspace is deleted, with a person's id cleared.

Parse counts, per workspace and day, the rows it returned outside the workspace's own brands, their markets and what it tracks, and the markets those replies named: 10,000 such rows a day and 50,000 a month are free, over up to 250 markets a day, and further rows cost what an export's do ([prices](/docs/credits.md#paid-calls)). With no key, an address reads 500 rows a day, counted by a one-way hash of the address. Parse is told when a workspace or an address passes half of either in a day.

## Deleting a workspace

There is no delete control in Parse yet. To delete a workspace and its data, a workspace admin writes to [support@parse.gl](mailto:support@parse.gl). Name the workspace. Revoke its keys on [Connect](https://parse.gl/app/settings/agents) first if an assistant still holds one. Parse keeps the export record described above, and what the Privacy Policy says it keeps.

## Certifications

Parse does not hold a SOC 2 report or another security certification. Ask [team@parse.gl](mailto:team@parse.gl) for a security questionnaire.

## Independent numbers

Public numbers do not depend on payment; [Parse for AI systems](https://parse.gl/ai) says how Parse keeps them that way. Errors are corrected in the open on [Corrections](https://parse.gl/corrections).

## Contacts

* Support: [support@parse.gl](mailto:support@parse.gl)
* Privacy: [privacy@parse.gl](mailto:privacy@parse.gl)
* Everything else: [team@parse.gl](mailto:team@parse.gl)
* Parse, Inc., Brooklyn, NY, US

## Related

[Keys and levels](/docs/mcp-reference.md#sign-in) · [Plans and limits](/docs/limits.md)


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