Layer 01

Translator

Universal manifest for agent ↔ system calls.

Today, every agent vendor speaks a different dialect and every system of record expects a different payload. Translator replaces that combinatorial mess with a single declarative manifest that any agent can call, version-controlled and schema-validated before it touches production.

Book a technical deep-dive

What it is

One manifest. Every system.

—
Declarative manifests. A typed YAML or JSON file describes every operation a system exposes to agents — fields, types, auth, policy tags, and semantic metadata. The manifest is the contract.
—
Per-agent SDKs. Python and TypeScript SDKs auto-generated from the manifest. Agents call typed functions, not raw HTTP. Breaking changes surface at build time, not in production.
—
Schema-diff CI. The Translator CI action diffs manifests on every PR. If a system-of-record API changes in a way that would break an existing agent call, the build fails before deployment.
—
40+ pre-built adapters. Native adapters for SAP S/4HANA, Salesforce, Workday, ServiceNow, Snowflake, and 35+ others. Long-tail systems onboard via OpenAPI import in under 30 minutes.

How it works

From manifest to production call.

01
Author a system manifest once per target system. Version it like code.
02
The Translator runtime validates every incoming agent call against the manifest schema at request time.
03
SDKs regenerate automatically when the manifest changes — agents always call the current API surface.
04
The schema-diff CI action blocks deployments when a manifest change would silently break an existing caller.

Why it matters

The integration fabric becomes your moat.

—
No more mid-sprint breakages. Salesforce, SAP, and Workday change their APIs on their own schedule. Schema-diff CI means your agents get a warning, not a silent failure at 2 a.m.
—
Onboard any new agent in hours, not weeks. A new agent vendor calls your existing manifests on day one. The 14–18 week SAP integration is done once, shared across every agent.
—
Typed calls, not prompt strings. Agents that call typed operations against a manifest are predictable. Agents that inject raw prompts into system APIs are not. Translator enforces the former.
—
The manifest library accumulates. Every manifest you write adds to a library that compounds. 40 pre-built adapters today — your custom ones live alongside them, versioned and reusable.

Config sample

A 20-line system manifest.

system-manifest.yaml

1# system-manifest.yaml — SAP S/4HANA
2name: sap-s4hana
3version: "2.1.0"
4display: "SAP S/4HANA ERP"
5base_url: "https://api.sap.example.com/v1"
6auth:
7  type: oauth2_client_credentials
8  token_endpoint: "https://auth.sap.example.com/token"
9  scope: "api.erp.read api.erp.write"
10
11operations:
12  create_purchase_order:
13    method: POST
14    path: /purchasing/orders
15    description: "Create a new purchase order in MM"
16    required_fields:
17      - vendor_id: string
18      - line_items: array<LineItem>
19      - cost_centre: string
20    returns: PurchaseOrder
21    policy_tags:
22      - requires_approval_above: 50000
23      - jurisdiction: EU
24
25  get_vendor:
26    method: GET
27    path: /vendors/{vendor_id}
28    description: "Retrieve vendor master data"
29    returns: Vendor
30
31types:
32  LineItem:
33    material_number: string
34    quantity: number
35    unit: string
36    price: number
37    currency: string  # ISO 4217
38
39  PurchaseOrder:
40    po_number: string
41    status: enum[draft, approved, rejected]
42    created_at: datetime

Pairs with

Layer 02

Provenance & Policy

Tamper-evident evidence per action.

Layer 03

Financial Attribution

Unit economics per agent, per task.

Layer 04

MCP / A2A Spin

Protocol convergence without waiting.

Ready to eliminate your integration backlog?

A 30-minute technical call with the founding team. We'll review your current agent-to-system topology and tell you honestly what Translator can and can't solve.

Book a technical deep-dive