One entry point
Start a unified conversation through the enterprise portal, workflow page, or mobile app—no need to understand the systems behind it.
One request, coordinated systems
Powered by the BoltFusion agent runtime, this solution connects travel requests, bookings, pre-trip services, expense claims, and reconciliation. Key write operations require human confirmation, and every result is traceable and can be read back.
The solution first unifies the entry point and runtime contract, then gradually replaces connectors with live integrations. The demo uses no customer data and does not present simulated results as production capabilities.
Start a unified conversation through the enterprise portal, workflow page, or mobile app—no need to understand the systems behind it.
Create runs, poll status, and read business results using the standard BoltFusion Agent API paths.
Internal systems use production adapters; ticketing, hotels, weather, and other services are demonstrated first with replaceable mock adapters.
Authentication, permissions, and human confirmation jointly protect real writes. Monitor is for observation and diagnostics only.
Each stage can be integrated independently or share the same run, trace, and business identity. Resume from interruption points and route exceptions to a human.
Say it once. The request is created automatically.
Recommend first, confirm before booking
Proactive alerts for important changes
Automated receipt collection
Searchable results, traceable exceptions
External calls enter only through the Agent API; Work stays internal; Monitor provides pages, logs, records, and diagnostics.
POST /api/agents/{agentKey}/runsPolicies · Tools · Browser TasksRecords · Logs · ReplayRun creation and status queries go through the business entry point. Monitor does not accept business write requests and is not the final authority on success.
POST …/agent-api/api/agents/{agentKey}/runsInclude a stable idempotency key and business input. An immediate response means only that the request was accepted.
GET …/agent-api/api/agents/{agentKey}/runs/{runId}Handle statuses such as queued, running, waiting_input, succeeded, and failed.
succeeded + requestId + workerStageA page toast, HTTP 200/202, or visibility in Monitor alone is not proof of success.
Write Boundary: Actions such as bookings, submissions, and authorizations pass through a policy gate. Demos use a simulated provider by default and do not call real third parties.
POST /api/boltfusion/interface/agentProxy/agent-api
/api/agents/agent.ecology.e9.workflow.request.create/runs
X-Idempotency-Key: travel-demo-20260729-001
Content-Type: application/json; charset=utf-8
{
"input": {
"workflowName": "Travel request",
"prompt": "Visit a regional center for a three-day project visit",
"formFields": { "destination": "A regional center" }
},
"trace": true,
"metadata": {
"clientRequestId": "travel-demo-20260729-001",
"providerMode": "simulated"
}
}Connectors isolate vendor differences, so upper-level orchestration stays vendor-agnostic. Switching from Mock to a live service preserves the same business semantics.
Unified Authentication · Semantic Mapping
Policy Checks · Runtime Evidence
After you press play, the employee and AI clarify the request, options, and confirmation together.
Define the checks and pass criteria first. After launch, use data from real workflows to see whether efficiency improves.
Users no longer need to find each system manually, while clear boundaries remain in the backend.
Search and analysis can be automated; bookings, submissions, and permission changes must pass policy checks.
Each run is associated with a runId, traceId, requestId, and workerStage.
Mock and production implementations share a semantic contract, so switching does not change upper-level orchestration.
Freeze business semantics and interface contracts first, then connect enterprise systems. Use third-party mock adapters throughout integration testing, replacing them one by one once providers and authorizations are confirmed.
Process scope, fields, identities, permissions, success criteria
Deliverables: interface inventory + acceptance matrixAgent API, workflow platform, organizational finance, third-party mocks
Deliverables: runnable end-to-end flow + Monitor evidenceProduction adapters for ticketing, hotels, weather, invoices, and more
Deliverables: integration test report + degradation planReal-role validation, performance baselines, exception replay, metrics governance
Deliverables: business sign-off + operations dashboardThis solution is a sanitized demo. People, locations, IDs, orders, provider responses, and reported outcomes shown on this page are generic examples or simulated data.