Add Firecrawl to your AI agent

Use when you have a domain or LinkedIn company URL and need the company behind it. For a company you can only name, search first.

Look up a company by its Apollo ID; use companies/enrich when you have a domain instead.

Find current hiring activity at a known company. Each requested page costs 30 Firecrawl credits.

Find news about known Apollo companies, optionally filtered by category and dates. Each requested page costs 30 Firecrawl credits.

Use to build a list from a shape: size, location, industry, technology. It bills per page, so ask for the page size you need rather than paging through the whole market.

Enrich up to ten identified people in one call, billed 30 Firecrawl credits per matched person; unmatched records are free.

Retrieve a known Apollo person by ID. Use people/match to unlock contact information.

Use to resolve one person you have already found. Prefer the id from people/search, then a LinkedIn URL, then email; a bare name needs a domain beside it or it will match the wrong person.

Tool to cancel a running batch scrape job using its unique identifier. Use when you need to terminate an in-progress batch scrape operation.

Tool to retrieve error details from a batch scrape job, including failed URLs and URLs blocked by robots.txt. Use when you need to debug or understand why certain pages failed to scrape in a batch operation.

Use for where analysts stand in aggregate right now on one company. For the individual changes that moved the consensus, use calendar/ratings instead.

Use for who is buying whom, at what price, and whether the deal is pending or closed. For the coverage and commentary around a deal use news/search.

Use for how analysts have moved on a stock: upgrades, downgrades, initiations and target changes. Filter by parameters[analyst_id] or parameters[firm_id] to follow one analyst or firm. It carries the ratings, not the reasoning behind them.

Use to resolve an analyst by name, or to judge how accurate a particular analyst has been, and to get the id you then pass to calendar/ratings as parameters[analyst_id]. For the ratings themselves use calendar/ratings; for the list of firms rather than people use calendar/ratings-firms.

Use to enumerate the covering firms or to turn a firm name into the id that calendar/ratings filters on as parameters[firm_id]. For an individual analyst and their track record use calendar/ratings-analysts; for the ratings themselves use calendar/ratings.

Use when you keep a copy of the ratings or M&A calendar and need to know which previously returned events have since been withdrawn, which Schedule C.10 requires you to act on. It answers only what disappeared; for the events themselves use calendar/ratings or calendar/mergers-acquisitions.

Use this for company-issued announcements as distributed over the wires (PRNewswire, Globe Newswire, Business Wire, ACCESS Newswire, Newsfile), the primary-source wording behind a story. For Benzinga editorial coverage and the wider newswire use news/search, and for the one-line explanation of a price move use news/wiims.

Use this when you keep a copy of Benzinga news and need to know which stories have been withdrawn so you can delete them, which Schedule C.10 requires. It never returns story content; for the stories themselves use news/search.

Use for what was reported about a company or subject, and when. Scope it to tickers or a date range: unscoped it returns the whole newswire. For the analyst reaction to a story use calendar/ratings.

Use this to answer why a stock moved: WIIMs are the short attributed explanations Benzinga files against a ticker's price action. For the underlying coverage use news/search, and for the company's own announcement use news/press-releases.

Use for positioning: large directional bets before a catalyst. It reports orders, not outcomes, and a sweep filled at or above the ask (execution_estimate) is a stronger signal than one at the midpoint.

Initiates a Firecrawl web crawl from a given URL, applying various filtering and content extraction rules, and polls until the job is complete; ensure the URL is accessible and any regex patterns for paths are valid.

Tool to cancel a running crawl job by its ID. Use when you need to stop an active crawl operation. The API returns a status of 'cancelled' upon successful cancellation.

Tool to retrieve errors from a Firecrawl crawl job. Use when you need to understand why certain pages failed to scrape or which URLs were blocked by robots.txt during a crawl operation.

Tool to retrieve all active crawl jobs for the authenticated team. Use when you need to see which crawl operations are currently running.

Preview crawl parameters before starting a crawl by generating optimal configuration from natural language instructions. Use this tool to understand what crawl settings will be applied based on your requirements before executing a full crawl operation. The endpoint intelligently interprets natural language prompts to configure crawl parameters like include/exclude paths, depth limits, and domain scope.

