What authentication does the Crunchbase API use?

The Crunchbase API uses an API key passed as the user_key query parameter on every request. Through Jentic the user_key is held in the vault and appended to outbound requests so it never enters the agent's context.

Can I search funding rounds with the Crunchbase API?

Yes. POST /searches/funding_rounds accepts structured filters such as date range, investor, and round size, and GET /entities/funding_rounds/{entity_id} returns the full record for a specific round.

What are the rate limits for the Crunchbase API?

The OpenAPI spec does not declare explicit numeric limits. Limits are governed by your Crunchbase data licence - apply backoff on 429 responses and prefer paginated search calls over high-frequency entity lookups.

How do I enrich a CRM record through Jentic?

Run pip install jentic, then search Jentic for 'search crunchbase organizations', load the POST /searches/organizations schema, and execute it with the company name or domain. Pipe the resulting entity_id into GET /entities/organizations/{entity_id} for the full record.

Does the Crunchbase API support autocomplete?

Yes. GET /autocompletes accepts a query and returns matching organizations and people, suitable for typeahead pickers in CRM and prospecting tools.

Can I limit what my agent is allowed to do with the Crunchbase API?

Yes. Because you run Jentic One yourself, your own rules decide which Crunchbase operations and credentials the agent may use, so you can restrict it to just the calls it needs, such as POST /searches/organizations or a single GET /entities/organizations/{entity_id} read. The Crunchbase API is read-only here, so the agent can only query the data you allow and cannot write or modify anything. You can grant search access to people, funding rounds, and acquisitions selectively or withhold it, keeping the user_key credential under your control.