Interface contract · version 1

Four jobs. One engine.

Build against Connect, Process, Query, and Deliver. MCP, REST, SQL, and the workspace are transports over the same evidence and control runtime, not separate products.

01 · Connect

Bring private context in

Connect workplace systems, direct uploads, webhooks, banking data, and SEC filings. Source identity and tenant boundaries follow every object into the runtime.

MCP connect MCP sec REST connectors

Start: GET /v1/connectors · GET /v1/oauth/providers · POST /v1/webhooks/ingest

02 · Process

Turn context into cited work

Extract documents, images, and voice; reconcile packets; run complete audits; compare what was said with what was filed; and discover the process behind the evidence.

extract reconcile audit analyze_call discover_process

Start: POST /v1/parse · POST /v1/reconcile · POST /v1/batch

03 · Query

Ask across the governed runtime

Ask plain-English questions, run read-only SQL, search evidence, inspect capabilities, and mine corpus-wide patterns without creating a second analytics store.

ask query list mine_corpus

Start: POST /v1/search · POST /v1/sql/ask · POST /v1/sql/execute

04 · Deliver

Put governed results to work

Export workflow results, write structured evidence downstream, and record business outcomes so operators can connect model and token spend to accepted work.

MCP write workflow export outcomes

Start: GET /v1/workflow-runs/{run_id}/export · POST /v1/outcomes

Use the transport your team already operates.

The contract stays the same

Human operator ─────────────── Workspace
Application ───────────────── REST /v1
Agent ─────────────────────── 12 MCP verbs
Finance / data team ───────── SQL + exports
                                  │
                                  ▼
          Connect → Process → Query → Deliver
                                  │
                                  ▼
       evidence · policy · identity · token economics

Public contract

4 stable jobs · Connect · Process · Query · Deliver

MCP

12 agent verbs · implementation helpers stay internal

REST

Preferred operations · discoverable at /v1/capabilities

Compatibility

No launch breakage · existing /v1 URLs remain available

Security

Tenant-aware · API keys · OAuth · signed webhooks · private deployment

Runtime

One evidence layer · shared by workspace, agents, APIs, and analytics

Start with the interface map.

The live manifest is the source of truth for supported public operations. Existing integrations can migrate gradually.

Open manifest API docs Connections