Pikwy Screenshot API
★ Only Publicly Available OpenAPI DocumentMediaScreenshot Captureapi_key1 EndpointsREST
For Agents
Capture full-page or viewport-specific screenshots of any URL in PNG, JPG, PDF, or HTML with customizable dimensions, delays, element hiding, and cloud export options.
Use for: I need to capture a screenshot of a landing page for content review, Take a full-page screenshot of this article and save it to S3, Generate a PDF of a webpage at mobile resolution, Capture a screenshot of a site after it loads for 5 seconds
Not supported: Does not host images, provide CDN delivery, or store screenshots beyond optional direct export to S3/Azure/Dropbox/FTP — use for screenshot capture only, not media asset management or transformation.
Pikwy is a high-speed screenshot capture API that converts any web page into full-resolution images or PDFs without requiring browser automation infrastructure. The API accepts a single endpoint at api.pikwy.com with flexible parameters for viewport dimensions, device simulation, format selection (PNG, JPG, PDF, HTML), custom delays, JavaScript injection, element hiding, geolocation simulation, and cloud export to S3, Azure, Dropbox, or FTP. Authentication uses an API token parameter that developers obtain from the Pikwy dashboard. Through Jentic, developers can programmatically capture landing pages, social media posts, articles, forum threads, and dynamic web content with a single API call, offloading the complexity of headless browser management, rendering consistency, and high-resolution output generation.
Install Jentic One Beta
Connect the Pikwy Screenshot API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Pikwy Screenshot API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with Pikwy Screenshot API.
Capture full-page screenshots of any publicly accessible or authenticated web page in resolutions from 320x240 up to 3840x2160 (4K UHD)
Render screenshots with device-specific dimensions simulating iPhones, iPads, Android devices, Kindle, and custom viewport sizes
Export screenshots in PNG, JPG, PDF, or HTML formats with adjustable zoom, scale, and quality settings
Hide page elements via CSS selectors (useful for removing GDPR banners, cookie notices, or dynamic overlays)
Inject custom JavaScript, set cookies, customize user-agent headers, and simulate geolocation for location-specific rendering
Automatically upload screenshots to FTP/SFTP servers, AWS S3 buckets, Azure Blob Storage, or Dropbox
Authenticate against protected pages using HTTP Basic or form-based login with XPath-targeted field configuration
Use Cases
Patterns agents use Pikwy Screenshot API for, with concrete tasks.
★ Automated Landing Page Archival
Marketing and compliance teams often need timestamped snapshots of landing pages, ads, or promotional content for regulatory audits, A/B test documentation, or historical records. Using Pikwy through Jentic, an agent can capture full-page screenshots at scheduled intervals or on-demand, export them to an S3 bucket with timestamped keys, and maintain an automated archive without managing headless Chrome instances or screenshot infrastructure. The API handles rendering consistency, full-page scrolling, and high-resolution output automatically.
GET https://api.pikwy.com with parameters: token={api_key}, url={target_url}, full_page=1, format=png, and s3_bucket/s3_key for automatic S3 export. Repeat on schedule or trigger.
Social Media Content Capture
Content moderation, brand monitoring, and social listening tools need to capture social media posts, threads, and comments as durable artifacts. Pikwy supports capturing Facebook posts, Instagram pages, Twitter threads, forum discussions, and YouTube videos in full fidelity. Through Jentic, agents can accept a social media URL, pass it to Pikwy with appropriate delays to allow dynamic content to load, hide cookie banners or overlays via CSS selectors, and return a high-resolution screenshot suitable for evidence collection or reporting dashboards.
GET https://api.pikwy.com with parameters: token={api_key}, url={social_url}, delay=3000, format=png, and css_selector to hide overlays. Return the screenshot for moderation review.
Competitor Website Monitoring
SEO and competitive intelligence platforms monitor competitor landing pages, product pages, and pricing tables for changes. By scheduling Pikwy captures through Jentic, agents can take daily screenshots of competitor sites, compare them using image diff libraries, and alert users to layout changes, new messaging, or pricing updates. The API's support for custom user-agents, geolocation simulation, and element hiding ensures captures reflect the intended audience experience without test banners or region-locked content.
GET https://api.pikwy.com with parameters: token={api_key}, url={competitor_url}, full_page=1, format=png, geolocation={target_region}. Store the result and compare with previous captures to detect changes.
Documentation and QA Screenshot Generation
Development teams building documentation, bug reports, or QA test suites need repeatable, high-quality screenshots of application states. Through Jentic, an agent can capture screenshots of staging or production environments with specific viewport sizes (mobile, tablet, desktop), inject JavaScript to set application state or highlight UI elements, and export the results directly to a documentation repository or JIRA attachment. Pikwy eliminates the need for developers to manually take screenshots or maintain Puppeteer scripts.
GET https://api.pikwy.com with parameters: token={api_key}, url={app_url}, width={viewport_width}, height={viewport_height}, js={state_setup_script}, format=png. Attach the result to the documentation or issue tracker.
Key Endpoints
1 endpoints — pikwy is a high-speed screenshot capture api that converts any web page into full-resolution images or pdfs without requiring browser automation infrastructure.
METHOD
PATH
DESCRIPTION
GET
/
Capture a screenshot with query parameters for URL, dimensions, format, delays, authentication, and export options
POST
/
Capture a screenshot with form-encoded or JSON body parameters for URL, dimensions, format, delays, authentication, and export options
GET
/
Capture a screenshot with query parameters for URL, dimensions, format, delays, authentication, and export options
POST
/
Capture a screenshot with form-encoded or JSON body parameters for URL, dimensions, format, delays, authentication, and export options
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
Pikwy API tokens are stored encrypted in the Jentic vault and injected as the token query parameter or body field at execution time. Raw tokens never appear in agent prompts, transcripts, or response payloads. If S3 or FTP export is used, those credentials are also vaulted.
Intent-based discovery
Agents search by intent such as 'capture a screenshot of a webpage' or 'screenshot a landing page to S3' and Jentic returns the Pikwy endpoint with its parameter schema and authentication requirements.
Time to first call
Direct Pikwy integration: 1-2 hours to wire the endpoint, handle authentication, and parse responses. Through Jentic: under 10 minutes — search, load schema, execute with credential injection.
Related APIs
Alternatives and complements available in the Jentic catalogue.
Alternative
Screenshot API
Screenshot API provides a similar screenshot capture service with comparable rendering features and export options.
Choose Pikwy for simpler pricing and straightforward device simulation; choose Screenshot API if the customer already has an integration or prefers their specific feature set.
Complementary
Cloudinary API
Cloudinary handles media asset management, transformation, and delivery that pairs with Pikwy-generated screenshots.
Use Pikwy to capture the screenshot and Cloudinary to store, transform, and deliver it via CDN with responsive breakpoints and optimizations.
FAQs
Specific to using Pikwy Screenshot API through Jentic.
What authentication does the Pikwy Screenshot API use?
The Pikwy API uses API key authentication passed as a query parameter (token or tkn) or in the request body. API keys are obtained from the Pikwy dashboard after account creation. Through Jentic, keys are stored encrypted and injected at execution time so they never appear in agent prompts or transcripts.
Can I capture screenshots of login-protected pages?
Yes. Pikwy supports both HTTP Basic authentication (via auth_user and auth_pass parameters) and form-based login (via form_user, form_pass, and XPath selectors for field targeting). The API handles login workflows and captures the authenticated page content.
What image formats does Pikwy support?
Pikwy generates screenshots in PNG, JPG, PDF, and HTML formats. PNG is best for lossless capture, JPG for smaller file sizes, PDF for multi-page documents, and HTML for preserving the original DOM structure alongside rendered content.
How do I export screenshots directly to S3 through Jentic?
Include the s3_bucket, s3_key, s3_region, s3_access_key, and s3_secret_key parameters in your Pikwy API request. The screenshot will be uploaded directly to the specified S3 location without returning the image to the client. Jentic manages the S3 credentials securely if configured.
Is there a rate limit for the Pikwy API?
Pikwy enforces usage limits based on your pricing tier. The free trial includes 100 screenshots over 7 days with 1 dedicated worker. Paid plans start at $3/month with 10 dedicated workers and per-screenshot overage pricing. Rate limits are not numerically specified in the API documentation but are enforced account-wide.
Can I hide cookie banners or GDPR notices in screenshots?
Yes. Use the css_selector parameter to specify CSS selectors for elements you want hidden before the screenshot is captured. This is useful for removing cookie notices, GDPR banners, chat widgets, or other overlays that obscure content. Multiple selectors can be provided.
GET STARTED