Agent-readable docs index: /llms.txt. Full docs in one file: /llms-full.txt. Download /docs.zip to grep all markdown files locally.

Integrate an agent

Establish the integration boundary

This guide connects an executor to the browser use supervisor. To protect your existing website or API, start with Company setup. How Halfspan works explains which credentials and endpoints belong to each integration.
Your organization supplies the task, approved terms, and authority. Trusted orchestration creates the run and issues credentials scoped to its service. Obtain the service origin and restricted bearer token from your integration operator. There is no public endpoint for an agent to enroll itself or mint its own authority.
The browser use supervisor exposes a configured action catalog through a browser adapter. The executor can request only those actions. The merchant, bank, and broker examples use synthetic transaction data; they do not move real funds.

Follow the action cycle

  1. Read the service capabilities and current observation.
  2. Select an action from the released catalog. Use its current target, arguments, observation, and state references.
  3. Submit a structured proposal describing the selected action and expected effects.
  4. Inspect the decision. An ALLOW verdict alone is insufficient: execution requires the issued single-use permit and the same scoped service credential.
  5. Execute the exact operation with the permit, then inspect its receipt and the next observation.
Use the protocol guide for schemas and the transport guide for HTTP and MCP contracts. Browser-local actions require the trusted browser runner.

Handle stops explicitly

A clarification request, authorization request, refusal, or operational failure is not permission to act. Read the stop context and follow the eligible recovery action. Exact approval belongs to the owner. Clarification never expands existing authority.
If an operation may have been dispatched, reconcile its receipt and external outcome before attempting another mutation. A timeout is not proof that nothing happened.

Retain evidence

Keep observation, proposal, decision, permit, and receipt references together. Use the evidence guide to assess signed records and their limits. Provider explanations remain untrusted evidence, even when included in a signed record.