ApiFlash MCP integration for AI agents.
Connect AI agents to ApiFlash through 3 structured actions, including get quota information, capture website screenshot, and get screenshot metadata. Review…
- ACTION CONTRACTS
- 3
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the ApiFlash integration exposes
The ApiFlash Agent App exposes 3 provider-backed actions for developer tools and design & media work. Its current contract lets an authorized agent retrieve the current apiflash screenshot quota and reset time, capture a website screenshot with apiflash and return the generated screenshot url, and read http metadata for a screenshot url previously returned by apiflash. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected ApiFlash account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real ApiFlash capabilities.
Showing 3 of 3 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_quota_informationREADRetrieve the current ApiFlash screenshot quota and reset time.
capture_website_screenshotREVIEWCapture a website screenshot with ApiFlash and return the generated screenshot URL.
INPUTS: url / fresh / ttl / full_page / scroll_page
get_screenshot_metadataREADRead HTTP metadata for a screenshot URL previously returned by ApiFlash.
INPUTS: url
INPUT CONTRACTS
Know what the action needs before it runs.
capture_website_screenshot
urlREQUIRED- The complete website URL to capture, including the protocol.
freshOPTIONAL- Whether ApiFlash should bypass the cache and capture a fresh screenshot.
ttlOPTIONAL- The screenshot cache lifetime in seconds, from 0 to 2592000.
full_pageOPTIONAL- Whether to capture the entire scrollable page instead of only the viewport.
scroll_pageOPTIONAL- Whether ApiFlash should scroll the page before capture to trigger lazy-loaded content.
get_screenshot_metadata
urlREQUIRED- The screenshot URL returned by `capture_website_screenshot` for metadata lookup.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Quota Information
Retrieve the current ApiFlash screenshot quota and reset time. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_quota_informationVerify with Get Screenshot Metadata
Read HTTP metadata for a screenshot URL previously returned by ApiFlash. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_screenshot_metadataSAFETY BOUNDARY
Operate ApiFlash with explicit limits
- Authorize ApiFlash with API key and grant only the provider access required by the selected actions.
- The current action names appear read-oriented, but returned ApiFlash data may still be sensitive and should be minimized before it enters model context.
- Do not infer permission from catalog visibility. Workspace policy, connection identity, and upstream authorization still govern execution.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in ApiFlash rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the ApiFlash task completed successfully.
CONNECTION MODEL
API key
ApiFlash access key passed as the access_key query parameter. Create or copy it from your dashboard: https://apiflash.com/dashboard/access_keys
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 2
- WRITE SIGNALS
- 0
- HIGH IMPACT
- 0
- REVIEW SIGNALS
- 1
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by ApiFlash.