Validation and legacy probes
The team gateway's automated tests use local synthetic providers to check key authentication, provider/model restrictions, allowances, concurrent requests, streaming usage and credential handling. Run npm test from a checkout. They do not perform vendor authentication or billable inference.
Verify a team deployment
After adding a connection, check it from Connections, inspect GET https://jatevo.ai/v1/models with a permitted team key, and make a small request in a format the connection supports. Verify the member/key usage row, then confirm a restricted key is refused for an unpermitted model. See the API reference for request shapes and error behavior.
A saved connection is configuration rather than evidence of successful inference. A successful model-list check also does not validate streaming, tools or usage accounting. Verify those against the models and clients your team will actually use.
Legacy engine diagnostics
scripts/probe-wires.sh and scripts/smoke.mjs were written for the personal 0.1 engine topology. They assume legacy model IDs and multiple translated request formats on one connection. Their expectations do not match the default API-only team gateway, where each provider advertises specific formats.
probe-wires.sh starts a scratch sidecar on port 8721, sends requests through the legacy forwarding block and writes a report under docs/probes/. It needs the legacy engines and an appropriately configured scratch environment:
PROBE_MODEL='<legacy model id>' bash scripts/probe-wires.shNot run here: this block was not executed on the server that serves this page.
smoke.mjs exercises legacy public routes and wire formats against a running legacy instance. With a key it sends real inference requests and may consume provider allowance:
BASE=https://jatevo.ai SMOKE_KEY='<legacy key>' SMOKE_MODEL='<legacy model id>' node scripts/smoke.mjsNot run here: this block was not executed on the server that serves this page.
Read each result and the engine logs rather than treating the existence of a report as validation. These reports are not imported into the team connection catalog and do not automatically mark a provider or format verified. Do not run the legacy forwarding probe directly against a production team connection to bypass its policies.