SELF-HOSTED HTTP SERVICE

A coordination layer
for agent messages.

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.

Documented HTTP behavior

Accepted does not mean approved.

POST /api/v1/messages

HTTP 202 Accepted
Default submission
accepted for processing
validate_and_route
inspect the governance result
HTTP 202 is a transport response, not permission to perform a side effect. No live request is sent.
Evaluation · operational setup requiredSource 3.0.2Python 3.11+Apache-2.0View evidence

WHERE IT FITS

A clear place in your stack.

Use this when agent communication and workflow operations need a service boundary. Message acceptance and execution authorization remain distinct.

  1. 01

    Submit the message

    Use the authenticated message endpoint with the required tenant context.

  2. 02

    Evaluate + route

    Select the documented processing mode and inspect the result body.

  3. 03

    Operate the workflow

    Use workflow and health interfaces with the configured service dependencies.

One service, several operational surfaces.

MESSAGES
Submission, validation mode, and message lifecycle.
WORKFLOWS
Create, inspect, cancel, and retry operations.
POLICIES
Policy and governance state interfaces.
HEALTH
Service health and operator-controlled agent overrides.

INSIDE THE PRODUCT

Capabilities you can inspect.

Follow each behavior to its implementation or maintained documentation.

01

Integrate over HTTP

The package is a FastAPI service run through Uvicorn. Its application registers messaging, workflow, policy, batch, and health routers.

Inspect the source
02

Read the governance result

The 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 source
03

Coordinate workflow operations

Workflow routes provide creation, inspection, cancellation, and retry interfaces, delegating to executor and repository infrastructure.

Inspect the source
04

Make production dependencies explicit

The production profile checks authentication secrets, shared Redis governance state, a workflow repository, and healthy policy and audit backends.

Inspect the source

LOCAL EVALUATION

Inspect the local service contract.

After following the pinned repository installation instructions, start the documented development profile on loopback. Production requires separate configuration.

  1. Prepare the source environment

    Review the README and package dependencies with Python 3.11+. Source metadata is not a verified distribution pin.

  2. Start the development profile

    The loopback command below starts a local HTTP process using the development profile. Read the authentication and endpoint setup before sending requests.

  3. Review operational gaps

    Read the startup contract and hardening report before choosing Redis, policy, audit, and workflow infrastructure.

Open full setup instructions Open the pinned checkout
Shell · installed source environment
EAB_PROFILE=dev uvicorn enhanced_agent_bus.api.app:app \
  --host 127.0.0.1 --port 8000

Documented local startup. This command was not executed during the website audit.

Copy the example or select the code manually.

DESIGN AROUND THE BOUNDARY

Know the scope.

The integration and operating conditions are part of the product decision.

Does HTTP 202 authorize an action?

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.

Is production message-status lookup durable?

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.

What does the service need in production?

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.

Are formal verification and receipts complete?

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

Evidence with a reference.

3.0.2 is inspected source metadata. No GitHub releases were returned in this audit; current PyPI publication was not independently verified.

INSPECTED SOURCEenhanced-agent-bus 3.0.2e4ecaf56b31a

Reviewed 2026-09-08. Source version and published release are tracked separately.

CI SNAPSHOT · 2026-09-08Selected CI checks passed

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 evidence

FROM READING TO EVALUATION

Start with the source.

Follow one example. Inspect the result. Decide whether it fits your workflow.