Route an outcome before an agent spends, posts, or runs.
Live demo | OpenAPI | Evaluator quickstart | Product launch checklist | Safety boundary
Bean Execution Gateway is a public beta POC for agent routing. Give it an outcome and it returns a decision memo that compares whether to use an owned agent, use an available public path, build a new agent, or block unsafe work before execution.
It is built for agents and developers who need a control layer before execution: policy gates, cost checks, context-risk checks, supplier readiness, proof requirements, and metadata-only learning signals.
- Open the live demo.
- Use public or synthetic input only.
- Run one guided route:
- Use public path
- Use or build
- Block risky work
- Read the decision memo.
- Run the proof packet if one is available.
- Leave metadata-only route feedback.
The first useful output should be a route memo, not a wall of JSON.
- Outcome-to-agent-path routing.
- Build vs use vs block decisions.
- Quality, speed, cost, risk, proofability, learning, trainability, and readiness scores.
- Public-demand discovery and local proof packets.
- Spend, private-data, public-write, and external-supplier gates.
- Metadata-only feedback for learning which routes were useful.
Most agent tools focus on making an agent execute. BEAN focuses on the step before that: deciding which execution path should run at all.
flowchart LR
A["Outcome request"] --> B["Policy and context gates"]
B --> C["Path ranking"]
C --> D["Use owned agent"]
C --> E["Use public path"]
C --> F["Build new agent"]
C --> G["Block risky work"]
D --> H["Decision memo and proof"]
E --> H
F --> H
G --> H
This repo is intentionally source agnostic. Demand can come from GitHub, chat, browser agents, internal tools, workflow platforms, or public task feeds. Supply can eventually include owned agents, public reusable agents, local runners, workflow adapters, and external suppliers. The hosted beta currently executes none of those external suppliers.
Run the public demo locally:
npm install
npm run gateway:verify
npm run gateway:demoOpen http://127.0.0.1:8787.
Route a sample outcome:
curl -s -X POST http://127.0.0.1:8787/v0/path \
-H 'content-type: application/json' \
--data @examples/execution-gateway/open-demand-path-request.jsonCheck readiness:
curl -s http://127.0.0.1:8787/v0/readyUse the SDK stubs:
Core endpoints:
GET /v0/healthGET /v0/readyGET /v0/metricsGET /v0/examplesGET /v0/openapi.jsonPOST /v0/pathPOST /v0/routePOST /v0/v2/feedbackPOST /v0/dispatch
Public-demand endpoints:
GET /v0/open-demand/learningPOST /v0/open-demand/scanPOST /v0/open-demand/opportunities/{opportunity_id}/bundlePOST /v0/open-demand/tasks/{task_id}/run
Product-contract endpoints:
GET /v0/v1/goalsGET /v0/v1/readinessGET /v0/v2/goalsGET /v0/v2/readinessPOST /v0/v2/intakePOST /v0/v2/supply/bidsPOST /v0/v2/execution/plansPOST /v0/v2/acceptanceGET /v0/v2/gtm
See API examples and the live OpenAPI contract.
The hosted demo is ready for trusted public beta review only.
It does:
- Accept public or synthetic inputs.
- Spend
0 USD. - Keep dispatch disabled.
- Reject private-like input before routing.
- Emit security and rate-limit headers.
- Store feedback as enumerated metadata only.
It does not:
- Execute external work.
- Call suppliers, freelancers, marketplace agents, LLM APIs, payment rails, trading tools, or hosted compute providers.
- Process private repositories, customer data, company data, secrets, credentials, regulated data, or local files.
- Authenticate tenants or isolate customer workspaces.
- Charge requesters or pay suppliers.
- Claim marketplace liquidity.
/v0/ready intentionally reports production_ready: false.
This repo is ready to evaluate as a public demo and trusted beta candidate. It is not ready for customer, private, paid, or external-supplier traffic.
Run the local launch audit:
npm run launch:readinessThe audit intentionally returns a report with:
public_demo_ready: truetrusted_beta_review_ready: truebroader_public_push_ready: falsecustomer_private_paid_or_supplier_ready: false
The full launch-control checklist is docs/product-launch-checklist.md.
This beta is useful if you are building or evaluating:
- Agent routing systems.
- Agent marketplaces.
- Build-vs-buy agent decisions.
- Multi-agent orchestration.
- Public-demand learning loops.
- Safe execution gates before autonomous work.
- Agent-facing APIs that need proof, policy, and cost controls.
Start with Evaluator quickstart, then use How to review.
assets/execution-gateway-demo/- hosted demo UI.scripts/- routing, server, verification, and package tooling.schemas/execution-gateway/- JSON Schema and OpenAPI contracts.examples/execution-gateway/- copy-paste request and response examples.fixtures/execution-gateway/- proof tasks and adversarial policy fixtures.sdk/execution-gateway/- JavaScript and Python client stubs.docs/- product, beta, safety, API, and readiness docs.CONTRIBUTING.md,CODE_OF_CONDUCT.md, andROADMAP.md- beta contribution and product direction..github/- issue templates, PR template, and CI workflow.llms.txtandllms-full.txt- agent-readable repo context.
npm test
npm run gateway:verify
npm run launch:readiness
BEAN_GATEWAY_BASE_URL=http://127.0.0.1:8787 npm run gateway:smoke:hostedLive hosted smoke:
BEAN_GATEWAY_BASE_URL=https://bean-execution-gateway-poc.onrender.com npm run gateway:smoke:hostedThe verification suite checks proof tasks, adversarial policy fixtures, schema self-tests, registry lint, open-demand guardrails, zero spend, zero external writes, disabled dispatch, hosted private-input rejection, metadata-only metrics, V1 contracts, and V2 product contracts.
Useful search phrases for this repo:
- agent execution gateway
- agent routing gateway
- outcome to agent path
- build vs use agent decision
- source agnostic agent marketplace control plane
- public demand agent proof runner
- metadata-only agent feedback
- zero-spend agent execution guardrails
See LICENSE.