For builders
Wire the line into your release.
Connect what you built, gate each release on a sealed plan, and fix with the smallest example in hand.
Connect
Bring the system as it is.
No SDK to add and no code to change. Plimsoll asks your system the way your users do.
An HTTPS endpoint
Paste a curl that already works. Studio reads the request, finds where the question goes and where the answer comes back.
An MCP server
Point at a tool server and name the tool to call. Each role is asked through it as itself.
Plimsoll Link
For a system on your own network: one outbound connection, no inbound firewall rule.
As every role
Roles go in a request field, a header or a test account per role, so a leak between roles shows up.
Release gate
A sealed plan, run on every release.
Seal a plan once in Studio. From then on your pipeline starts it with an API key and reads one of three verdicts.
# Start a run of a sealed plan (the key comes from Settings, API keys)
curl -s -X POST https://api.plimsollsi.com/api/v1/plans/$PLAN/runs \
-H "Authorization: Bearer $PLIMSOLL_KEY"
# -> {"id": "run_...", "state": "queued", ...}
# Ask until it is done, then read the verdict
curl -s https://api.plimsollsi.com/api/v1/runs/$RUN \
-H "Authorization: Bearer $PLIMSOLL_KEY"
# -> {"state": "done", "verdict": "PASS", ...}
# Hand the checks to your CI view (JUnit XML; ?format=sarif for SARIF)
curl -s https://api.plimsollsi.com/api/v1/runs/$RUN/report \
-H "Authorization: Bearer $PLIMSOLL_KEY" > plimsoll.xmlPASS
Every check held its line, with the bound to show it. Merge.
FAIL
A check crossed its line. The finding carries the example. Stop the merge.
INCONCLUSIVE
Nothing failed, but the plan cannot prove the line yet. It says what to add.
The passport, from the same run
Each finished run has its passport and its verify page, so the build log can link the evidence a reviewer will ask for.
The same plan, every time
The questions and limits are sealed before the first run, so a green build means the same thing in March as it did in January.
Fix loop
Find it, fix it, prove the fix.
Find
Each FAIL comes with the smallest example: who asked, what came back, and the likely cause.Fix
Change the retrieval filter, the prompt or the tool permission. The finding names the place to look.Prove
Rerun the same sealed plan and compare the two runs side by side, check by check.