[NEW v2 API] Initiates a Firecrawl v2 web crawl with enhanced features over v1: natural language prompts for automatic crawler configuration, crawlEntireDomain for sibling/parent page discovery, better depth control with maxDiscoveryDepth, subdomain support, and full webhook configuration. Polls until crawl is complete.

Tool to retrieve historical team credit usage on a monthly basis. Use when you need to analyze credit consumption patterns over time, optionally segmented by API key.

Use the base Data Legion product by default for company enrichment. Choose the premium action only when the caller explicitly requests premium enrichment. Name matching is global, so include a domain or social URL for ambiguous names.

Use only when the caller explicitly requests Data Legion premium company enrichment; otherwise use the base action. Name matching is global, so include a domain or social URL for ambiguous names.

Use the base Data Legion product by default for person enrichment when personal contact data is not wanted. Choose a with-contact action only when the caller explicitly requests contact data.

Use the base Data Legion product when the caller explicitly requests personal contact data. Contact entitlement comes from the dedicated credential, never from field projection.

Use only when the caller explicitly requests premium Data Legion person enrichment without personal contact data. Otherwise use the base no-contact action.

Use only when the caller explicitly requests both premium Data Legion person enrichment and personal contact data. Otherwise use a lower-tier or no-contact action.

Extracts structured data from web pages by initiating an extraction job and polling for completion; requires a natural language `prompt` or a JSON `schema` (one must be provided).

Call to discover what is covered, or to resolve names to identifiers when you do not already have a ticker. Check the per-company dataset list before assuming a costlier capability will answer for it.

Call first when starting from a ticker or stable company or security identifier. It returns every other identifier, peers, and secondary listings. Use company/list when starting from only a company name.

Call for the numbers a business is actually run on - segment revenue, units, subscribers - which never reach the three statements. Coverage is narrower than for financials, and varies by company.

Call when a per-share figure has to be computed, or when a dual-class structure means the headline share count is misleading. Point-in-time, not a series.

Call to answer who reports when. Omit every company identifier for the whole calendar, which is what makes this the one capability here that answers a question not about a specific company. Read `eventStatus` before relying on a date - an estimated one moves.

Call to find what exists for a quarter before asking for any of it - the deck, the release, the report, the transcript. Rows sharing a fiscal year and quarter are one event, so group on that pair rather than on the date.

Call for what was said on the call, attributed and timed. The speaker mapping is what makes it worth more than the raw text: management's prepared remarks and an analyst's question can be told apart, and the Q&A boundary is given rather than guessed.

Call to find out what exists and when it was filed, and to get the document links. The filing bytes themselves are not retrievable through this provider - see its page for why - so treat `pdfUrl` as a handoff.

Call when comparing against analyst estimates or consensus, which are quoted on an adjusted basis rather than a GAAP one. Not a substitute for the statements: these are management's adjustments, and the exclusions are theirs.

Call when comparing companies, screening, or computing anything that has to mean the same thing across two filers. The mapping is visible: each standardized metric names the as-reported lines behind it, so a surprising figure can be traced rather than trusted.

Call when fidelity to the filing matters more than comparability: the labels and groupings are the company's own, so two companies cannot be lined up against each other. Use the standardized view for that. Each value carries a link back to the filing page it came from.

Call when comparing companies, screening, or computing anything that has to mean the same thing across two filers. The mapping is visible: each standardized metric names the as-reported lines behind it, so a surprising figure can be traced rather than trusted.

Call when fidelity to the filing matters more than comparability: the labels and groupings are the company's own, so two companies cannot be lined up against each other. Use the standardized view for that. Each value carries a link back to the filing page it came from.

Call when comparing companies, screening, or computing anything that has to mean the same thing across two filers. The mapping is visible: each standardized metric names the as-reported lines behind it, so a surprising figure can be traced rather than trusted.

Call when fidelity to the filing matters more than comparability: the labels and groupings are the company's own, so two companies cannot be lined up against each other. Use the standardized view for that. Each value carries a link back to the filing page it came from.

Call to find which companies professional investors are actually writing about, and how heavily, before asking what they said.

Call for the qualitative case on a company as professional investors put it, with the stance and conviction attached. The one capability here that answers what people think rather than what was reported.

