Browser agent

Permanently delete every redacted Browser Agent approval and execution audit record in this account. This cannot be undone; local extracted results remain only in each browser until that browser clears its extension storage.

Marked confirm: this operation is irreversible, reaches real people, or spends money. Holding a credential is itself the confirmation for API and MCP callers — call it only when you mean it. The in-app assistant refuses to run it without a human approving first.

Parameters

No parameters — POST an empty body.

Example

curl -X POST https://app.chirply.io/api/v1/actions/browser_agent.clear_runs \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{}'

Over MCP the same operation is the tool browser_agent_clear_runs at https://app.chirply.io/api/mcp, same bearer token, same input.

Create a single-use Browser Agent pairing code for this account. The code expires in ten minutes and can mint one revocable browser credential; it does not publish, message, or modify any social account by itself. The response also returns installUrl, the Chrome Web Store listing a person adds the extension from before entering the code in its side panel.

Parameters

No parameters — POST an empty body.

Example

curl -X POST https://app.chirply.io/api/v1/actions/browser_agent.create_pairing \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{}'

Over MCP the same operation is the tool browser_agent_create_pairing at https://app.chirply.io/api/mcp, same bearer token, same input.

Permanently erase one standing approval and its link to past unattended runs. This cannot be undone, and it removes the audit trail's record of what used to run on its own — prefer revoking, which stops the automation but keeps that history. The paired browser drops its local copy on the next sweep.

Marked confirm: this operation is irreversible, reaches real people, or spends money. Holding a credential is itself the confirmation for API and MCP callers — call it only when you mean it. The in-app assistant refuses to run it without a human approving first.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/browser_agent.delete_automation \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
  }'

Over MCP the same operation is the tool browser_agent_delete_automation at https://app.chirply.io/api/mcp, same bearer token, same input.

Permanently delete one redacted Browser Agent approval and execution audit record from this account. This cannot be undone; it does not affect page data or extracted results because the platform never receives or retains them.

Marked confirm: this operation is irreversible, reaches real people, or spends money. Holding a credential is itself the confirmation for API and MCP callers — call it only when you mean it. The in-app assistant refuses to run it without a human approving first.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/browser_agent.delete_run \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
  }'

Over MCP the same operation is the tool browser_agent_delete_run at https://app.chirply.io/api/mcp, same bearer token, same input.

List the standing approvals in this account — the automations that let a paired browser run one approved action on one website on a schedule, with nobody watching it happen. Each entry shows the browser that granted it, the exact origin and path it may act on, how many packaged steps it runs, whether it ends by activating an outward control such as Post or Submit and what that control is labelled, its hourly run cap, when it was approved, when it must be re-approved, and whether it has been revoked. Page contents, task text, and field values are never stored and are not returned.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/browser_agent.list_automations \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "limit": 50
  }'

Over MCP the same operation is the tool browser_agent_list_automations at https://app.chirply.io/api/mcp, same bearer token, same input.

List the Chrome browsers currently paired with this account's Browser Agent Marketplace app. Returns display names, release channels, extension versions, last-seen times, and non-secret token prefixes; it never returns device credentials.

Parameters

No parameters — POST an empty body.

Example

curl -X POST https://app.chirply.io/api/v1/actions/browser_agent.list_devices \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{}'

Over MCP the same operation is the tool browser_agent_list_devices at https://app.chirply.io/api/mcp, same bearer token, same input.

List the redacted approval and execution audit trail for Browser Agent. It returns page origins, packaged action types, risk classifications, statuses, and result counts; page contents, task text, form values, cookies, credentials, and extracted records are never retained.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/browser_agent.list_runs \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "limit": 25
  }'

Over MCP the same operation is the tool browser_agent_list_runs at https://app.chirply.io/api/mcp, same bearer token, same input.

Stop one standing approval from running unattended ever again. The paired browser checks with the platform before every unattended run, so this takes effect on that browser's next sweep — within about five minutes — without anyone touching the machine. Scheduled work that the automation was handling returns to the manual queue for a person to do. The record is kept, not deleted, so the run history still shows what used to run on its own.

Marked confirm: this operation is irreversible, reaches real people, or spends money. Holding a credential is itself the confirmation for API and MCP callers — call it only when you mean it. The in-app assistant refuses to run it without a human approving first.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/browser_agent.revoke_automation \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
  }'

Over MCP the same operation is the tool browser_agent_revoke_automation at https://app.chirply.io/api/mcp, same bearer token, same input.

Immediately revoke one paired browser's access to this account. The extension keeps only its local task draft and last local result, but it can no longer create audited browser runs, read handoffs, or update this account until paired again.

Marked confirm: this operation is irreversible, reaches real people, or spends money. Holding a credential is itself the confirmation for API and MCP callers — call it only when you mean it. The in-app assistant refuses to run it without a human approving first.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/browser_agent.revoke_device \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
  }'

Over MCP the same operation is the tool browser_agent_revoke_device at https://app.chirply.io/api/mcp, same bearer token, same input.