nimble_agent_templates_get
ChatGPTGet a Web Search Agent gallery template. Not an Extract Template.
By Nimble
Nimble gives agents governed, accurate access to the public web, at a lower token cost per answer. Search finds current pages with ranked results and snippets. Extract returns clean, structured content from any URL, including pages needing JavaScript or interaction. Extraction Templates give consistently shaped records from known sites. Web Search Agents handle open-ended work across many sources, returning findings with citations, for research, enrichment, and dataset building. Also included: ready-made workflows for competitor research, company profiles, meeting prep, market discovery, brand monitoring, SEO, and talent sourcing.
template (from nimble_agent_templates_list) when a gallery blueprint matches; otherwise describe the agent via name/goals/sources. Classify use_case`: research = dossiers/briefings/synthesis; dataset_building = entity lists/catalogs/extract-all without a URL; enrichment = add fields to records the user already has. Set effort from the task — do not ask the user to pick: low/medium simple, high default, x-high/max complex; dataset_building requires high or above. For a one-shot, prefer nimble_agents_run(agent_name=...) create-or-reuse instead of create-then-run.id and status. Poll nimble_agents_run_status until terminal, then nimble_agents_run_result. Provide agent_id to run an existing agent, or agent_name to create-or-reuse by name (the one-shot path). Classify use_case` when creating: research = dossiers/briefings/synthesis; dataset_building = entity lists/catalogs/extract-all without a URL; enrichment = add fields to records the user already has. Set effort from the task — do not ask the user to pick: low/medium simple, high default, x-high/max complex; dataset_building requires high or above.limit. Poll nimble_crawl_status for progress. Use this only when you need many pages from a site discovered and extracted automatically — it is the slowest of the extraction paths to first result. For a single known URL you want inline, use nimble_extract; for one URL where you can wait and poll, use nimble_extract_async.wait is set); a page that requires a login or returns a consent/interstitial prompt may yield little or no content. If you have many URLs to extract, or your turn's latency budget can't absorb a slow page, use nimble_extract_async instead. For discovering and pulling many pages across a whole site, use nimble_crawl_run.nimble_extract on comparable pages — it is not a faster route to the same content). After starting, poll nimble_task_results with the returned task ID, or supply callback_url to be notified on completion. Prefer this path when extracting many URLs in parallel, or when a single synchronous call would blow your turn's latency budget. For one URL you need inline now, use nimble_extract. For crawling many pages across a site, use nimble_crawl_run.generation_id; poll nimble_extract_templates_generation_status until terminal (completed or failed`). On completion, run via nimble_extract_templates_run.pending / processing / etc.): call again after ~30 seconds. - completed: template_name and version_id are set; proceed to run. - failed / error: inspect error` for diagnostics.generation_id; poll nimble_extract_templates_generation_status until terminal, then run with the returned template_name`.Click any prompt to copy it.