Tenant-facing execution docs

Billing: plan + pay-as-you-go balance

Your monthly plan covers the platform (browser runtime, fetch, workflows, keys) and a monthly task quota. Tools with a per-call provider cost are charged from a prepaid balance you top up in your workspace. Tasks past the quota run as overage at $0.010 each instead of being blocked.

Every task response includes charged_usd; failed tasks are refunded automatically (refunded: true). When the balance can't cover a call you get HTTP 402 with price_usd, balance_usd and top_up_url - handle it by prompting a top-up. The Knowledge API below is free and needs no key.

Knowledge API & MCP (free, no key)

Read-only JSON about Pludor's live products, stores, features and pricing - product records, alternatives, comparisons, plain-language product matching, store records, feature facts and pricing. No API key; rate limited per IP.

curl "https://pludor.com/api/knowledge/product-answer?q=portable+blender+under+40"

Knowledge API docs & live examples · OpenAPI spec (Knowledge + OPS) · AI commerce manifest · MCP server for AI clients: https://mcp.pludor.com/mcp (9 read-only tools)

Auth

Use a tenant API key created in the OPS workspace. Send it as a Bearer token on every request.

Authorization: Bearer ops_live_...

Endpoints

User browser bridge

OPS now supports two browser runtimes. The server runtime runs in `aura-ops`. The user browser bridge runs inside the account owner's actual browser through the OPS Browser Bridge extension.

1. Go to /me/ai_friend or /me/ops
2. Generate a browser bridge token
3. Download https://age.pludor.com/ops/browser-bridge.zip and unzip it
4. In Chrome, go to chrome://extensions, enable Developer mode, click
   "Load unpacked", and select the unzipped folder
5. Paste the token and your Pludor base URL into the extension popup
6. Aura and direct OPS browser tasks will prefer your own browser when the bridge is online

Create a task

The current public contract is queue-first. Every task returns a `public_task_id` that you use for status polling.

curl -X POST https://age.pludor.com/api/ops/tasks \
  -H 'Authorization: Bearer ops_live_...' \
  -H 'Content-Type: application/json' \
  -d '{
    "tool": "web_fetch",
    "params": {
      "url": "https://example.com"
    },
    "metadata": {
      "source": "demo-app"
    }
  }'

Workflow templates

Saved workflows turn raw tools into reusable outcomes. The initial public templates cover browser open, browser extract, browser sequence, and research summary patterns. Trigger types currently supported are manual, webhook, and schedule.

curl -X POST https://age.pludor.com/api/ops/workflows \
  -H 'Authorization: Bearer ops_live_...' \
  -H 'Content-Type: application/json' \
  -d '{
    "name": "Twin docs extractor",
    "template_key": "website_extract",
    "trigger_type": "webhook",
    "params": {
      "url": "https://docs.twin.so/web-agent"
    }
  }'

Run a saved workflow

curl -X POST https://age.pludor.com/api/ops/workflows/owf_abc123/run \
  -H 'Authorization: Bearer ops_live_...' \
  -H 'X-Idempotency-Key: nightly-research-2026-04-30' \
  -H 'Content-Type: application/json' \
  -d '{
    "callback_url": "https://your-app.example.com/ops/callback",
    "metadata": {
      "source": "ops-docs"
    }
  }'

Use X-Idempotency-Key or idempotency_key to make repeated requests safe. Add callback_url when you want OPS to POST the completed run back to your app.

Trigger a webhook workflow

curl -X POST https://age.pludor.com/api/ops/webhooks/owh_abc123 \
  -H 'Content-Type: application/json' \
  -d '{
    "params": {
      "url": "https://example.com"
    },
    "metadata": {
      "event": "nightly-research"
    }
  }'

Poll status

curl https://age.pludor.com/api/ops/tasks/ops_abc123 \
  -H 'Authorization: Bearer ops_live_...'

Plan-aware capabilities

Capability inventory