Switchyard Default First Success
The easiest mistake for a first-time Switchyard visitor is opening twenty docs
tabs before proving even one bounded path.
This page only does one job:
Compress the shortest, most honest, most valuable first-success route into
one line.
In plain English:
- start the Switchyard service runtime
- prove the runtime is alive
- prove it can accept one minimal invoke
- only then move into builder packs, starter packs, or compat lanes
Default Route
Step 1. Start the local service runtime
pnpm run start:service-local
Think of this as turning the power on for the runtime.
Default port:
Step 2. Prove the read-only runtime surface is alive
pnpm run example:mcp-inspector
This proves:
- the service runtime is reachable
- the read-only MCP surface can boot
- the tool inventory is readable
runtime.health is actually reachable
If you only need to prove that the runtime on this machine is alive, stopping
here is already a useful first success.
Step 3. Prove one minimal invoke path
pnpm run example:runtime-bridge
This is the closest minimal proof of the Switchyard value proposition:
- it sends one bounded JSON body through
/v1/runtime/invoke
- it proves the shared runtime can do more than list tools and print catalogs
This step needs your own valid access material:
- for
BYOK
- the target provider API key
- for
Web/Login
- a valid web-login session, cookie bundle, and user agent
If You Get Stuck
You cannot get past Step 2
Start here:
Step 2 works, but Step 3 fails
That usually does not mean “the repo is broken.” It usually means:
- the target provider credentials are not ready
- the current workstation is missing session material
- the browser session, cookie bundle, or user agent is incomplete
Start here:
What To Open Next
I want the builder path next
Open:
I want to wire this into a host next
Open:
What This Path Proves
- Switchyard really has a service-first runtime front door
- the repo really has a runnable read-only MCP surface
- the repo really has an executable minimal invoke starter
- you do not need to pretend you already have full Codex, Claude Code, or
OpenClaw parity
What This Path Does Not Prove
- full consumer parity
- an MCP execution brain
- any marketplace is already listed
- every Web/Login provider on every machine is already live-ready
Closing Sentence
Run one bounded success first.
Open builder lanes second.
That is the most honest front door Switchyard can offer today.