Public API + MCP + RSS + Sandbox proof

Ambassador Public Research to Proof Flow

A demo-ready AgentUI workflow that starts with a public source URL, enriches it with real PlatPhorm public surfaces, validates a generated proof packet in Sandbox, and produces markdown, CSV, schema, OpenAPI, MCP contract, provenance, and ASCII screenshot artifacts. Source URLs are input only; selected backend lanes create new draft, event, task, BrowserOps run, screenshot, OpenContent, and ASCII outputs with server-side PlatPhorm auth, and only confirmed target responses are shown as output URLs.

Template

available

Nodes

Writes

selected backend lanes

API

Fetch public source and root graph

MCP

Read tools/list from the registry

RSS

Parse AgentUI public feed context

Sandbox

Validate generated proof schema

Specs

Auto-generate selected tool specs

Docs

Create confirmed draft report

Sheets

Optional derived sheet URL

Calendar

Create review event

Kanban

Create Ambassador task set

BrowserOps

Visually verify confirmed URLs

OpenContent

Optionally ingest screenshot URL

ASCII

Convert BrowserOps screenshot

Public proof runner

Run the multi-tool chain

AgentUI fetches a public source, reads RSS context, calls MCP tools/list, reads the root graph, validates the contract with Spec, validates the proof packet with Sandbox, scores the run with Evals, and returns generated artifacts. Selected backend lanes create or verify service-owned records only with server-side env auth and confirmed target responses, while public tool intelligence can generate specs from AgentOps mappings and MCP metadata.

Toolchain profiles

one click setup

Public source URL or sheet

Network

Registry

Validation

Content

Proof

Analysis

TopicOutput mode

Optional backend lanes

Selected write lanes run only on the server with Vercel env auth. BrowserOps screenshots are preferred; if a run returns without a screenshot artifact, AgentUI can use an explicit 404 fallback proof image for OpenContent and ASCII.

Create Docs draft/reportCreate derived Sheets output (optional)Create review event in CalendarCreate Kanban task setGenerate tool/service specsRun BrowserOps visual verificationPublish BrowserOps screenshot to OpenContentConvert BrowserOps screenshot to ASCIIPost ASCII proof to Docs

Boundary

Docs, Calendar, Kanban, BrowserOps, and ASCII are selected backend lanes by default.
Tool intelligence is public-read: it checks AgentOps mappings, canonical MCP registry tools, Spec docs, service MCP metadata, and content-analysis tools without sending backend auth.
Generated specs include selected source metadata, MCP registry tools, Spec docs, and the exact selected toolchain lanes.
Sheets remains selectable, but a Sheets viewer URL is shown only after Sheets confirms it resolves.
If BrowserOps returns a run but no screenshot artifact, AgentUI labels the lane fallback_confirmed and uses a generated 404 fallback image for downstream proof.
No browser key input.
Backend tool calls use Vercel env auth when configured.
Spec, Sandbox, and Evals are required validation/scoring steps.
AgentUI only labels a lane confirmed after a target validation, URL, id, slug, run id, screenshot URL, scorecard, ASCII conversion, or reference is returned.

Run history

0 local runs

Completed runs are stored in this browser so you can compare output URLs and artifacts without rerunning the chain.

Run status

Ready for public proof

Use the default PlatPhorm source to produce a successful API + MCP + RSS + Sandbox validation chain.

ready

What this proves

AgentUI can orchestrate public API, MCP, RSS, and Sandbox validation from one human-operable interface.

Generated markdown, CSV, schemas, and contracts are deterministic and public-safe.

Backend-to-backend PlatPhorm calls can use server-side PLATPHORM_API_KEY envs without exposing browser secrets.

Selected Docs, Calendar, Kanban, BrowserOps, OpenContent, and ASCII lanes are server-side only and confirmation-gated with returned references. Sheets remains optional until its viewer confirms.

Operator reproducibility

The same flow is available as a public API endpoint and a template graph. The API route runs the confirmed public proof chain and optional backend lanes; the builder route opens the reusable graph for inspection and the run page can execute the Ambassador toolchain end to end through the server API.

Inspect in Builder

Source versus output: the sample `source_url` below identifies the public source to read. A successful default run returns new target-service references, including a Docs draft URL, Calendar event URL, Kanban task URLs, generated public tool specs, BrowserOps run URL, BrowserOps screenshot URL or explicit AgentUI fallback proof image, optional OpenContent URL, ASCII text artifact, and optional Docs-ingested ASCII URL. Sheets is selectable, but it is not treated as complete unless the Sheets viewer confirms the new record.

curl -X POST https://agentui.platphormnews.com/api/workflows/templates/ambassador-public-research-to-proof \
  -H "content-type: application/json" \
  --data '{"source_url":"https://platphormnews.com/api/network/graph","topic":"PlatPhorm public toolchain demo","output_mode":"standard","selected_steps":{"docs":true,"sheets":false,"calendar":true,"kanban":true,"browserops":true,"tool_intel":true,"opencontent":false,"ascii":true,"docs_ascii":true}}'

Capability surfaces used by AgentUI

AgentUI reads public API docs, OpenAPI, AgentOps mappings, and MCP registry surfaces to generate run-specific tool specs. Mutating lanes still execute through the owning backend services only with server-side platform auth.

Sheets API docs Sheets MCP tools Sheets OpenAPI AgentOps service map SearchOps mapping ASCII API docs ASCII MCP tools Emoji MCP tools JSON MCP tools XML MCP tools Markdown MCP tools Canonical MCP registry