Who may call it, and what it costs
Price. Free. A full text (
format: "full") of an answer or a page needs credits: the workspace’s own answers and pages free, and public ones 25 a day free, then $0.005 each, shown in meta.costCredits. A public answer older than 90 days costs $0.001 the first time the workspace counts or lists it, and is the workspace’s after, shown in meta.costCredits. An export’s rows were counted when the file was written. Every reply says what the call cost in meta.costCredits. The prices are on Spending, tracking and stopping.
Arguments
ids of one kind: ans_ (up to 10), pg_ or URLs (20 with text, 100 when fields leaves text out), one exp_, or job_/cf_ (up to 25) up to 100
the parts to return. Answers: the parts to return, besides each answer’s id, date, engine and question; default all five. Without text, ten answers fit one compact reply. Pages: the parts of each page to return (ids always stay); a part left out is not loaded. Default omits “contact” ($0). Pass fields: [“contact”] to unlock actionable contact routes ($0.05 each, free on misses, bare author names, and 90d repeats) up to 12
full: whole text for up to 5 answers or 3 pages, free with credits within the day’s allowance
answers and pages: brd_ ids to mark, and on pages to answer for, besides the brands each names up to 20
jobs: seconds to wait for the jobs to finish, at most 50: the call returns as soon as none is queued or running or a first run’s first look arrives, else when the time is up. Saves polling min 1, max 50
jobs: with one job_ id of an ask: the whole ask_ai_engines call that wrote it, its totals and its jobs 25 a page (cursor for the next); wait is not used
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
Read the text of answers and the brands each names, from ids a search returned. Over REST:- Read the whole text: free with credits, within the day’s full texts:
{"ids":["ans_…"],"format":"full"} - Who to write to about a page, for up to 100 pages:
{"ids":["pg_…"],"fields":["contact"]} - Read a page of the file an export wrote, through the service, with no fetch tool:
{"ids":["exp_…"],"limit":200} - The status and results of an ask or a baseline, holding the call up to 30 seconds until it finishes:
{"ids":["job_…"],"wait":30}
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.