JUST SHIPPEDRuntime 2.4 — a clearer view of every agent

Connect your stack

Less glue code.
More useful connections.

Bring your models, data, and operational tools together through a consistent integration boundary.

9 results

MODELS

Model gateway

Route requests to your preferred inference endpoints with one consistent contract.

See the connection model
INFRASTRUCTURE

Telemetry export

Send structured traces to the observability destination your team already uses.

See the connection model

Generic integration categories, not claims of working connectors or third-party partnerships.

01One clear interface

Keep the connection.
Replace the implementation.

Separate a tool’s purpose from the service behind it. Keep input validation, credentials, timeouts, and permissions explicit.

  • Describe what a tool accepts and returns.
  • Keep secrets outside the workflow definition.
  • Validate responses before passing them to an agent.
Read the integration guide
JavaScript / tool contract
const tool = {
  name: "lookup_document",
  input: { documentId: "string" },
  output: { title: "string", body: "string" },
  connection: "workspace-knowledge",
  permission: "documents:read",
  timeoutMs: 3000,
  retry: { attempts: 2, backoffMs: 250 }
};

// Sample definition, not a live connector.

From first request to production

Keep your stack.
Connect the context.

Make the existing pieces easier to operate together.

CONTROL / CONNECT / SHIP