1. Discover authorized capabilities
Use the BOS identity connection and authenticated MCP discovery. Read current service descriptors and their versioned contracts. Discovery describes capabilities; it grants no authority.
Give AI agents controlled execution over your services.
BOS is a service gateway. Build clients that help people plan complex workflows while BOS executes sanctioned work through permissioned state machines. Service infrastructure, authoritative business state, data stores, and private implementation IP stay outside the agent host.
For companies connecting business services to AI agents and builders creating clients for those services. Authorized inputs and results, public client skills, and permitted caches may reach the agent workspace.
Build around the control your business needs.
Your client supplies reasoning and domain expertise. BOS owns permissions, workflow state, provider integrations, approvals, and receipts.
2. Request sanctioned execution
Invoke the exact deterministic HTTPS operation returned by discovery, using its declared inputs. BOS revalidates current actor, organization, application, installation, role, and capability before private work.
3. Present evidence and next actions
Show attributed results, required approvals, receipts, and unresolved exceptions. Service-owned state machines control workflow transitions, persistence, and recovery.
Verified starting points
Use the existing public resources and the contracts returned by current authenticated discovery.
Connect an OAuth client
Discover the published BOS connection metadata and follow the existing user-operated PKCE example.
Read the public OAuth client example →Consume streaming source results
Discover the optional bos/source-results/v1 contract, negotiate SSE delivery, and consume pages and terminal results.
Read the streaming API contract →Explore current product guidance
Review the documented plugin views, supported workflows, and integration requirements.
Read product documentation →Inspect the public client packages
Review the BOS client skills, package guidance, and supported installation instructions.
View the public client repository →Compose workflows with BOSL
Agent-Driven Custom Journeys coordinate discovered client and server capabilities. BOSL has two node ownership values: client and server.
A server-executable node names an existing sanctioned semantic operation. BOS Service validates the operation’s inputs, outputs, approvals, permissions, limits, and public errors before registration, then rechecks current access and readiness during execution. A journey creates no new authority.
Start with a workflow your business needs, identify its approval points and expected results, and use the public contracts returned by authenticated discovery. Integration availability and workflow readiness depend on the configured services.
Bring one workflow to the conversation.
Request an invite to discuss your service, client, and control requirements. Access is reviewed; requesting an invite creates no automatic access.