Skip to content
FRAYTLINE

Developers

Build on the graph,
not around it.

Connectors speak canonical commands and events through provider adapters — never writing directly to UI models. Everything inbound is authenticated, authorized, validated, idempotent, tenant-scoped and traceable.

API

Typed events in. Receipts out.

Every write is a typed command or event proposal. Policy decides whether it auto-commits, needs review, or is quarantined — and only the action service performs canonical commits. Duplicate deliveries are absorbed by idempotency keys and semantic detection.

  • Versioned, policy-filtered schemas — you can't receive a field your credential can't see.
  • Webhooks with signed payloads, retries and replay protection.
  • Connector outages degrade independently — queue, retry, reconcile, manual fallback.
  • Storage, map, channel, model and telematics providers are replaceable adapters.

report a driver position — any channel, same semantics

http
POST /v1/movements/FL-204/events
Idempotency-Key: evt_9f27c1

{
  "type": "position.reported",
  "occurred_at": "2026-07-17T13:42:00+02:00",
  "source": {
    "channel": "whatsapp",
    "identity": "driver:t.haufiku",
    "verified": true
  },
  "truth_state": "reported",
  "payload": {
    "place_text": "40 km before Katima Mulilo",
    "resolved_place": null
  }
}

201 Created
{
  "event_id": "evt_9f27c1",
  "committed": true,
  "movement": "FL-204",
  "policy": "auto_commit.position_report",
  "receipt": "rcpt_88f2"
}

Connectors

Channels and systems, adapted — never hard-wired.

Messaging

WhatsApp · Telegram · email · SMS

Semantic actions — report arrival, upload POD, confirm handoff — defined once, rendered per channel capability.

Telematics

Position, geofence, sensor feeds

Observed truth with provider lineage; provider IDs never become canonical freight identifiers.

Storage

S3 · Azure · GCS · Drive · SharePoint · Box

Customer-owned originals; Fraytline keeps metadata, checksums and permission-scoped indexes.

Finance

Accounting and settlement systems

Reconciled identifiers and statuses — the connector is never the system of record.

MCP & external agents

Your AI can use Fraytline. It can't bypass it.

External AI clients connect through scoped MCP and API credentials and get exactly what a human with the same scope would: permission-filtered tools, typed action proposals, policy gates and evidence receipts. Every non-human action records the initiating principal, delegated authority and purpose.

Scoped credential · example

clientcustomer-ops-assistant
toolsmovements.read · milestones.read · ask
scopeobjects shared to Collaboration Room R-118
actionspropose only — human approval required
expiry2026-09-30 · revocable

An external agent cannot retrieve, summarize or cite anything its credential could not open directly.

The demo speaks the same language.

Try Ask Fraytline