Vulpine API
Vulpine API is the hosted surface for teams that want browser-backed extraction, visual workflows, and recurring monitors without operating their own browser fleet.

Extraction
Structured browser-backed extraction with sync, async, and batch execution
Visual flows
Screenshots, annotated image retention, and redacted traces
Operations
Recurring monitors, task history, usage, scoped keys, provider controls, retained artifacts
What Teams Buy
| Workflow | What the hosted surface provides |
|---|---|
| Structured extraction | Browser-backed extraction from schema or natural-language prompts, with sync and async execution |
| Visual extraction | Screenshot-backed extraction plus retained annotated images for later operator review |
| Monitoring | Repeated runs, change detection, webhook delivery, extraction history, retry/failure classification |
| Operations | Usage, scoped API keys, provider listing, retained result and artifact downloads |
What Is Available Now
| Area | Current surface |
|---|---|
| Extraction | POST /v1/extract, POST /v1/batch, task lookup, extraction history, result export |
| Visual workflows | POST /v1/visual, retained screenshot and annotated image downloads |
| Monitors | Create, list, and delete recurring monitors |
| Account and usage | Usage totals, provider listing, scoped key creation and listing |
Example
curl -X POST https://api.vulpineos.com/v1/extract \
-H "Authorization: Bearer $VULPINE_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"url": "https://example.com/products",
"schema": {
"type": "object",
"properties": {
"products": {
"type": "array",
"items": {
"type": "object",
"properties": {
"name": { "type": "string" },
"price": { "type": "number" }
}
}
}
}
}
}'Why the Hosted Surface Exists
VulpineOS itself is public and self-hostable. The hosted API exists for teams that want:
- browser-backed extraction without running the browser fleet
- visual workflows behind a stable service boundary
- retained artifacts and history for operators
Open Runtime, Hosted Surface
The hosted API uses the same public runtime family and public tool contracts. Provider implementations and deployment wiring are not part of the open-source runtime repository.
Product Boundary
The public/open pieces are:
- VulpineOS runtime
- Foxbridge
- Vulpine Mark
- Android MobileBridge
- public docs and API positioning
See Source Availability for the exact boundary and API Reference for the endpoint-level contract.
Read Next
Last updated on