Integration field noteExisting system → agent edge02 / 12

Your systems do not need an AI rewrite.
They need an agent edge.

Put a narrow Pilot adapter beside the software you already trust. Agents gain identity and reachability while the database, service, webhook, or legacy protocol keeps its existing contract.

Systems you keep
01PostgreSQL
02Internal HTTP
03UDP service
04Webhook
Smallest viable seam
Pilot agent edgeSDK · socket · gateway · webhook
Agent-facing result
Reachable capabilityinventory.lookuptrusted · typed · observable
Integration pathfinder

Find the narrowest
integration seam.

Share the first system an agent must reach. We will recommend whether to start with an SDK, local socket, compatibility gateway, webhook, or packaged app.

What you get
  1. 01Recommended integration mode
  2. 02Minimal system change
  3. 03Evaluation checklist
Start with one real workflowAbout 2 minutes

Do not include credentials, secrets, or customer data. By submitting, you agree that Pilot may use this information to respond. Privacy Policy.

Four ways in

Change the boundary.
Keep the contract.

01 / Embed

SDKs for application code

Node.js, Python, and Swift applications can address trusted Pilot peers from their existing runtime.

02 / Bridge

Loopback TCP and UDP

The gateway maps Pilot peers to local aliases so legacy network clients can communicate without learning a new wire protocol.

03 / Trigger

Webhooks with delivery controls

Agent and network events can feed existing HTTP workflows with retry and circuit-breaker behavior.

46%

of technical leaders identified integration with existing systems as an obstacle to deploying more capable agents.

Anthropic State of AI Agents 2026 ↗
Integration runbook

One seam at a time.

  1. 1

    Choose the integration seam

    Embed an SDK, call the local socket, bridge a legacy port, or subscribe a webhook.

  2. 2

    Keep the existing application contract

    Pilot handles peer identity and reachability around the application protocol.

  3. 3

    Scope the trusted endpoints

    Only approved agents become reachable through the bridge.

  4. 4

    Expand one workflow at a time

    Additional systems join the same network without redesigning the original connection.

Technical basis

Specific product surfaces.
Inspectable in the docs.

Product reviewPilot release 1.13.9Inspect documentation
  • 01Node.js, Python, and Swift SDKs
  • 02Local Unix socket API
  • 03Legacy TCP and UDP gateway
  • 04Webhook retries and circuit breaker