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

# Piloterr API

Jentic publishes the only available OpenAPI specification for Piloterr API, keeping it validated and agent-ready. Piloterr API provides web scraping and data extraction across 66 endpoints covering search engines (Google, Bing, Brave), social platforms (LinkedIn, Instagram, Pinterest, GitHub), e-commerce sites (Amazon, Walmart, Shopify), business intelligence sources (Crunchbase, Trustpilot, G2), and website analysis tools including screenshot capture, technology detection, and email/phone extraction.

## For AI agents

Extract structured data from search engines, social platforms, e-commerce sites, and business directories. Scrape LinkedIn profiles, Google search results, Amazon products, and company information from multiple sources.

## Scope

Does not handle data storage, CRM management, or outreach automation - use for web data extraction and enrichment only.

## Capabilities

- Scrape Google search results including images, news, videos, and job listings
- Extract LinkedIn profile, company, and job posting data
- Retrieve Amazon and Walmart product details with pricing and availability
- Look up company information from Crunchbase, Trustpilot, and G2
- Capture website screenshots and detect technology stacks
- Find and verify email addresses associated with domains
- Extract contact information including phone numbers from websites

## Use cases

### Lead Research and Enrichment

Build comprehensive company and contact profiles by combining data from LinkedIn, Crunchbase, and business directories. Piloterr extracts company details, employee profiles, funding rounds, and contact information across multiple sources through a single API, replacing manual research with automated data collection.

Example prompt: Extract LinkedIn company info for 'acme-corp', retrieve their Crunchbase funding data, and find email addresses for their domain

### Competitive Intelligence Monitoring

Monitor competitors across search rankings, product reviews, and social presence. The API scrapes Google search positions, Trustpilot and G2 reviews, product listings on Amazon, and Similarweb traffic estimates, enabling automated competitive analysis without manual browsing.

Example prompt: Search Google for 'project management software', extract Trustpilot ratings for the top 3 companies, and get their Similarweb traffic data

### E-Commerce Product Data Extraction

Extract product listings, pricing, offers, and availability from Amazon, Walmart, Best Buy, and Shopify stores. The API returns structured product data including titles, prices, ratings, and seller information for price comparison, catalog enrichment, and market analysis.

Example prompt: Retrieve Amazon product details for ASIN B09V3KXJPB including price, ratings, and available offers

### Website Analysis and Contact Extraction

Analyze websites for technology stacks, capture screenshots, check domain reputation, and extract contact information. The API identifies frameworks, CMS platforms, and analytics tools while also finding email addresses and phone numbers published on site pages.

Example prompt: Detect the technology stack on example.com, capture a screenshot, and extract any email addresses found on the site

### AI Agent Data Collection Pipeline

AI agents use the Piloterr API through Jentic to automate multi-source data extraction without configuring individual scrapers. Agents search for extraction operations by intent, load endpoint schemas, and execute calls with Jentic handling API key authentication and rate limiting across all 66 endpoints.

Example prompt: Search Jentic for 'extract LinkedIn company profile', load the Piloterr LinkedIn endpoint schema, and retrieve company data for a target organization

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/google/search` | Scrape Google search results for a query |
| GET | `/linkedin/profile/info` | Extract a LinkedIn profile |
| GET | `/linkedin/company/info` | Extract LinkedIn company data |
| GET | `/amazon/product` | Retrieve Amazon product details |
| GET | `/email/finder` | Find email addresses for a domain |
| GET | `/email/verify` | Verify email deliverability |
| GET | `/website/technology` | Detect website technology stack |
| GET | `/crunchbase/company/info` | Look up Crunchbase company data |

## Key resources

- **Google Search** — Search, images, news, videos, jobs, and autocomplete results
- **LinkedIn** — Profile, company, job search, job details, and post information
- **Amazon** — Product details, search results, and offer listings
- **Email** — Email finding, verification, and domain analysis
- **Website** — Screenshot capture, technology detection, and contact extraction
- **Crunchbase** — Company profiles, people, funding rounds, and events
- **Domain** — WHOIS lookup, malicious detection, and DNSBL checking

## Why Jentic

- **Setup:** Wiring the Piloterr API by hand means setting up its x-api-key header auth and coding each scrape and enrichment call across search, LinkedIn, Amazon, and email endpoints yourself. Through Jentic you install once, import Piloterr from the API Directory, store the API key once, and your agent calls it.
- **Permission scoping:** Piloterr takes its target in the request query rather than a resource id in the path, so scoping is by operation: you limit the agent to the operations it needs, such as a Google search or LinkedIn profile lookup, and leave the rest out. You choose that set, so an unlisted operation like email finding stays unavailable unless you add it.
- **Credential handling:** Your Piloterr API 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 'scrape LinkedIn company data' or 'verify an email address', and Jentic returns the matching Piloterr operation with its input schema so the agent calls the right endpoint without browsing dozens of endpoints.

## Related APIs

- **ScraperAPI** — ScraperAPI provides general-purpose web scraping with proxy rotation but without Piloterr's pre-built data extractors
- **Apify API** — Apify offers customizable web scraping actors with broader automation capabilities beyond data extraction
- **Bitly API** — Bitly shortens and tracks links to content discovered through Piloterr data extraction

## FAQ

### Why is there no official OpenAPI spec for Piloterr API?

Piloterr does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Piloterr API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

### What authentication does the Piloterr API use?

The Piloterr API uses an API key passed in the request header. Through Jentic, this key is stored encrypted in your Jentic One instance and injected automatically into every request without exposing it to the agent.

### Can I scrape LinkedIn profiles and company data with the Piloterr API?

Yes. The `/linkedin/profile/info` endpoint extracts individual profiles and `/linkedin/company/info` retrieves company pages. Additional endpoints cover job search, job details, and post information from LinkedIn.

### How many data sources does the Piloterr API cover?

The API covers 15+ data sources across 66 endpoints including Google, Bing, Brave, LinkedIn, Amazon, Walmart, Best Buy, Shopify, Crunchbase, Trustpilot, G2, Product Hunt, Instagram, Pinterest, GitHub, Similarweb, and more.

### How do I extract company data through the Piloterr API using Jentic?

Search Jentic for 'extract LinkedIn company profile', load the `/linkedin/company/info` operation schema, and execute with the company LinkedIn slug. Jentic handles API key injection and returns structured company data including employee count, industry, and description.

### Can I verify email addresses with the Piloterr API?

Yes. The `/email/verify` endpoint checks email deliverability, and `/email/finder` discovers email addresses associated with a domain. The `/email/analyzes` endpoint provides detailed analysis of email address patterns.

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

Yes. Because you self-host Jentic One, your own rules decide which Piloterr operations the agent may call and which stored credentials it may use. Piloterr takes its target in the request query rather than a resource id in the path, so you scope by operation: expose only what the agent needs, such as a Google search or a LinkedIn profile lookup, and leave the rest out. An operation you do not list, like email finding, stays unavailable to the agent unless you add it.