Frequently Asked Questions
Everything you need to know about public JSON tooling, schema registry files, local drafts, MCP, and future protected actions.
What is JSON Tree + PlatPhorm Schema Registry?
It is the public JSON utility and schema registry layer for json.platphormnews.com. Humans and agents can paste, format, minify, validate, search, explore, and download JSON while browsing public PlatPhorm schema contracts.
Is pasted JSON stored on the server?
No server persistence is claimed in Phase 1. The editor stores non-sensitive local drafts in browser IndexedDB so reloads can restore your work. Do not paste secrets or store private JSON in browser drafts.
Which schema files are real?
The public schema files under /schemas/json are bundled files served by the app, including the universal schema pack, core, realm, item, observability, and agent schemas.
Do public JSON tools require an API key?
No. Public-safe parse, format, minify, validate, stats, schema browsing, and schema validation are open by default in Phase 1. Future protected actions use PLATPHORM_API_KEY when enforcement is enabled.
What does the MCP endpoint expose?
The MCP endpoint exposes JSON-RPC 2.0 methods for public-safe JSON parsing, formatting, minification, validation, stats, schema lookup, schema pack access, JSON-LD validation, and read-only registry introspection.
How does this integrate with the wider PlatPhormNews mesh?
JSON remains the JSON utility and schema registry. Trace, Docs, Sheets, Decks, Claws, Evals, BrowserOps, Sandbox, and other services are integrations that are reported as active only when real backing behavior exists, otherwise they show degraded status.