Build an event catalog
Extract event names, dates and venues from known event pages. Use the returned fields to populate records for your team to review.
Gomry Cloud / Scrape
Structured data from web pages.
Turn the pages you already have into the fields your application needs. Scrape renders the page, reads its content and returns structured data in the format you define.
What you can build
Bring web content into your product.
Use Scrape to turn published information into records for catalogs, internal tools and AI applications.
Enrich product records
Bring names, descriptions and other published product details into your catalog, using the same field structure across different page layouts.
Prepare content for your own parser
Retrieve rendered HTML and metadata with Fetch when your application already has its own extraction logic.
Choose how much processing you need.
| When you are considering | How Scrape fits |
|---|---|
| Writing page-specific extraction code | Scrape renders JavaScript before extracting your chosen fields. You define the output schema instead of writing CSS selectors for each page layout. |
| Fetching content for your own parser | Use Fetch when you want raw HTML and metadata without model-based extraction. It is billed separately at a lower rate. |
| Discovering pages across the web | Scrape starts with a URL you provide. For a question that requires finding and reading several sources, use Superagent. |
Usage and control
Usage-based pricing.
Scrape is billed per page returned. Fetch has its own lower per-request rate. Failed requests that return no page are not billed.
Enable the service for your project, grant the required API key permissions and set a monthly budget in the Cloud console.
View current pricing ↗Common questions.
Does Scrape search for pages?
No. Supply the page URL you want to read. It does not discover URLs or automatically crawl a website.
Can I use my own extraction logic?
Yes. Choose Fetch for HTML and metadata, or request raw HTML alongside a structured extraction.