ClawsOpenClaw for PlatPhormNewsAI Integration and Testing PlatPhorm

OpenClaw gateway and toolchain test harness for PlatPhormNews.

Claws discovers MCP tools, APIs, schemas, workflows, and services, then lets humans, developers, IDEs, CLI tools, MCP clients, and future runtimes inspect, plan, validate, dry-run, trace, and hand off toolchains safely.

Runtime Truth Model
Every metric includes source and state. Unmeasured values stay degraded instead of becoming fake activity.
Model providerimplemented
Toolchains6 templates
Public tools57
Protected tools23
Public handlers11
Dry-run/schema tools39
Delegated handlers16

Protected execution, memory writes, workspace persistence, report publishing, Sandbox, BrowserOps, and Evals triggers require PLATPHORM_API_KEY.

Registered Tools
73
verified_snapshotcanonical_registry_bootstrap
Network Sites
36
verified_snapshotcanonical_registry_bootstrap
MCP Servers
4
verified_snapshotcanonical_registry_bootstrap
Connected Services
29
verified_snapshotintegration_registry
Latency
Degraded
degradednot_measured
What Claws Does

Discovers tools, schemas, services, policies, and workflows, then turns them into testable agent plans.

How Toolchains Work

Build from Start, MCP Tool, API Call, Spec Validate, Sandbox, BrowserOps, Evals, Trace, and Report nodes.

Public vs Protected Actions

Public reads and dry-runs stay open. Mutations, protected tool calls, provider credentials, and private evidence require the shared key.

Evidence and Traces

Every plan includes run id, trace id, redacted inputs, artifact links, degraded states, and a reproduction command.

Toolchain Testing Lifecycle

The main loop is validation first, execution second, evidence always. Claws can plan every step publicly, but protected actions remain queued until the operator supplies PLATPHORM_API_KEY.

1Discover service
2Inspect MCP/API contract
3Render or inspect tool schema
4Create toolchain
5Validate toolchain
6Dry-run plan
7Execute public-safe tool or prepare protected tool
8Validate output
9Run Sandbox test if needed
10Run BrowserOps UI check if needed
11Run Evals scorecard
12Record Trace
13Publish report
14Create Catalog capability
15Generate platphormctl reproduction command
MCP and API Tool Discovery
Tool schema browser, JSON-RPC examples, API mappings, and validation links.
OpenClaw Alignment
Compatible metadata and public discovery are implemented. Hosted runtime and marketplace claims are not made.
CLI / platphormctl Examples
Every toolchain plan returns a command that can reproduce the public-safe dry-run.

Integration Matrix

Configured integration records are public. Add live probes from the API when operator evidence is needed.

API Hub
Canonical API catalog and OpenAPI operation source
coredegraded
MCP Gateway
Federated MCP capability registry and JSON-RPC gateway
coredegraded
Spec
OpenAPI and schema validation for tool/API contracts
validationdegraded
Webhooks
Webhook signature, event, and delivery testing
validationdegraded
Sandbox
Safe command execution, replay, dry-run, and schema checks
runtimedegraded
AgentUI
Agent-facing UI rendering and workflow validation
runtimedegraded
Monitor
Status, uptime, and availability checks
observabilitydegraded
Evals
Eval suites, release gates, and quality scoring
validationdegraded
BrowserOps
Browser journeys, screenshots, accessibility, and route checks
validationdegraded

What can Claws safely do?

Claws is published by PlatPhorm News Network as an operator cockpit for inspectable agent plans. It can discover registered tools, validate schemas, assemble toolchains, generate deterministic dry-runs, and link evidence to traces. It does not claim a provider or tool executed when no handler ran. Public reads expose registry and planning state; workflow execution, persistence, reporting, test triggers, remediation, and administrative changes require the shared platform credential.

  • Registry-backed tools and schemas
  • Human approval for protected actions
  • Honest unavailable and degraded states

Protocol behavior follows the Model Context Protocol specification, and request correlation follows the W3C Trace Context recommendation.

Published by PlatPhorm News Network ·