Documentation
OpenAPIAgent index

Security, privacy, and billing

Tenant boundary

Every resource is organization-scoped. A customer token, device signature, object identifier, artifact URL, or MCP session from one organization must not enumerate or invoke another organization's agents, traces, repositories, skills, or usage.

Credential boundary

  • organization tokens authenticate only to Dharma;
  • local provider keys stay on the device;
  • GCP Vertex BYOK uses workload identity federation, not downloaded JSON keys;
  • browsers never call internal runtimes, workers, or providers directly;
  • control-agent approvals require the authenticated portal identity.

Evidence policy

The local vault stores complete evidence encrypted on the device. The active organization policy controls what leaves it. Continuous content synchronization requires an explicit bounded policy defining retention and upload limits. Withdrawal stops future synchronization and tombstones content uploaded under that grant according to the server contract.

Always preview capsules, exclude unrelated roots, and avoid credentials, personal data, privileged legal material, medical data, or regulated content unless the organization has approved the corresponding processing boundary.

Execution authority

Remote tasks are signed, expire, use durable leases, and run within registered workspace, path, command, network, Git, and budget policy. Unknown providers receive generic setup guidance only; unsupported execution or activation is never implied.

Billing

The customer-visible ledger settles credits idempotently. Managed execution can include model, compute, tools, storage, traces, and analysis. Local BYOK does not incur a Dharma provider-token charge but can incur analysis and orchestration usage. GCP Vertex BYOK provider charges remain in the customer project while Dharma services remain in the organization ledger.

Use GET /api/v1/orgs/{orgId}/agent-fabric/usage with usage:read to reconcile customer-visible usage. Do not estimate an invoice by counting API responses alone.

Incident and offboarding

  1. Disable the narrowest affected capability.
  2. Revoke organization tokens and enrolled devices.
  3. Stop relay and runtime execution.
  4. Revoke GitHub and workload-identity access.
  5. Export required audit records.
  6. Apply the retention and deletion policy.
  7. Verify no new task, run, rollout, or usage event can be created.