Skip to main content
Change brief schedule, nudges, pace, or monthly budget (lowering budget, pausing spend, validated webhook, and alerts apply immediately; raising budget or resuming spend returns needs_confirm for an admin). Also manages private saved topics (topic), data/claim error reports (correction), unconfirmed brand facts (fact), brand background (about), and push ping URL (wake — sends empty ping; call get_brief on arrival). Send one form per call. Free.

Who may call it, and what it costs

Price. Free. Every reply says what the call cost in meta.costCredits. The prices are on Spending, tracking and stopping.

Arguments

object
To have the brief delivered to an address, set webhookUrl (https) with the webhook channel: Parse sends it there. maxPerWeek limits each channel separately. Weekly and on-change email uses the Monday slot; daily email uses hour in workspace time. Webhooks use hour and timeZone for scheduled deliveries. alerts: kinds sent at once (default fact_contradicted)
one of on_change, daily, weekly, off
list of one of webhook, email
up to 2
string or null
number
min 1, max 50
one of tracked, all
boolean
integer
min 1, max 21
integer
min 0, max 23
string
list of one of fact_contradicted, proof_step_blocked, own_page_changed, page_changed, page_dropped, page_first_cited, mention_move, rival_move, finding
up to 9
boolean
one of off, light, steady, fast
off|light|steady|fast: how often Parse watches claimed tasks, checks outcomes and scouts questions by itself, within the budget; any pace applies at once
object
monthlyUsd: the workspace’s one monthly budget, everything Parse spends for it in a UTC month. paused: true pauses spending at once; false asks a person to resume it
number
min 1, max 300000
boolean
object or null
the wallet’s auto top-up: a person’s setting, refused from an assistant
any
the standing instructions get_brief opens with: a person writes them in Settings, refused from an assistant
object
one fact this workspace holds about a brand it saved or tracks, with where you got it (source). Stored unconfirmed until a person confirms it in Parse or Parse finds it on the brand’s site; delete: true withdraws it. Alone, without settings
string
required
brd_ id of a brand in this workspace, saved or tracked
one of one_liner, audience, buyers, claim, not_offered
required
one_liner (what the brand is), audience (who it is for: the kind of customer), buyers (only the geographic regions or cities it serves, never a kind of customer), claim (one thing it offers), not_offered (one thing it does not offer)
string
the fact, as one statement; with delete, the claim or not_offered to withdraw
string
required
where you got it: a URL, “person” when the person told you, or a file or note reference
boolean
withdraw this workspace’s fact of that kind
object
the brand’s background every agent reads in get_brief (positioning, launches, rivals), replacing what it held; shown as an assistant’s until a person saves it. Alone, without settings
string
required
string
required
object
lower one brand’s monthly allowance, a slice of the budget an admin set for that brand: a lower figure applies at once; setting or raising one is an admin’s, in Parse. Alone, without settings
string
required
brd_ id of a brand of this workspace
number
required
min 0, max 300000
object
a wake address you may set yourself: url (https) and an optional bearer token for the receiver, which no call shows again. Parse POSTs {“type”:“parse.wake”} to it, and nothing else: no workspace, no text, no ids. The receiver then calls get_brief. url: null turns it off. Alone, without settings
string or null
required
string or null
object
a private topic: id alone shows it; name and include save a new one; id with name, include or exclude changes it; id with delete: true deletes it. Alone, without settings
string
top_saved_ id: alone shows the topic; with name, include or exclude changes it
string
required to save a new topic; with id, renames it
object
questions to add
object
boolean
with id: delete the saved topic
object
a wrong fact, in Parse’s data or claimed on any page or in any answer: kind not_this_brand (brand with site or page), wrong_market (market), off_target_topic (topic), duplicate (otherBrand), wrong_judgment (answer, judgment), other (note: a page’s or an answer’s wrong claim, with its URL or ans_ id). Alone, without settings
one of not_this_brand, wrong_market, off_target_topic, duplicate, wrong_judgment, other
required
string
brd_ id the fact is about
string
a domain or site: id (not_this_brand)
string
pg_ id; for not_this_brand its site stops counting as the brand’s
string
mkt_ id (wrong_market)
string
top_ id (off_target_topic)
string
ans_ id (wrong_judgment)
string
brd_ id of the second record (duplicate)
object
the facet and the value it should have (wrong_judgment)
string
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:

Example call

Lower the workspace’s monthly budget to $10. Over REST:
Over MCP, the assistant calls the tool by name with the same arguments:
More calls:
  • Send the brief once a week: {"brief":{"schedule":"weekly"}}
  • Save a set of questions as a private topic: {"topic":{"name":"Agency project management","include":{"questions":["qst_…"]}}}
  • Delete a saved topic: {"topic":{"id":"top_saved_…","delete":true}}
  • Tell Parse a site is not the brand’s: {"correction":{"kind":"not_this_brand","brand":"<brd_ id>","site":"example.com","note":"This site belongs to another company with the same name"}}
  • Write the brand’s background every agent reads in get_brief: send the whole text, which replaces what it held: {"about":{"brand":"<brd_ id>","text":"Observability for platform teams. We launch the mobile app in December; buyers compare us with Datadog."}}
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.