Abstract API · Arazzo Workflow

Abstract API Screenshot, Scrape, and Image Processing

Version 1.0.0

Capture a website screenshot, scrape its HTML, then optimize an image asset.

1 workflow 3 source APIs 1 provider
View Spec View on GitHub AvatarsCompany EnrichmentContactsCurrencyEmail ValidationExchange RatesIBAN ValidationImage ProcessingIP GeolocationIP IntelligencePhone ValidationPublic HolidaysScreenshotsTimezonesVAT ValidationWeb ScrapingArazzoWorkflows

Provider

abstract-api

Workflows

screenshot-scrape-and-process
Screenshot a URL, scrape it, and optimize the resulting screenshot image.
Captures a full-page screenshot of a URL, scrapes the same page's rendered HTML, and feeds the screenshot URL into image processing to produce an optimized asset.
3 steps inputs: apiKey, imageUrl, url outputs: processedUrl, savedBytes
1
captureScreenshot
captureWebsiteScreenshot
Capture a full-page screenshot of the target URL. The response is the screenshot image binary, so there are no JSON body outputs to chain.
2
scrapePage
scrapeWebPage
Scrape the rendered HTML of the same URL with JavaScript rendering enabled.
3
optimizeImage
processImageByURL
Run the supplied image URL through image processing to produce a lossy, compressed WebP asset and report the bytes saved.

Source API Descriptions

Arazzo Workflow Specification

Raw ↑
arazzo: 1.0.1
info:
  title: Abstract API Screenshot, Scrape, and Image Processing
  summary: Capture a website screenshot, scrape its HTML, then optimize an image asset.
  description: >-
    A site-capture flow that takes a full-page screenshot of a URL, scrapes the
    same URL's rendered HTML, and then runs an image through the Image Processing
    API to produce an optimized, compressed asset. Note an adaptation: the
    Website Screenshot operation returns a binary image rather than a JSON URL,
    so its output cannot be chained downstream; the Image Processing step instead
    operates on a separately supplied image URL. Every step inlines the api_key
    query parameter and request so the flow reads and runs without opening the
    underlying OpenAPI descriptions.
  version: 1.0.0
sourceDescriptions:
- name: websiteScreenshotApi
  url: ../openapi/abstract-api-website-screenshot.yaml
  type: openapi
- name: webScrapingApi
  url: ../openapi/abstract-api-web-scraping.yaml
  type: openapi
- name: imageProcessingApi
  url: ../openapi/abstract-api-image-processing.yaml
  type: openapi
workflows:
- workflowId: screenshot-scrape-and-process
  summary: Screenshot a URL, scrape it, and optimize the resulting screenshot image.
  description: >-
    Captures a full-page screenshot of a URL, scrapes the same page's rendered
    HTML, and feeds the screenshot URL into image processing to produce an
    optimized asset.
  inputs:
    type: object
    required:
    - apiKey
    - url
    - imageUrl
    properties:
      apiKey:
        type: string
        description: Abstract API key valid for Website Screenshot, Web Scraping, and Image Processing.
      url:
        type: string
        description: The page URL to screenshot and scrape.
      imageUrl:
        type: string
        description: An image URL to optimize via the Image Processing API (the screenshot returns binary, so it cannot be chained).
  steps:
  - stepId: captureScreenshot
    description: >-
      Capture a full-page screenshot of the target URL. The response is the
      screenshot image binary, so there are no JSON body outputs to chain.
    operationId: captureWebsiteScreenshot
    parameters:
    - name: api_key
      in: query
      value: $inputs.apiKey
    - name: url
      in: query
      value: $inputs.url
    - name: capture_full_page
      in: query
      value: true
    successCriteria:
    - condition: $statusCode == 200
  - stepId: scrapePage
    description: >-
      Scrape the rendered HTML of the same URL with JavaScript rendering enabled.
    operationId: scrapeWebPage
    parameters:
    - name: api_key
      in: query
      value: $inputs.apiKey
    - name: url
      in: query
      value: $inputs.url
    - name: render_js
      in: query
      value: true
    successCriteria:
    - condition: $statusCode == 200
  - stepId: optimizeImage
    description: >-
      Run the supplied image URL through image processing to produce a lossy,
      compressed WebP asset and report the bytes saved.
    operationId: processImageByURL
    parameters:
    - name: api_key
      in: query
      value: $inputs.apiKey
    - name: url
      in: query
      value: $inputs.imageUrl
    - name: lossy
      in: query
      value: true
    - name: output_format
      in: query
      value: webp
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      processedUrl: $response.body#/url
      savedBytes: $response.body#/saved_bytes
      savedPercent: $response.body#/saved_percent
  outputs:
    processedUrl: $steps.optimizeImage.outputs.processedUrl
    savedBytes: $steps.optimizeImage.outputs.savedBytes

Work with this as data

Every workflow here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for arazzo workflows

4 MCP tools reach this
  • find_arazzoBrowse and filter every workflow in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools

Call it yourself

curl for this page
This workflow
curl "https://apis.io/api/v1/arazzo/abstract-api-screenshot-scrape-and-process-workflow"
All arazzo workflows
curl "https://apis.io/api/v1/arazzo?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no email required.

A second provider on the same verified email joins the account you already have.