Call for what one letter actually argued. The narrative sections are the investor's own words; the theses are the extraction, and each names what it was based on so a thin mention is not mistaken for a conviction.

Call to understand how a firm invests before weighting what it says about a company. The profile is derived from its own letters rather than from marketing material.

Call to find the investorId for a firm, or to pick firms by style or sector focus before reading any letters. Sorted by coverage, so the most-covered firms come first.

Call to see what was published in a quarter. Returns the letter index rather than the letters - take a letterId to fund-letters/detail for the content.

Call to find a ratio id before requesting a series, and to check `hasDailyData` before asking for a daily one - not every ratio has it.

Call to find the standardized metric id for a concept before requesting statements, rather than guessing at a name. Free, and takes no company.

Call rather than the full list when the template is already known - it is the only place the prose definition and the sub-component breakdown of each metric are published, which is what settles what a line actually includes.

Call to read ownership from the investor's end rather than the company's - what a fund holds and how it is weighted. The counterpart to institutional-holders, over the same 13F data.

Call to resolve an institution's name to the holder id that ownership/holder-holdings needs. Free, and takes no company.

Call for the current standing position of officers and directors, including holdings held through trusts and other vehicles. Use insider-transactions for what they have been doing rather than what they hold.

Call to see insider activity over time. Read `transactionType` before drawing conclusions: an option exercise or a tax withholding is not a market sale, and they sit in the same series.

Call to see who institutionally owns a company and who moved last quarter. 13F data lags: the report date is the quarter end, the filing date is up to 45 days later, and both are returned so the lag is visible.

Call for a daily close series. Prices are split-adjusted already, so no correction against prices/splits is needed; the series is per listing, so a cross-listed company answers in whichever listing the identifier denoted.

Call when the question is about movement within a session - a reaction to an announcement, say. Rounded to two decimals, so it is not a tick feed for execution purposes.

Call to explain a discontinuity, or to reconcile against a price series from elsewhere that is not split-adjusted. The series returned by prices/daily already is, so this is not needed to correct it.

Call when the question is how a ratio moved between reporting dates rather than what it was at them. Each day is recomputed against that day's close and the then-current fundamentals, so it is a real series, not a step function.

Call for valuation, margin and leverage ratios already computed against the reported statements, rather than recomputing them from financials and risking a different denominator.

Resolve one company from its domain, LinkedIn company URL, or LinkedIn company ID. Returns firmographics, technologies, social profiles, and locations.

Use only for strict exact-match semantics with a LinkedIn company URL. For broader resolution from a domain, LinkedIn URL, or LinkedIn ID, prefer companies/lookup.

Find companies by industry, size, location, technologies, or founding year. Combine filters and page through the results. Use companies/lookup when you already have a domain or LinkedIn identifier.

Find a person's mobile phone number from a LinkedIn URL, or from their name and employer. The most expensive line by far: ask for it only when a phone is what the task needs. To enrich multiple contacts, send up to 10 separate calls in the Firecrawl /v2/scrape alexandria array, each with its own provider, capability and options. Each call accepts one contact, runs as a separate upstream job and is billed only for a result found. Inspect each call for errors; this is not a single bulk job. Concurrent enrichments share poll capacity and can hit rate limits; spread large batches out. Do not pass a contacts array in options.

Find a person's personal email from a LinkedIn URL, or from their name and employer. Schedule A bars marketing to personal addresses; use contacts/work-email for outreach. To enrich multiple contacts, send up to 10 separate calls in the Firecrawl /v2/scrape alexandria array, each with its own provider, capability and options. Each call accepts one contact, runs as a separate upstream job and is billed only for a result found. Inspect each call for errors; this is not a single bulk job. Concurrent enrichments share poll capacity and can hit rate limits; spread large batches out. Do not pass a contacts array in options.

Identify the person and company behind a work or personal email address. Returns a professional profile; use people/lookup when a name or LinkedIn URL is already known. To enrich multiple contacts, send up to 10 separate calls in the Firecrawl /v2/scrape alexandria array, each with its own provider, capability and options. Each call accepts one contact, runs as a separate upstream job and is billed only for a result found. Inspect each call for errors; this is not a single bulk job. Concurrent enrichments share poll capacity and can hit rate limits; spread large batches out. Do not pass a contacts array in options.

