One interface. A clear scope.

Pharen API

Embed defined workspace data, workflows and agent steps into existing applications. Endpoints, permissions and deployment follow your Pharen setup.

Example — paths and fields depend on the setup
curl --request POST \
  --url https://your-pharen-host.example/api/v1/workflows/invoice-review/runs \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '{
    "input": {
      "document_id": "doc_example_184",
      "requires_approval": true
    }
  }'

Workspace Context

Read approved data from Lists, Projects or documents for a defined purpose.

Discuss an API setup

Workflow Runs

Start a workflow, query status and return a reviewed result.

Discuss an API setup

Agent Tasks

Run a bounded agent task with a goal, sources and an approval point.

Discuss an API setup

Embed agent steps

Run a bounded agent task and review the output before it moves on.

Discuss an API setup
Deployment and control

The API follows your Pharen setup.

Cloud or self-hosted, authentication, data areas and limits are agreed before production use.

Deployment and controlAPI building blocksAPI
AuthenticationTokens, roles and validity constrain access to the agreed use case.
Data scopeEndpoints return only the fields and workspace areas the integration needs.
ObservabilityRequests, workflow status and failure paths remain traceable in operations.
Support and limitsRate limits, availability and support scope are documented for the chosen operation.

The exact contract follows the setup.

Start with one clear endpoint

Bring the application that needs Pharen context.

We will clarify data, actions, authentication and deployment and turn them into the smallest useful API contract.