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.
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
}
}'The API follows your Pharen setup.
Cloud or self-hosted, authentication, data areas and limits are agreed before production use.
| Deployment and control | API building blocks | API |
|---|---|---|
| Authentication | Tokens, roles and validity constrain access to the agreed use case. | |
| Data scope | Endpoints return only the fields and workspace areas the integration needs. | |
| Observability | Requests, workflow status and failure paths remain traceable in operations. | |
| Support and limits | Rate limits, availability and support scope are documented for the chosen operation. |
The exact contract follows the setup.
The complete AI stack for your company.
Intuitive for teams. Ready for advanced use cases.
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.





