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
plan: work to do (planned); log: something done (default); update: change an item (with item)
what happened or is planned, in your words; pasted email text is fine (up to 4,000 characters)
pitch, listing_request, reply, page_written, page_edit, site_fix or note; plan (or todo, task) is a to-do, as move plan; the older published, pitched, reply, listed, declined, fixed still work
outreach: planned, drafted, sent, no_reply, replied, declined; content: planned, drafted, published; site_fix: planned, shipped; note: noted, planned, done (open, todo and pending mean planned; bounced, failed, not sent mean planned, the word kept). An explicit status wins over the kind’s default. won and live are recorded as reported until Parse’s monitoring agrees
what it is aimed at: a page URL or pg_ id, a site (domain or site:), a contact’s email or ct_ id, a top_ id
who it went to: “Jane Doe, Editor, [email protected]”, an address, a ct_ id, or { name, role, email, site }
who does the work, to hand it to someone: a person’s name; default this key’s label on a new item. Who wrote each change is kept on its event
when it happened: a date, or yesterday or a weekday; default today. A page that went up yesterday is at yesterday
several notes in one call (up to 50), each with the fields above; the call’s own fields apply to each as defaults up to 50
tools/list 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:
Example call
A note as you have it: Parse files it as an item on the page, with the contact, and replies with what it understood. Over REST:- Plan several pieces of work at once: to-dos are items in planned:
{"move":"plan","brand":"<brd_ id>","items":[{"kind":"pitch","target":"https://example.com/best-tools","due":"2026-11-20"},{"kind":"page_written","topic":"pricing comparison","owner":"Dana"}]} - Update an item: a second session or another agent writing the same brand, kind and target updates it too:
{"item":"itm_…","status":"replied","text":"The editor wants a quote from the CEO"} - The older call, which works as before: a pitch sent to a page:
{"kind":"pitched","page":"https://example.com/best-tools","brand":"<brd_ id>","note":"Emailed the editor"}
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.