Owler

Setup

Wiring this Owler API by hand means placing your access key in the custom user_key header on every request and reconciling its many company-search and competitor variants yourself. Through Jentic you install once, import the Owler API from the API Directory, store the key once, and your agent calls it.

Permission scoping

Owler puts the company id in the URL path (/v1/company/id/{companyId}), so a rule can pin your agent to one company for reads like its detail and competitor lists. You choose the operations it may call, so basic search and fuzzy search are not included unless you add them.

Credential isolation

Your Owler user_key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'find competitors for a company' or 'search companies by name', and Jentic returns the matching Owler operation with its input schema so the agent calls the right endpoint without browsing the reference docs.