What ships with it
Pick the thinnest integration that works
Most clients only need HTTP or MCP. Reach for packages when you want framework conventions baked in.
One contract, multiple transports
The same plans, sessions, scoring, and registry concepts show up in REST, MCP, and package-level integrations.
Good defaults for agent clients
MCP remote configs and API key scopes make it straightforward to onboard a coding agent or assistant.
Documentation first
Package and protocol docs are public, so teams can validate the contract before they commit to an integration style.
Surface area
Best when you are already inside the Laravel stack and want the same patterns the platform uses internally.
Best when the job spans repositories, release automation, or build orchestration.
Best for backend systems, dashboards, or scripts that want explicit HTTP endpoints and generated OpenAPI docs.
Best for AI assistants and agent runtimes that already speak the Model Context Protocol.
Choose the right lane
There is no thick, generated SDK layer here by design. The package docs and protocol docs are the contract.