POST /research takes one focused objective and returns a synthesized answer. Start with tier: "standard" for company-level research.
curl --request POST \ --url https://api.tryhuntr.com/research \ --header 'content-type: application/json' \ --header "x-api-key: ${HUNTR_API_KEY}" \ --data '{ "prompt": "We sell cloud cost-optimization software to large enterprises. Research Shell'\''s IT and digital organization: who owns cloud infrastructure and FinOps decisions, initiatives announced from December 2024 through June 2026, and practical conversation angles tied to cost pressure.", "tier": "standard" }'
When your workflow needs predictable top-level fields, pass a flat schema map. Keys become result fields; values describe what each field should contain.
curl --request POST \ --url https://api.tryhuntr.com/research \ --header 'content-type: application/json' \ --header "x-api-key: ${HUNTR_API_KEY}" \ --data '{ "prompt": "We provide fraud-prevention APIs for fintech platforms and are building an account plan for Stripe. Research enterprise product initiatives from June 2025 through June 2026, partnership angles for a fraud vendor, and deal risks.", "tier": "deep", "schema": { "summary": "Concise account summary", "recommended_angles": "Array of concrete partnership angles", "risks": "Array of risks that could stall the deal" } }'
The schema value is a field map, not JSON Schema. Nested schema definitions are not supported.Structured responses include a confidence object per field (live, model, or not_found). Fields marked not_found are returned as null.