Cursor's AI agent can run terminal commands. Set DENKBOT_API_KEY in your environment and Cursor can curl any URL during a session — fetching live documentation, checking that a deploy looks right, or pulling in page content to reason about. One env var and the dog is on standby.
Checking if an external API endpoint is up while writing integration code, pulling live documentation into context, verifying visual output of a new feature with a screenshot, fetching examples from library docs.
# Set once in your shell profile:
export DENKBOT_API_KEY="dk_live_..."
# Cursor's agent can now run:
curl -s -X POST https://api.denkbot.dog/scrape \
-H "Authorization: Bearer $DENKBOT_API_KEY" \
-H "Content-Type: application/json" \
-d '{"url":"https://docs.stripe.com/api/charges","format":"json"}' \
| jq '.text' | head -100
# Or screenshot a staging URL:
curl -X POST https://api.denkbot.dog/screenshot \
-H "Authorization: Bearer $DENKBOT_API_KEY" \
-H "Content-Type: application/json" \
-d '{"url":"https://staging.myapp.com","fullPage":true}' \
--output /tmp/staging-check.png && open /tmp/staging-check.pngCursor can browse some URLs via its built-in context features, but for programmatic, cacheable, structured access, denkbot.dog gives you full control.
Yes via the .cursorrules file or as a custom tool in Cursor's settings. Define fetch_url as a tool and the agent will use it autonomously.
If you save the PNG to a local path, you can drag it into Cursor's chat for visual analysis by the model.

€19/year. Unlimited requests. API key ready in 30 seconds.