Find a person's verified work email from a LinkedIn URL, or from their name and employer. Use contacts/mobile for a phone number and people/lookup when only the profile is needed. To enrich multiple contacts, send up to 10 separate calls in the Firecrawl /v2/scrape alexandria array, each with its own provider, capability and options. Each call accepts one contact, runs as a separate upstream job and is billed only for a result found. Inspect each call for errors; this is not a single bulk job. Concurrent enrichments share poll capacity and can hit rate limits; spread large batches out. Do not pass a contacts array in options.

Resolve a person from a LinkedIn URL or ID, or a full name combined with a company domain, LinkedIn URL, or ID. Returns a profile, not verified email addresses or phone numbers.

Use only for strict exact-match semantics with a LinkedIn profile URL. For broader resolution from a LinkedIn URL or ID, or from a name plus company identifiers, prefer people/lookup.

Tool to get the status and results of an agent job. Use when you need to check if an agent job has completed and retrieve the collected data. Agent jobs autonomously search, navigate, and extract data from the web.

Retrieves the status and results of a deep research job by its ID. Use when you need to check the progress or retrieve the final analysis of a deep research operation.

List standalone Firecrawl Interact browser sessions, optionally by status.

List recent check runs for a Firecrawl monitor.

Initiates an async job to generate an LLMs.txt file for a website, converting web content into LLM-friendly format. Returns a job ID to check status and retrieve results. Use when you need to create a standardized, machine-readable representation of website content for language models.

Tool to get the status and results of an LLMs.txt generation job. Use when you need to check if a job has completed and retrieve the generated content.

Resolve a canonical Instagram post/video URL against Oriane's index. Instagram uses the post shortcode; TikTok uses the numeric video ID. Empty results do not trigger ingestion. Choose projection: basic 20 credits, default 30 credits, full 40 credits per nonempty call. Search limit is at most 100; URL lookup targets one record. Empty results cost zero.

Search Oriane's indexed Instagram posts, captions and engagement. Platform is fixed to Instagram. Coverage and freshness depend on the existing index; this is not a complete live feed. Results include profileUrl; an empty result does not trigger ingestion. Choose projection: basic 20 credits, default 30 credits, full 40 credits per nonempty call. Search limit is at most 100; URL lookup targets one record. Empty results cost zero.

Pass a canonical Instagram profile URL to look up account details in Oriane's index. Returns profileUrl with each match. Short links and post URLs are unsupported; empty results do not trigger ingestion. Choose projection: basic 20 credits, default 30 credits, full 40 credits per nonempty call. Search limit is at most 100; URL lookup targets one record. Empty results cost zero.

Search Oriane's indexed Instagram profiles, bios and follower counts. Platform is fixed to Instagram. Coverage and freshness depend on the existing index; this is not a complete live feed. Results include profileUrl; an empty result does not trigger ingestion. Choose projection: basic 20 credits, default 30 credits, full 40 credits per nonempty call. Search limit is at most 100; URL lookup targets one record. Empty results cost zero.

Search Oriane's indexed TikTok posts, captions and engagement. Platform is fixed to TikTok. Coverage and freshness depend on the existing index; this is not a complete live feed. Results include profileUrl; an empty result does not trigger ingestion. Choose projection: basic 20 credits, default 30 credits, full 40 credits per nonempty call. Search limit is at most 100; URL lookup targets one record. Empty results cost zero.

Pass a canonical TikTok profile URL to look up account details in Oriane's index. Returns profileUrl with each match. Short links and post URLs are unsupported; empty results do not trigger ingestion. Choose projection: basic 20 credits, default 30 credits, full 40 credits per nonempty call. Search limit is at most 100; URL lookup targets one record. Empty results cost zero.

Search Oriane's indexed TikTok profiles, bios and follower counts. Platform is fixed to TikTok. Coverage and freshness depend on the existing index; this is not a complete live feed. Results include profileUrl; an empty result does not trigger ingestion. Choose projection: basic 20 credits, default 30 credits, full 40 credits per nonempty call. Search limit is at most 100; URL lookup targets one record. Empty results cost zero.

