canonical: https://jentic.com/apis/owler.com/owler

# Owler

Search for information on companies using a website or company name and get access to Company Data, News, Blog Posts, Competitor Lists and much more.

## For AI agents

Search for information on companies using a website or company name and get access to Company Data, News, Blog Posts, Competitor Lists and much more.

## Scope

Provides access to Owler functionality as defined in the OpenAPI specification.

## Capabilities

- Basic Search Company by Ticker or Website or Name or PermID
- Get Competitor information by Id
- Get Competitor information by URL
- Get Competitor information by Id
- Get Competitor information by Url

## Use cases

### Basic Owler Integration

Integrate Owler into your application to access its core functionality.

Example prompt: Use the Owler API to access vendor services and data.

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/v1/company/basicsearch` | Basic Search Company by Ticker or Website or Name or PermID |
| GET | `/v1/company/competitor/id/{companyId}` | Get Competitor information by Id |
| GET | `/v1/company/competitor/url/{website}` | Get Competitor information by URL |
| GET | `/v1/company/competitorpremium/id/{companyId}` | Get Competitor information by Id |
| GET | `/v1/company/competitorpremium/url/{website}` | Get Competitor information by Url |
| GET | `/v1/company/fuzzysearch` | Fuzzy Search Company by Name or Address or Phone |
| GET | `/v1/company/id/{companyId}` | Get Company by Id |

## Key resources

- **Main API** — Primary Owler resources and operations

## Why Jentic

- **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 handling:** 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.
- **Discovery method:** 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.

## FAQ

### What authentication does the Owler use?

The Owler uses apiKey authentication.

### How many endpoints does the Owler have?

The Owler has 13 endpoints available.

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

Yes. Because you run Jentic One yourself, your own rules decide which Owler operations and credentials your agent may use. Since Owler carries the company id in the URL path, such as `/v1/company/id/{companyId}`, you can pin the agent to a single company for reads like its detail and competitor lists. You also choose the operations it may call, so broad lookups such as basic search and fuzzy search stay out of reach unless you explicitly add them.