API reference
Use your own provider credentials. The endpoints below return errors when required keys are missing. Provider requests may incur charges on your account.
Lead discovery
| POST endpoint | Provider header | Request |
|---|---|---|
| /api/tavily | x-tavily-api-key | query, location (optional) |
| /api/brightdata | x-brightdata-api-key | query, location (optional) |
| /api/places | x-google-places-api-key | query |
Send JSON with Content-Type: application/json. Successful search responses contain a leads array. Coverage and contact completeness depend on the provider; Pindrop does not independently verify every field.
Capabilities and integration limits
GET /api/capabilities returns safe availability flags, never provider keys. GET /openapi.json describes the selected discovery endpoints. GET /api/mcp returns a static manifest; use the repository stdio server for MCP. AI pitch and email tools are available in the browser workspace with separate provider keys. Public proposal hosting and direct CRM synchronization are not available.