Resolve a canonical TikTok post/video URL against Oriane's index. Instagram uses the post shortcode; TikTok uses the numeric video ID. Empty results do not trigger ingestion. Choose projection: basic 20 credits, default 30 credits, full 40 credits per nonempty call. Search limit is at most 100; URL lookup targets one record. Empty results cost zero.

Use for who a sponsor shares ad breaks with: the advertisers that buy the same inventory.

Use for the company record behind a sponsor, an entity or a companies/search hit. For its podcast advertising footprint use advertising/company/overview; for firmographics or funding, a company data provider is the better source.

Use for a company's podcast advertising footprint in one call, across all its brands. For the show list use advertising/company/shows.

Use for the feed of a company's actual ad reads, episode by episode, to read or audit them.

Use as a buy-side prospect list: where an advertiser could go next, with the shows it already buys as the reason.

Use for where a company advertises, ranked by volume, with the reads to sample. Pages are at most 24 rows.

Use for exactly who advertised in one episode, with the offer and where in the episode the read sits.

Use for the biggest podcast advertisers overall, in a period, or on one network. For the top-ten snapshot use advertising/leaderboard/preview.

Use for a quick read of who is spending most on podcasts this week and who is climbing. For deeper pages, other windows or filters use advertising/leaderboard.

Use for how a network is monetised and who buys across it. For its shows ranked by ad volume use advertising/publisher/shows.

Use for which of a network's shows carry the advertising. For the same catalogue by popularity use podcasts/publisher/shows.

Use for who buys a network, and which of them buy it as a bundle: sort by podcast_coverage with a minimum.

Use for which networks carry the most advertising, or monetise their catalogue most densely.

Use for who sponsors a show and how heavily it is monetised. For the full per-sponsor list use advertising/show/sponsors.

Use as a prospecting list for a show selling its own inventory: who buys shows like mine and has not bought me.

Use for every advertiser on one show with counts and recency, or one company's brands on it. Set since and until on shows with extensive ad history to keep the query bounded.

Use to find who is buying advertising, or to go from a sponsor back to the company paying for it. For where it runs use advertising/sponsor/shows.

Use to tell network buys from per-show buys: a sponsor at 60 to 100 percent coverage of several publishers is buying bundles.

Use to read the actual ad reads for a sponsor, then podcasts/segment/transcript for the words of one.

Use for where an advertiser buys: the canonical footprint of one sponsor, or of a whole company across its brands.

Use to find a sponsor by name or by company and pick up its id. For the biggest spenders use advertising/leaderboard.

Use for which advertisers are ramping podcast spend right now, by airdate.

Use for how an advertiser's podcast spend trends by week or month, optionally on one show or network, and its host-read mix.

Use for a network's political profile as a whole: how political its catalogue is and which way it leans.

Use to list a network's shows by political lean, or only the ones in a bucket.

Use for which publishers carry the most shows of one lean: the flip of a publisher's own bias profile.

Use for which networks lean furthest left or right, are most political, or most ideologically diverse.

Use for where a show sits politically and why, with the evidence to quote. The bucket alone rides on every show record as bias.

Use for what podcasts are talking about most this week in one domain: the most-mentioned shows, films, games, teams or players, or the most-booked guests, with movement since last edition.

Use to see which charts exist (all, tv-series, movies, video-games, nfl, nba, guests and so on) and who leads each, before fetching one with charts/chart.

Use for a company's competitive set with the reason each one is on it, before comparing their podcast presence or advertising.

Use to get a company's handles, domain, CIK or ticker. The reverse, identifier to company, is entities/lookup.

Use to find executives and role holders at a company, or the marketing, brand and partnerships contacts a sponsorship conversation would go to.

Use to see what a company sells, structured by segment and product line, for example to match an ad read's offer to a product.

Use to resolve a company by name, ticker, domain, CIK or Wikidata QID to the slug every company capability takes. The record itself is advertising/company.

Resolve one entity slug or ID to its knowledge-graph record and linked company or person. For where the entity was mentioned, use podcasts/mentions or podcasts/episodes/list with entity_id.

Use for the most-discussed entities overall, in one show, or of one kind, or to fetch several entities by slug at once. Takes no free text; for a name use entities/search.

