Integrate over HTTP
The package is a FastAPI service run through Uvicorn. Its application registers messaging, workflow, policy, batch, and health routers.
Inspect the sourceSELF-HOSTED HTTP SERVICE
Run a FastAPI service for governed messaging and workflow coordination. Connect message submission, policy evaluation, and operational state through explicit HTTP interfaces.
For platform teams evaluating a shared service between agents and workflows.
POST /api/v1/messages
HTTP 202 AcceptedWHERE IT FITS
Use this when agent communication and workflow operations need a service boundary. Message acceptance and execution authorization remain distinct.
Use the authenticated message endpoint with the required tenant context.
Select the documented processing mode and inspect the result body.
Use workflow and health interfaces with the configured service dependencies.
INSIDE THE PRODUCT
Follow each behavior to its implementation or maintained documentation.
The package is a FastAPI service run through Uvicorn. Its application registers messaging, workflow, policy, batch, and health routers.
Inspect the sourceThe validate_and_route mode includes a governance result in the response body while still returning HTTP 202. Interpret the body according to the message contract.
Inspect the sourceWorkflow routes provide creation, inspection, cancellation, and retry interfaces, delegating to executor and repository infrastructure.
Inspect the sourceThe production profile checks authentication secrets, shared Redis governance state, a workflow repository, and healthy policy and audit backends.
Inspect the sourceLOCAL EVALUATION
After following the pinned repository installation instructions, start the documented development profile on loopback. Production requires separate configuration.
Review the README and package dependencies with Python 3.11+. Source metadata is not a verified distribution pin.
The loopback command below starts a local HTTP process using the development profile. Read the authentication and endpoint setup before sending requests.
Read the startup contract and hardening report before choosing Redis, policy, audit, and workflow infrastructure.
EAB_PROFILE=dev uvicorn enhanced_agent_bus.api.app:app \
--host 127.0.0.1 --port 8000Documented local startup. This command was not executed during the website audit.
Copy the example or select the code manually.
DESIGN AROUND THE BOUNDARY
The integration and operating conditions are part of the product decision.
No. Default submission accepts a message for processing. The synchronous validation mode also returns 202; its body carries the governance result. A bus response is not the gove-zone execution gate.
Durable message-status persistence is not implemented in the inspected production configuration. Development uses an in-memory store; unavailable production status lookup returns HTTP 501.
The explicit production profile, authentication secrets, shared Redis governance state, workflow persistence, and healthy policy and audit backends. A successful local start does not establish production readiness.
The hardening report leaves deeper receipt-gate integration open. The standalone Z3 route can produce synthetic results when its external verifier backend is absent; this page makes no formal-verification claim.
SOURCE, RELEASE, AND CHECKS
3.0.2 is inspected source metadata. No GitHub releases were returned in this audit; current PyPI publication was not independently verified.
Reviewed 2026-09-08. Source version and published release are tracked separately.
The inspected head has a green CI run covering selected smoke, regression, conformance, and critical-path suites. It is not a run of every repository test or proof of production operation.
Read the workflow evidenceFROM READING TO EVALUATION
Follow one example. Inspect the result. Decide whether it fits your workflow.