Vulpine API

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

Extraction

Structured browser-backed extraction with sync, async, and batch execution

Authenticated and visual flows

Stored credential workflows, redacted traces, screenshots, annotated image retention

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
Authenticated extraction	Stored credential references, expiring saved sessions, and redacted auth traces for diagnosis
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
Authenticated workflows	`POST /v1/extract/authenticated`, session listing/removal, redacted auth traces
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
Mobile and audio surfaces	Available when the corresponding commercial bridge/capture wiring is attached

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
authenticated and visual workflows behind a stable service boundary
retained artifacts and history for operators
commercial extensions such as Vault, AudioBridge, and iOS MobileBridge behind the same product line

Open Runtime, Commercial Surface

Open source foundation	Hosted / source-closed surface
VulpineOS runtime	Vulpine API
Foxbridge	Vulpine Vault
Vulpine Mark	AudioBridge
Android MobileBridge	iOS MobileBridge

The hosted API uses the same runtime family, but some higher-level product surfaces stay source-closed. Public docs name them and describe their capability boundaries, while implementation details stay out of the public repos.

Commercial Product Line

Product	Status	Public description
Vulpine API	Current	Hosted extraction, authenticated and visual workflows, monitors, usage, keys, and operations
Vulpine Vault	Current commercial extension	Credential metadata, secure autofill, TOTP, and authenticated workflow support
AudioBridge	Current commercial extension	Browser audio capture and transcription-oriented workflows
MobileBridge for iOS	Current commercial extension	iOS device discovery and session support for managed environments
Vulpine Sentinel	Roadmap	Fleet stealth health monitoring
Vulpine Replay	Roadmap	Deterministic replay and audit bundles
Vulpine Clockwork	Roadmap	Mid-session identity rotation

Product Boundary

The public/open pieces are:

VulpineOS runtime
Foxbridge
Vulpine Mark
Android MobileBridge
public docs and API positioning

The source-closed pieces are:

Vulpine API service implementation
Vault
AudioBridge
iOS MobileBridge
planned commercial products such as Sentinel, Replay, Clockwork, Prism, Pulse, Forge, Scribe, Harbor, Mesh, and Oracle

See Source Availability for the exact boundary and API Reference for the endpoint-level contract.