Use when you hold a LinkedIn slug, a handle, a domain, a ticker or a CIK and need the Particle person or company: the reverse of the external-links capabilities.

Use to turn what someone typed into a specific person, company or entity and its slug, before asking what was said about it with podcasts/mentions or filtering episodes by it. Searching episodes directly is better when the topic, not a name, is the question.

Use to place a topic in the taxonomy and see its neighbours. For the shows in it use podcasts/list with topic_id; for episodes, podcasts/episodes/list. This returns classification, not passages.

Use to find the topic_id that podcasts/search, podcasts/list and the guest capabilities filter on. Walk down from the roots by passing parent_id.

Use to see what the type filter on entities/list can take. Skip it when listing without a filter.

Use to get a person's LinkedIn or social handles. The reverse, handle to person, is entities/lookup.

Use when the question is about someone as a podcast guest: how often they appear, where, and since when. For the episode list use people/guest/appearances.

Use for where someone has appeared, episode by episode, to read what they said: take episode.id to podcasts/transcript with speaker set to their name.

Use to build a pitch list for a guest: the shows most like the ones that already booked them, with the venues to cite.

Use for the set of shows behind a guest rather than the episodes: which shows book them and how often.

Use to find guests by name, by show, by topic or by how often they appear, and pick up the person slug. For who is currently making the rounds use people/guests/trending.

Use for who is doing the podcast circuit right now: a book launch, a product unveil, a news moment, or someone new. For a steady-state directory use people/guests.

Use to go from a name on an episode to the person: who they are, where they work and worked, and their profile links. For their podcast appearances use people/guest.

Use for who has been on a show and how often. For who it could book next use people/show-recommended-guests.

Use as a booking pipeline for a show: guests its peers chose that it has not had yet.

Use when a segment needs to be cited as a playable range rather than as text. For its words call podcasts/clip/transcript.

Use to quote a clip verbatim with speaker labels, or export it as subtitles with format srt.

Use to browse quotable moments by show, speaker or kind. For clips about a subject, search episodes: matching clips ride inside each search result.

Use episode.id from a search match to get the full record and, when available, its web URL or direct audio stream. Neither link is guaranteed. For what was said, fetch podcasts/transcript.

Use for the quotable moments of an episode as bounded, playable ranges with a kind and a speaker.

Use for what an episode was about in named things: the companies, people and products it discussed, ranked by salience. For where each one came up in the dialogue use podcasts/transcript/mentions.

Use for who else covered this: the same story or subject on other shows, optionally within a week of the episode.

Use to see the structure of an episode and pick the section to read: which time ranges are ads to skip, where the interview starts, what each discussion covers. Then podcasts/segment/transcript for the words.

Use to find who was on an episode and in what role, with the person slug to follow into people/profile or people/guest. Ask for the advertiser role to see who voiced the sponsor reads.

Use to classify an episode by subject area, or to pick up a topic_id for filtering shows and episodes.

Use to poll for new episodes of a set of shows or topics as they are transcribed: a resumable, strictly ordered pull. A filter is required. For a one-off list by date use podcasts/episodes/list.

Use for episode-level filtering without dialogue: every episode a person spoke on, every episode featuring a company, a show's episodes in a date range, episodes in a language. When the question is about what was said, search episodes instead.

Use when you hold a Spotify, Apple Podcasts or YouTube episode link, a platform episode id, or an RSS guid and need the Particle episode id to read its transcript. A transcript_status of transcribed means the transcript can be read now; requestable means it has not been transcribed yet. Guids match exactly as supplied.

Use to find episodes that discussed something. This is the entry point: it returns ids the other podcast capabilities take. For every line about one person or company use podcasts/mentions instead.

Use for a trend rather than a list: how often a person appeared by month, how a show's output changed, how many episodes discussed a term each week. One call replaces paging the episode list per period.

Use to browse shows by attribute rather than by name: a topic, a language, a brand-suitability tier, a length band, a cadence, an ad-free or interview format. For a name, podcasts/search is the canonical search.

Use when you already hold an Apple collection id, Spotify show id, YouTube channel id or RSS feed URL and need the Particle podcast deterministically. For a name, use podcasts/search.

Use for every line of dialogue about one person or company across podcasts: the read-everything-about-X call. Resolve the subject with entities/search first. For dialogue by topic or exact phrase use podcasts/episodes/search.

