Apiflash for AI agents
ApiFlash is a website screenshot API that captures high-quality images of web pages programmatically, used by developers to generate previews, thumbnails, and visual reports. Connect it once through Arc0, and your agent, or Claude, ChatGPT and Cursor, can use it through one MCP endpoint, limited to what each user approved.
What agents do in Apiflash.
Capture a screenshot of a webpage
Take a screenshot of a given URL to use in a report or preview.
Batch capture screenshots across pages
Capture screenshots for a list of URLs in a single batch request.
Check remaining screenshot quota
Look up the account's quota before running a large screenshot capture job.
5 Apiflash actions, graded by risk.
Every Apiflash action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.
read
2Look things up. Allowed by default.
- apiflash.get_quota_informationGet Quota Information
- apiflash.get_screenshot_metadataGet Screenshot Metadata
write
3Create and change things. Allow, or ask the user first.
- apiflash.capture_screenshotCapture Screenshot
- apiflash.batch_capture_screenshotsBatch Capture Screenshots
- apiflash.capture_website_screenshot_postCapture Website Screenshot (POST)
destructive
0Delete, cancel or archive. Ask first, or deny outright.
- No destructive actions.
Apiflash in three steps.
- 01Your users connect ApiflashThey add their Apiflash api key on Arc0 Connect, under your brand. It goes straight into the vault.
- 02You set the rulesReads run, and writes like “capture Screenshot” can wait for the user to approve.
- 03Any agent can actYour agent calls Apiflash through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('apiflash', { read: 'allow', write: 'ask', // capture_screenshot destructive: 'deny', }) # Claude Code: the same connection, one URL $ claude mcp add --transport http arc0 \ https://mcp.arc0.ai/u/u_8f2
How Apiflash connects.
Users add their Apiflash api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.
The same Apiflash connection serves your agent over MCP and your own backend over REST and the proxy, so a user connects once. How Arc0 handles credentials →
- AUTH
- API key
- CREDENTIALS
- Per-tenant encrypted vault
- MODEL SEES
- Results only, never credentials
- AUDIT LOG
- Every call, on every plan
Use Apiflash from any agent.
Apiflash and Arc0, answered.
Can I use Apiflash with Claude, ChatGPT or Cursor?
Yes. Connect Apiflash to Arc0 once, then add your Arc0 MCP URL to Claude, ChatGPT, Cursor, Claude Code or any other remote-MCP client. Each assistant only gets the Apiflash actions you allow.
How do users connect Apiflash?
Users add their Apiflash api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.
Which Apiflash actions can my agent take?
5 in total: 2 read, 3 write and 0 destructive, such as “capture Screenshot”. Your policies decide which of them each agent may call.
Can I make my agent read-only in Apiflash?
Yes. Allow read actions and deny writes in the Apiflash policy. Your agent can still look things up, and any write it attempts is blocked and logged.
Can my own backend call Apiflash too?
Yes. The same Apiflash connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug Apiflash into your agent.
Your users connect Apiflash once, under your brand. Your agent gets 5 actions behind your policies, with every call on the record.
Free to build · MCP + REST · Audit log on every plan