Not a chatbot. An operating intelligence.
Poly is the conductor of a network of domain agents — not a monolithic model. You talk to Poly; Poly dispatches to the right specialists, runs them in parallel where it can, and gives you back a single coherent answer. The output of a Poly session is finished work, not text.
Every Platform TL company, every industry surface, and every embedded product runs through the same operating intelligence. Rather than each product building its own AI stack, they inherit Poly's perception, reasoning, memory, orchestration, and action layers — and add their own domain expertise on top.
A request can begin as a voice note and end as a published listing in a CMS without ever leaving Poly's working memory. It can arrive in one language and be mediated, in real time, into another — with intent, tone, and cultural register preserved, not just literal meaning.
Underneath Poly sits a federation of five domain specialists spanning real estate, football, music, hospitality, and live events — each engineered for its vertical, each invoked through Poly, each governed by the same confirmation gates and audit trail.
This prospectus describes Poly as it ships: the four defining capabilities, the product family, the agent network, the six-layer operating system, the protocols that bind it, and the commercial model that brings it to teams and partners.
Polymath. Polyglot.
Multimodal. Agentic.
Four capabilities define what Poly is. Each is engineered into the operating system, not bolted onto a single model — and each is inherited by every agent and every embedded product.
A polymath mind
Understands every domain Platform TL operates in. Loads the right specialist agent — Aida, Jose, Kai, Pepper, Xavi — dynamically, switches context without losing memory, and unifies multi-domain outputs into a single coherent response.
Master orchestration · 5 domain agentsPolyglot by default
Detects your language automatically and replies in it. Mediates between parties speaking different languages, preserving intent, tone, and cultural register — never just literal meaning. Eleven languages at launch with cultural and tonal adaptation.
11 launch languages · real-time mediationA multimodal perception layer
Text, voice, image, video, and structured data all flow into one perception layer and are reasoned over together. Poly can watch a property walkthrough and produce a listing — one pipeline, every sense, feeding the same understanding.
Text · Voice · Image · Video · DataAn agent, not an answer
Poly doesn't just answer — it acts. It routes work to specialists, calls APIs, runs workflows, and hands off to humans when judgement is needed. Listings get published. Scouts get scheduled. Menus get translated and written to POS.
Completed work · not just textOne foundation, four forms.
From the master agent to the operating system to embedded copilots and a developer SDK — the Poly intelligence layer comes in four forms, all built on the same foundation.
Poly AI
Polymath, polyglot, multimodal, agentic — engineered to orchestrate a network of domain specialists across real estate, football, music, hospitality, and live events, through a single unified interface.
- ✓Master orchestration across five domain agents
- ✓Polyglot by default — 11 launch languages
- ✓Persistent memory across sessions and surfaces
- ✓Chat · Voice · Vision as one unified interface
Poly OS
The architecture, protocols, and runtime that let agents perceive, reason, communicate, and act together as a single coherent intelligence — the layer every Platform TL product runs on.
- ✓Six-layer architecture — Interface to Data, fully observable
- ✓OpenClaw protocols — AMP, MACP, KGSP, CCP
- ✓KMS · IMS · DMS — knowledge, intelligence, data
- ✓Skill registry + tool-invocation framework
Poly Co-pilot
Embed the full agent network — reasoning, routing, memory, action, polyglot, multimodal — directly into your application via the Poly SDK. Your brand, your voice, Poly's intelligence.
- ✓Drop-in SDK for web, mobile, and native apps
- ✓White-label — your brand, Poly's intelligence
- ✓Per-tenant agent config — pick the agents that fit
- ✓Usage-based pricing with SLAs and tenancy isolation
Poly SDK
A clean REST API and native client libraries giving developers chat, voice, vision, translation, orchestration, memory, and actions — with full token-level streaming and end-to-end tracing.
- ✓REST + native libraries — install and ship in a sprint
- ✓SSE streaming at token level for chat and voice
- ✓Webhooks for completions, confirmations, memory events
- ✓Full observability — correlation IDs, latency, attribution
Five specialists,
one conductor.
Poly is not a monolithic model — it is the conductor of a network of domain agents, each engineered for a specific vertical. When you ask Poly something, it decides which agents to dispatch, in parallel where possible, and synthesises one coherent answer.
You talk to Poly. Poly dispatches to the right agents. They work in parallel, and Poly returns one answer.
Every conversation routes through Poly, who decides which agents do what — running them concurrently where the work allows — and synthesises the result. Each agent inherits Poly's full orchestration layer, polyglot engine, multimodal perception, and persistent memory.
Aida
Valuation, listings, comps, deal structure, and multilingual buyer-side mediation across the Agentcy and Abode estate.
Lisbon → Stockholm
Jose
Scouting, player valuation, tactical analysis, transfer modelling, and dossier generation across every Inter Labs vertical.
4,218 profiles tracked
Kai
Artist coordination, release planning, fan-engagement analytics, label operations, and distribution strategy across Union and Lyve.
Pepper
Menu management, kitchen operations, inventory, ordering, and multilingual rollout across every Plates location.
Xavi
Tour logistics, ticketing, stage production, on-stage analytics, and artist coordination across every Lyve event. In beta.
works with Kai & Pepper
Every agent output is attributable, traced, and reversible. No listing is published, no offer is sent, and no client communication leaves the system without an explicit confirmation gate.
A six-layer operating system.
Every request enters the Interface layer, traverses Perception and Reasoning, is dispatched by Routing, executes through Action, and persists through Data. Every layer is observable end to end.
Interface → Perception → Reasoning → Routing → Action → Data
The protocols that bind the network.
The Agent Collaboration Interface (ACI) is the protocol family that lets Poly and the entire Platform TL agent network communicate, coordinate, share knowledge, and run scheduled work. Every agent invocation — from Poly to a domain agent — runs over OpenClaw.
Agent Messaging Protocol
The request/response protocol between agents. Messages carry the trace correlation ID, the calling agent's identity, and the user context — so every hop is attributable.
Multi-Agent Coordination Protocol
Coordinates parallel and sequential execution of multiple agents. Handles dependency tracking and integration handoff when several specialists contribute to one answer.
Knowledge Graph Sync Protocol
Keeps semantic memory in sync across the agent network. New facts propagate to the KMS and to subscribing agents automatically, so the whole network learns at once.
Cron Communication Protocol
The scheduled-execution layer. Lets agents register recurring tasks — a Monday-morning digest, a weekly watchlist refresh — without a user in the loop.
Three subsystems. One persistent mind.
Poly carries working, episodic, and semantic memory across sessions and surfaces. Beneath the conversation, three subsystems hold everything Poly knows — and every memory is editable, and every memory is deletable.
Knowledge Management System
User episodic memory, project state, prior agent outputs, and shared knowledge graphs. The canonical home of every persistent fact.
Intelligence Management System
Model embeddings, learned patterns, scoring models, classifiers, and cached results of expensive computations.
Data Management System
Raw ingested documents, uploaded media, structured records from external systems, and integration operational state.
Memory is configurable per workspace: cross-domain connections can be enabled, retention windows tuned, and a verify-before-assert mode makes Poly search before stating a remembered fact when it is in doubt.
The building blocks Poly composes into work.
Native tools are atomic capabilities. Domain skills wrap a specialist agent's expertise. Composite skills chain tools and agents into named, reusable workflows — the units of work Poly runs end to end.
Vision pipeline → domain enrichment → translation → publish. Turns a 30–90 second property walkthrough into a published, bilingual listing in the connected CMS.
Bridges two parties speaking different languages with full real-time translation, conversational memory, and a complete transcript log written to CRM.
Pulls StatsPerform data, runs comparable transfer analysis, and generates a full scout report with valuation and recommendation — using the Inter scout template by default.
Takes a source menu, applies Pepper's culinary terminology mapping, runs translation with cultural and dietary adaptation, and outputs print- and POS-ready versions per location.
AI when it can. Humans when it matters.
Poly acts — so every consequential action passes through a gate. AIAHH, Poly's AI-Human Handover, keeps a person in the loop for high-stakes decisions, and every action is logged, attributable, and reversible.
Confirmation gates & the audit trail
Every Poly output is attributable, traced, and reversible. Nothing irreversible happens silently: high-stakes actions escalate to a named human, and the safety layer defends against prompt injection from untrusted documents and third-party content.
- ✓No listing is published without an explicit confirmation gate
- ✓No offer is sent and no client message leaves the system unconfirmed
- ✓Irreversible commitments escalate to a named human for approval
- ✓Prompt-injection and credential-request attempts are detected and refused
- ✓Full audit log — agent runs, tool calls, CMS writes, escalations, refusals
The same intelligence, everywhere you work.
Chat, voice, and vision are a single unified interface. Projects, artifacts, memory, and the activity log give that interface a long-running home — on desktop and, single-thumb reachable, on the phone.
Projects
Long-running workspaces where Poly remembers everything: pinned agents, connected knowledge, open threads, and the custom instructions that shape its behaviour.
Artifacts
Every document, listing, dossier, deck, dataset, and chart Poly has produced — versioned, traceable to its conversation, and reusable across projects.
Knowledge (KMS)
Everything Poly remembers about you, your work, and your domains: episodic memories, project state, the entity graph, and live data sources.
Activity log
Every action across the workspace — agent runs, tool calls, CMS writes, AIAHH escalations, and safety refusals — queryable and complete.
Mobile runs the same operating intelligence — chat, voice, vision, agent network, and projects — in a bottom-tab pattern, polyglot by default.
Embed Poly in minutes.
The Poly SDK gives developers programmatic access to every capability via a clean REST API and native client libraries. Drop in the co-pilot component, or bring your own UI with the headless client.
# install npm install @platform-tl/poly-sdk // orchestrate across the agent network const poly = createClient({ apiKey }) await poly.orchestrate({ input: "Brief the Lisbon agency on the Príncipe Real listing", agents: ["aida"], language: "auto", stream: true })
Server-sent events
Token-level streaming for low-latency chat and voice interactions.
Event subscriptions
Receive agent completions, action confirmations, and memory-promotion events.
Tenant-scoped keys
Per-user OAuth or signed JWTs layered on top; tenancy enforced at the data layer.
Start where you are. Scale as Poly becomes the default.
Begin with the plan that fits your team and scale as Poly becomes the default interaction layer for everything you do. New workspaces receive 500 free API calls — no credit card required.
For individuals and small teams exploring Poly across one or two domains.
- ✓500 free API calls to start
- ✓Chat · core agents
- ✓Persistent memory
- ✓AIAHH human handover
For operators who live in Poly daily across multiple domains, with voice and vision.
- ✓All domain agents
- ✓Voice & vision included
- ✓REST API access
- ✓Extended memory retention
For Platform TL partners and organisations deploying Poly across their products.
- ✓99.95% uptime SLA
- ✓Dedicated infrastructure option
- ✓Customer-managed encryption keys
- ✓Audit-log export · named manager
Embed Poly into any product and pay per interaction. No minimum commit.
- ✓Full intelligence layer
- ✓White-label, per-tenant config
- ✓Automatic capability updates
- ✓Enterprise SLAs available
Each request to a Poly endpoint counts as one call; streaming responses count once regardless of token count. A message that triggers several agents in parallel is billed as a single orchestration call.
Start your workspace, connect your agents, and Poly is ready in under two minutes. One operating intelligence for every domain, every language, and every modality.