Use for how mentions of a person or company trend by day, week or month, optionally within one show or network. One call instead of paging podcasts/mentions per period.

Use to go from a show's publisher reference to the network record. For the network's shows call podcasts/publisher/shows; for its advertising, bias or suitability roll-ups use the capabilities under those concepts.

Use to walk a network's catalogue by audience. For the same catalogue ranked by ad volume use advertising/publisher/shows.

Use to find a network's slug by name before asking about its shows, advertising, bias or suitability.

Use to turn a show name into its slug and record. To find what was said inside one, search episodes instead: this matches show metadata, not transcripts. For an Apple, Spotify or YouTube id use podcasts/lookup.

Use to see what a matched segment is (an interview, a topic discussion, an ad) and its time range. For its text call podcasts/segment/transcript.

Use to read the words of one segment in full and in order, at the price of a segment rather than an episode.

Use to pull one kind of section across a show: every interview, every ad read, every topic discussion in a date range. For one episode's structure use podcasts/episode/segments.

Use when a search or an episode record gave you a podcast id and the full show record is needed, including the publisher to go up to and the slug every other show capability takes.

Use to get from a show to its episodes and their ids: the latest episode, an episode by title, or the run of episodes in a date range. A podcast slug is never an episode id; this is how you get one.

Use to get a show's Apple, Spotify or YouTube ids and links, its social handles, or its website. The reverse direction, platform id to show, is podcasts/lookup.

Use for the exact rates and distributions behind a show's format: how often it has guests, how long episodes run, how often it publishes and on which days. The compact form rides on every show record as format.

Use for how much one show talks about a person or company: an episode-level roll-up inside one podcast. For the dialogue lines themselves, across shows, use podcasts/mentions.

Use to read what listeners wrote about a show. For the averages and histogram use podcasts/show/ratings-summary.

Use for a show's average rating and count per storefront, plus the combined figure and what recent reviews say in aggregate.

Use for shows like this one: competitive sets, a listener's next show, or the peer set a sponsor or guest pitch cites. Branch on band rather than on the raw score.

Use to see which subject areas have the most shows. For the full taxonomy tree use entities/topics; for the shows in one topic use podcasts/list with topic_id.

Use to read a whole episode rather than the excerpt a search returned. For one passage, podcasts/segment/transcript is smaller and cheaper; for a moment, podcasts/transcript/preview.

Use to see exactly where and how a company, person or product was discussed within one episode, with the dialogue around each mention. Across episodes, use podcasts/mentions.

Use to read what was being said at a timestamp, or the opening of an episode, at a fifth of the full transcript's price. For a whole episode use podcasts/transcript.

Use to find the category_slug the chart capabilities take.

Use for today's chart: the US Apple overall top podcasts with no arguments, or a country and category. Use rankings/categories and rankings/countries for the valid slugs.

Use to find the country codes the chart capabilities take.

Use for how a chart looked on past days, or how one show moved within it. For one show across every chart use rankings/show/history.

Use for what debuted, climbed, fell or dropped off a chart since yesterday or over a window.

Use for where a show charts today, everywhere it charts. For a one-number summary use rankings/show/summary.

Use for a show's chart trajectory over time.

Use for how big a show is on the charts in one call: its best rank and how widely it charts.

Use to check which chart sources exist and how fresh the snapshot is.

Use to pivot on one category for a regulated or family brand: which networks carry the most, or least, alcohol, weapons, adult or hate-speech exposure.

Use for what kind of shows a guest tends to appear on, in brand-safety terms.

Use for how brand-safe a network's catalogue is as a whole and where its exposure sits.

Use to build an inclusion or exclusion list inside one network: its shows by tier, or the ones exposed in a category.

Use for the safest or riskiest networks to buy, or the most broadly placeable.

Use for whether a show is safe to advertise on and in which categories it is exposed, with the evidence. The tier alone rides on every show record as suitability_tier.

Use when you have one company and want its firmographics, funding and headcount. Give it a domain, ticker or social profile if you possibly can - a bare name is the identifier most likely to miss.

Use to find companies by attribute - industry, headcount, funding stage, location - rather than to look one up you can already name. Each returned company costs 50 credits. Smaller pages reduce payload size.

