Phrony exposes a JSON HTTP API for running agents from your own backends and clients. Requests useDocumentation Index
Fetch the complete documentation index at: https://docs.phrony.com/llms.txt
Use this file to discover all available pages before exploring further.
https and, for authenticated routes, a workspace API key in the X-API-Key header.
Base URL
| Environment | Base URL (example) |
|---|---|
| Phrony Cloud | https://api.phrony.com |
| Self‑hosted or staging | As configured by your team (path layout under /v1 is the same) |
https://api.phrony.com/v1/agents/{agentId}/runs.
Quick examples
SetPHRONY_API_KEY and AGENT_ID from the Phrony dashboard. Use runId from the start response to poll. Each group shows the same start a run, then get run flow.
Versioning
All documented paths use thev1 prefix. Future versions, if any, will be named explicitly.
How this relates to the guides
- Embedded agents — End‑to‑end flow: API trigger, API key, start run, poll, optional file uploads, and code samples.
- Trigger ingress — Operational log in the Phrony dashboard for API and event start attempts.
Next steps
Authentication
API keys, headers, and how access is scoped to agents, triggers, and runs.
Agents
Start a run and list sessions for an agent.
Runs
Poll status, conversation, stream, and session messages.
File library
Presign, upload, finalize, and file references in run input.