Agent Control Server
FastAPI server that powers Agent Control. It manages agents and controls, evaluates requests at runtime, and exposes REST APIs used by the SDKs and UI.
What it provides
- Agent registration and control association
- Control CRUD and evaluator configuration
- Runtime evaluation (
/api/v1/evaluation) with pre/post stages - Observability endpoints for events and stats
- API key authentication for production deployments
Quick start (local)
From the repo root:
make sync
make server-run
Server runs on http://localhost:8000. The UI expects this base URL by default.
To use non-default local ports with make server-run, export
AGENT_CONTROL_PORT for the server listen port. If you also want the local
Postgres container exposed on a different host port, set
AGENT_CONTROL_DB_HOST_PORT and point the server at the same value with
AGENT_CONTROL_DB_PORT.
Database migrations
The server package includes the agent-control-migrate command for bundled
Alembic migrations.
In production, migrations are serialized with a Postgres advisory lock. Alembic runs each migration revision in its own transaction, so if an upgrade across multiple revisions fails, earlier revisions may already be committed. Check the current revision before retrying:
agent-control-migrate current
agent-control-migrate upgrade head
PostgreSQL driver runtime
agent-control-server depends on plain psycopg. The published Docker image
installs Debian libpq5 and sets PSYCOPG_IMPL=python so the server uses
psycopg's Python implementation with the OS libpq library.
For wheel-based deployments outside Docker, either install the OS libpq runtime
package for your platform, or install agent-control-server[binary] if you want
psycopg's bundled binary package.
Configuration
Server configuration is driven by environment variables (database, auth, observability, evaluators). For the full list and examples, see the docs.
Full guide: https://docs.agentcontrol.dev/components/server
1 maintainer
Metadata
1 maintainer
Release files for agent-control-server 8.14.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| agent_control_server-8.14.0.tar.gz | 306.8 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| agent_control_server-8.14.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 508.8 kB
Release files / agent_control_server-8.14.0.tar.gz
| Download URL | agent_control_server-8.14.0.tar.gz |
|---|---|
| Size | 306.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
011cf0e9b30d93371c824dfbbddadeadc836f50d4155c9e41bdbaebaf4f90183
|
|
BLAKE2b-256 checksum How to use checksums |
742242de801a13c5d8569e9f9884d6efa93438d76eed1daac1446236c239cfb0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Release files / agent_control_server-8.14.0-py3-none-any.whl
| Download URL | agent_control_server-8.14.0-py3-none-any.whl |
|---|---|
| Size | 202.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
587ae2c69ad4bfb14207c860e823d39e80bbec99b28f1f6a29499bf969cc525f
|
|
BLAKE2b-256 checksum How to use checksums |
3a6c0df087071116af72e23fa141b31cc9786258e1aad1137b28021aaa3a3dc5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Security for agent-control-server 8.14.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