Tool to retrieve metrics about the team's scrape queue. Use when you need to check queue status, job counts, or concurrency limits.

Scrapes a publicly accessible URL, optionally performing pre-scrape browser actions or extracting structured JSON using an LLM, to retrieve content in specified formats.

Performs a web search for a query, scrapes content from the top search results using Firecrawl, and returns details in specified formats.

Search professional profile previews by role, company, keywords and location through Firecrawl Alexandria Apollo. Returns first names, masked surnames, titles, organizations and contact-availability flags, not revealed email addresses. Request one page at a time with page and per_page (maximum 100).

Search professional profiles by current or past roles, employers, skills, education and location through Firecrawl Alexandria FullEnrich. Returns one page with provider pagination metadata. Use offset up to 10,000, then metadata.search_after with unchanged filters. Up to 6 records per page; default 2. Contact email and phone enrichment is separate. A team administrator must accept FullEnrich terms in Firecrawl before use.

Use for marketing channel shares for one complete month. Subscription availability applies. The Similarweb-only monthly credit allowance applies.

Use for marketing channel traffic for one complete month. Subscription availability applies. The Similarweb-only monthly credit allowance applies.

Use for traffic geography for one complete month. Subscription availability applies. The Similarweb-only monthly credit allowance applies.

List domains sending referral traffic to the supplied domain for one complete month, using record-offset pagination. Use web/referrals when page-number pagination is preferable.

Use for paid search spend for one complete month. Subscription availability applies. The Similarweb-only monthly credit allowance applies.

List domains sending referral traffic to the supplied domain for one complete month, using page-number pagination. Use web/incoming-referrals when record-offset pagination is preferable.

Use for traffic and engagement for one complete month. Subscription availability applies. The Similarweb-only monthly credit allowance applies.

List domains that receive referral traffic from the supplied domain, optionally filtered by date, country, device, and granularity. Use incoming-referrals to find domains sending traffic to the supplied domain.

Stop a scrape job's interactive browser session, releasing browser resources and finalizing duration-based billing.

Tool to retrieve historical team token usage on a monthly basis. Use when you need to analyze token consumption patterns over time, optionally segmented by API key.

Use for how a market advertises: the share of hooks, personas, offers or formats across a vertical, brand or filter. Run it twice, once with min_impressions=4, to see what the winning ads over-index on.

Use to list a brand's or a vertical's ads by filter: what an advertiser is running now (advertiser_id + is_active=true), or the winners in a category (order_by=best, min_impressions=4).

Use for everything about one ad: the hook, offer, landing page and whether the page delivers what the ad promises. Add include=full for scenes, transcript, overlays and narrative.

Use to find Meta ads matching a free-text idea, relevance-ranked across Upspring's competitor ad corpus. Re-rank the page by strength.impressions, then open the finalists with ads/detail. For the newest or best-performing ads without a query use ads/browse.

Use to find ads creatively like one ad, from the same brand and from its competitors.

Use for a brand's ad strategy at a glance: size grades, Facebook and Instagram followers, Reddit sentiment, its creative fingerprint (personas, mechanisms, hooks, media mix, funnel), hook themes and its top ads.

Use when all you have is a company's website: resolves it to one advertiser and returns the same brief as advertisers/brief. Never 404s; a domain Upspring cannot source answers status unavailable and is not charged.

Use to put two brands' ad strategies side by side: where they overlap, where they differ, and what each leaves open.

Use for brands like this one: same category, vertical, geography or size band. For creative similarity instead use advertisers/similar.

Use when advertisers/brief answers not found or status unavailable for an advertiser id you know exists: asks Upspring to source it, then poll advertisers/brief. Idempotent; each new advertiser counts against a daily limit.

Use to find a brand's advertiser id by name, website or Facebook page, or to list the advertisers in a vertical, category or size tier. For one brand from its domain with the full brief in one call use advertisers/by-domain.

Use for a brand's closest competitors: advertisers going after the same audience with comparable creative strategies.

Use, free, before filtering ads by persona, hook or another dimension: lists the valid ids in one vertical.

Use first, free, to learn the vertical and category ids the ads and advertiser filters accept.