diff --git a/.github/pr-assets/what-tangle-is/after-desktop.png b/.github/pr-assets/what-tangle-is/after-desktop.png new file mode 100644 index 0000000..26c235e Binary files /dev/null and b/.github/pr-assets/what-tangle-is/after-desktop.png differ diff --git a/.github/pr-assets/what-tangle-is/after-mobile.png b/.github/pr-assets/what-tangle-is/after-mobile.png new file mode 100644 index 0000000..b73d5ed Binary files /dev/null and b/.github/pr-assets/what-tangle-is/after-mobile.png differ diff --git a/.github/pr-assets/what-tangle-is/before-desktop.png b/.github/pr-assets/what-tangle-is/before-desktop.png new file mode 100644 index 0000000..f85e692 Binary files /dev/null and b/.github/pr-assets/what-tangle-is/before-desktop.png differ diff --git a/.github/pr-assets/what-tangle-is/before-mobile.png b/.github/pr-assets/what-tangle-is/before-mobile.png new file mode 100644 index 0000000..e1f28ea Binary files /dev/null and b/.github/pr-assets/what-tangle-is/before-mobile.png differ diff --git a/components/LandingPage.tsx b/components/LandingPage.tsx index 27493e2..2296524 100644 --- a/components/LandingPage.tsx +++ b/components/LandingPage.tsx @@ -1,162 +1,99 @@ -import Image from "next/image"; -import { GiPlatform, GiToken } from "react-icons/gi"; -import { GrNodes } from "react-icons/gr"; -import { FiActivity } from "react-icons/fi"; -import CallToActionCard from "./CallToActionCard"; - -const getStartedCards = [ +const startingPoints = [ { - icon: , - title: "Sandbox", + name: "Sandbox", + state: "Live service", description: - "A real computer for every agent: shell, files, browser, any coding harness.", - link: "/sandbox", + "Run an agent in an isolated computer with files, a shell, and a browser.", + href: "/sandbox", }, { - icon: , - title: "Inference", - description: - "One OpenAI-compatible key. Hundreds of models, routed to a live provider on price and latency.", - link: "/gateway", + name: "Router", + state: "Live service", + description: "Route model requests through one API.", + href: "/gateway", }, { - icon: , - title: "Intelligence", + name: "Agent Builder", + state: "Hosted-assistant preview", description: - "Every run leaves a trace. See why an agent failed and what to change.", - link: "/intelligence", - }, - { - icon: , - title: "Blueprint Agent", - description: - "Describe a project and build it with an AI agent in the browser, then ship it.", - link: "/blueprint-agent/introduction", + "Planned hosted path for assistant creation and approved channels.", + href: null, }, ]; const LandingPage = () => { return ( -
-
- {/* Header and Image Row */} -
-
-

- Build, run, and{" "} - - improve agents - -

-

- Build agents in the Blueprint Agent, run them in isolated - sandboxes with one API key to every model, and improve them with - Intelligence, which traces every run and tells you what to fix. - Start on the managed cloud, or run the same services yourself on - the Tangle protocol. -

-
- -
- A visualization of the Tangle Network -
-
+
+

+ Build and run assistants on Tangle +

+

+ Tangle provides isolated sandboxes, agent runtime, model routing, + integrations, and evaluation tools. Agent Builder is becoming the hosted + path for creating an assistant and connecting approved channels. That + hosted path is in preview while Builder adopts the shared kit. +

- {/* Horizontal Line */} -
- - {/* System Overview */} -
-

- How the products connect -

-

- You build in the Blueprint Agent, agents run in isolated sandboxes, - and every run produces traces that show what happened and where to - improve. Run those services on the managed cloud, or host them - yourself on the protocol and get paid on-chain. -

-
-
- Build, run, improve loop -
-
- The loop: Blueprint Agent -> sandbox runtime -> protocol - (payments + evaluation). -
-
-
- - {/* What Runs Where */} -
-

- What runs where -

-
-
-

- Blueprint Agent -

-

- Where you describe and build projects with an AI agent. -

-
-
-

- Sandbox runtime -

-

- Where agents run. A real computer per session: shell, files, - browser, any harness. +

+

+ Choose where to start +

+
    + {startingPoints.map((point) => ( +
  • + {point.href ? ( + + {point.name} + + ) : ( + + {point.name} + + )} +

    + {point.description}

    -
-
-

- Protocol -

-

- Where services settle. Operators run Blueprints and get paid - on-chain. -

-
-
-
- - {/* Call-to-Action Cards Row */} -
-

- Start building -

-
-
- {getStartedCards.map((card, index) => ( - - ))} -
-
-
+ + {point.state} + + + ))} + + -
-
-
+

+ The hospitality preview is designed to turn a guest message into an + assigned task and bring overdue work to a person. The complete + request-to-resolution flow is still being verified with a design + partner. +

+

+ For an in-browser coding workspace, see the{" "} + + Blueprint Agent + + . To inspect agent runs and compare changes, see{" "} + + Intelligence + + . +

+ ); }; diff --git a/pages/_meta.ts b/pages/_meta.ts index 06d4cf8..8474c70 100644 --- a/pages/_meta.ts +++ b/pages/_meta.ts @@ -19,7 +19,7 @@ const meta: Meta = { type: "page", }, gateway: { - title: "Inference", + title: "Router", type: "page", }, intelligence: { diff --git a/pages/ai/index.mdx b/pages/ai/index.mdx index f2649f4..bcaeebf 100644 --- a/pages/ai/index.mdx +++ b/pages/ai/index.mdx @@ -1,22 +1,13 @@ --- title: AI -description: Build, run, and improve AI agents on Tangle. +description: Shared infrastructure for Tangle assistants and developer-built agents. --- -# AI +# Agent infrastructure -Tangle runs AI agents across the Blueprint Agent, isolated sandboxes, and one-key inference, and pays the operators who host protocol-backed services. Every run is bound by explicit policies and resource limits, and Intelligence traces each one so you can see what happened and tune prompts, policies, and tools. - -
- Build, run, improve loop -
- Build, run, improve loop: workbench -> sandbox runtime -> protocol (payments + - evaluation). -
-
+Tangle uses isolated sandboxes, model routing, integrations, and evaluation tools to run its hosted assistant preview. +Developers can use the same services for their own agents. +The managed services are live; the hospitality request-to-resolution flow is still being verified. ## Blueprint Agent @@ -42,15 +33,16 @@ Core capabilities: ## Evaluation Loop -Each run produces task and agent evaluations. You use that data in the workbench to refine prompts, policies, and workflows. +Instrumented runs can produce traces and evaluations. +Teams review that evidence before changing prompts, policies, and workflows. -## Inference Gateway +## Router -The [Tangle Gateway](/gateway) is the hosted inference routing layer. Agents and applications call one API, and the gateway applies provider policy, model selection, compliance filters, billing, and settlement rules before forwarding the request. +The [Tangle Router](/gateway) is the hosted inference routing layer. Agents and applications call one API, and the router applies provider policy, model selection, compliance filters, billing, and settlement rules before forwarding the request. Key capabilities: -- **One API, any model.** OpenAI, Anthropic, Google, Groq, and every other supported provider. +- **One API for supported models.** Check the [live model catalog](https://router.tangle.tools/v1/models) for routeable choices. - **Operator routing.** Route to registered operators when a request pins an operator path or uses SpendAuth. - **Compliance.** [Zero Data Retention](/gateway/zdr) and [no-train](/gateway/no-train) routing with verified provider agreements. - **On-chain payments.** [SpendAuth](/gateway/spend-auth) lets users pay operators directly without a credit card. diff --git a/pages/gateway/index.mdx b/pages/gateway/index.mdx index 41558c3..449dc27 100644 --- a/pages/gateway/index.mdx +++ b/pages/gateway/index.mdx @@ -1,9 +1,9 @@ --- -title: Inference +title: Router description: One OpenAI-compatible API key to every model, routed across providers and Tangle operators on price, latency, and reputation. --- -# Inference +# Router Tangle Inference is one OpenAI-compatible endpoint for every model. A single API key routes each request across provider APIs and registered Tangle operators, chosen on price, latency, and reputation. diff --git a/pages/index.mdx b/pages/index.mdx index 90d797a..6ff8109 100644 --- a/pages/index.mdx +++ b/pages/index.mdx @@ -1,6 +1,6 @@ --- title: Tangle Docs -description: Build, run, and improve AI agents on Tangle with the sandbox runtime, inference, Intelligence, and Blueprint Agent. +description: Build and run assistants on Tangle with live Sandbox and Router services and a hosted-assistant preview. --- import LandingPage from "../components/LandingPage"; diff --git a/pages/vision/introduction.mdx b/pages/vision/introduction.mdx index a01f2a1..c0cc92c 100644 --- a/pages/vision/introduction.mdx +++ b/pages/vision/introduction.mdx @@ -1,42 +1,32 @@ -# Build, run, and improve agents +# Build and run assistants on Tangle -Tangle is infrastructure for AI agents. You **build** them in the [Blueprint Agent](/blueprint-agent/introduction), **run** them in isolated [sandboxes](/infrastructure/introduction) with one API key to [every model](/gateway/getting-started), and **improve** them with [Intelligence](/intelligence), which traces every run and tells you what to fix. One account, one key, one balance across all of it. +Tangle builds hosted AI assistants for businesses, starting with hospitality. +The hospitality preview is designed to turn a guest message into an assigned task and bring overdue work to a person. +The complete request-to-resolution flow is still being verified with a design partner. -We started by building a protocol for complex services: MPC, zero-knowledge, distributed systems. That foundation maps directly to what AI agents need: isolation, coordination, and economic accountability. - -## Mission - -Give developers the infrastructure to run AI agents in production, and a loop that makes each run better than the last. - -Agents should ship with the rigor of real infrastructure: isolation by default, reviewable outcomes, and cost tied to result. - -## The problem - -Running agents in production is brittle. They execute outside any policy, results are hard to inspect, and there is no straightforward way to see why a run failed or measure whether a change helped. Teams either build all of this themselves or avoid shipping agents at all. +Developers use Tangle's [Sandbox](/sandbox), [Router](/gateway), agent runtime, integrations, and evaluation tools to build and run agents. +Agent Builder is becoming the hosted path for creating an assistant and connecting approved channels. +That hosted path is in preview while Builder adopts the shared kit. ## What exists today -- **Sandbox runtime**: isolated dev containers, one per agent, pre-loaded with any coding harness. The flagship product; everything runs here. -- **Inference**: one OpenAI-compatible API key to every model and provider. -- **Intelligence**: ingests traces from sandbox runs and inference calls, and tells you why agents fail and what to change. -- **Blueprint Agent**: describe a project and an AI agent builds it with you in an in-browser IDE. -- **Platform**: one account, `sk-tan-` API keys, and a shared USD balance that every product bills against. +- **Sandbox:** an isolated computer for an agent, with files, a shell, and browser access. +- **Router:** one API for model requests across supported providers. +- **Intelligence:** traces and comparisons that help a person inspect an agent run and evaluate a change. +- **Blueprint Agent:** an [in-browser coding workspace](/blueprint-agent/introduction) for building projects with an AI agent. +- **Platform:** one account, API keys, and a shared balance for supported services. -## Where it goes - -- **Operator network**: runtime hosting moves to registered operators, paid through on-chain settlement. -- **Improvement delivery**: today Intelligence reports what to fix; next it delivers those fixes back to the agents directly. -- **Protocol-native coordination**: payments, reliability, and service discovery move on-chain. - -Managed cloud is live today. The decentralized operator network is the trajectory, not a current claim. +The hosted assistant offer uses these shared components. +A live component does not establish that the complete hosted assistant workflow is ready. ## Who this is for -- **Developers shipping AI agents.** [Run one in a sandbox](/infrastructure/introduction). -- **Teams building products with agents.** [Start in the Blueprint Agent](/blueprint-agent/introduction). -- **Operators providing compute.** [Operator onboarding](/operators/introduction). -- **Partners evaluating the stack.** [Protocol overview](/network/overview). +- **Business operators** evaluating the hospitality assistant preview. +- **Developers** running agents in [Sandbox](/sandbox) or building a hosted assistant in Agent Builder. +- **Teams** inspecting run evidence in [Intelligence](/intelligence). -## The long term +## Where it goes -As agents take on more real work, developers need infrastructure that runs them safely and a loop that improves them with evidence. Tangle is building that: build the agent, run it under policy, trace what it did, and ship the fix. +The first acceptance proof is a real hospitality request completed from message through task assignment, follow-up, and human escalation when needed. +The protocol is a separate long-term path for operator-hosted services and on-chain settlement. +The managed Sandbox and Router services are live today. diff --git a/theme.config.tsx b/theme.config.tsx index de8aeca..cde32c2 100644 --- a/theme.config.tsx +++ b/theme.config.tsx @@ -16,8 +16,9 @@ function Head() { // Set default values for title and description const defaultTitle = "Tangle Docs"; - const tabTitle = "Tangle Docs - Autonomous Work"; - const defaultDescription = "Comprehensive documentation for Tangle Tools"; + const tabTitle = "Tangle Docs - Assistants and Developer Tools"; + const defaultDescription = + "Build assistants with Tangle's hosted preview, Sandbox, and Router."; // Get the title and description from the front matter, or use the default values const title = frontMatter.title