From business request to AI result
FlowBeacon connects tasks with configured AI resources and returns results your application can handle. Keep the request, execution status and proposed next step connected.
The example is a local simulation. Production execution requires an account, configured tasks and provider access.
Illustrative task · no model call
A team needs a clearer review brief. Its application supplies the task and a document excerpt. Explore three possible response states using fictional data.
01 / Application request
“Suggest a clearer task description from the context below and identify missing information.”
This is an explanatory scenario, not a submitted execution request or a promise of legal review.
02 / FlowBeacon response
Showing a simulated completed response.
Proposed task description: “Review the scope of services in supplier agreement v3. Confirm who owns the review before scheduling approval.”
Uncertainty: The review owner is not included in the supplied context.
The application still validates this proposal. The task has not been changed or marked complete.
Keep the original invocation and correlation identifiers. An authorized replay of the same request can retrieve its recorded result.
Pending is not a failure or permission to start a duplicate execution. The result contract does not add an automatic polling worker.
The response provides an error code, category and retryability flag. The application decides whether recovery or intervention is appropriate.
A simulated or degraded provider response is not accepted as a successful negotiated result.
How it works
Your application chooses the task, supplies relevant context and checks whether execution is allowed.
For signed execution requests, FlowBeacon checks the request identity and uses the configured technical-task mapping.
The runtime calls the selected provider with the prepared prompt and required output format.
The application receives a correlated result, pending state or error. It validates the output before applying business changes.
Capabilities with a defined scope
Available behavior depends on the execution path and deployment. These are implementation capabilities, not a live availability report.
Supported task profiles return schema-bound output with execution correlation. Pending and error responses remain distinct.
OpenAI execution code is present. Real calls require provider credentials, task mapping, quota entitlement and enabled provider networking.
The repository also includes voting, fallback and workflow components. Their availability depends on the selected path; they are not all implied by one API call.
Two ways to connect
Integrate with the HTTP API. Your application owns task preparation, authentication, context selection and acceptance of the result.
The structured-result path requires a trusted issuer and a configured technical task. Installing the SDK alone does not enable execution.
Start with the API guide →Use AI within a business workflow. Robo Connector supplies the scoped request and receives proposals for domain validation and review.
Technical success does not close a matter, approve a document or complete a business task.
Explore Robo Connector →Context & control
The caller decides what information belongs in a request and which business actions it may authorize. FlowBeacon executes within the configured integration and returns the technical outcome.
Context Engine supports queue and memory integrations. The direct HTTP path has its own request contract; it does not imply that every call subscribes to a shared Task Board.
Read the integration boundaries →Risk, legal requirements and approval decisions need explicit application rules. Token verification does not establish business eligibility.
API & PHP SDK
Use HTTP for execution and the PHP SDK for token verification and structured-result parsing.
Install with Composer
composer require robo-meister/flow-beacon-apiPHP 8.2+ · Composer 2
The package provides authentication and result-contract helpers. It does not send or automatically poll execution requests.
SDK source & contracts →Availability & costs
Features and usage limits depend on your account and plan.
View plans →Confirm how credentials and provider usage are billed in your deployment. A FlowBeacon account alone does not establish access to a model.
The demonstration uses fictional, local content. It does not consume provider tokens or show production performance measurements.
Explore the example →Start with one task
Account setup uses the shared Robo Meister sign-in. Provider configuration is a separate step.