/The first thing anyone lands on at developers.fuzefront.com. It explains what the
portal is, lets an anonymous visitor browse the catalog read-only, and makes clear that
trying an endpoint requires signing in — the Playground is gated on the root-org
Developer grant, so it is shown locked rather than hidden.
Browse the OpenAPI contract of every service across FuzeFront, FuzeAgent, FuzeBI, FuzeX and the rest of the family — then exercise any endpoint in a sandbox that never touches production.
Signs in with your existing Fuze identity — no separate
account. First sign-in provisions you as a Developer on the platform root organization.
Every harvested openapi.yaml, grouped product → service → spec.
Send a real request to a sandbox target. Never to production.
Publish your repo's spec to the catalog with one CI step.
Your Developer membership, sandbox quota and keys.
See which Fuze products publish an API here — sign in to browse.
The Playground never touches production.
Every "Try it" call is brokered by devportal-service to a spec-generated mock
server, or to a sandbox URL a repo has explicitly opted into. Your real session token is never
forwarded — the proxy mints a synthetic sandbox identity scoped only to that target.
Test hooks: [data-frame='01-home-signed-out'] · [data-auth='anonymous'] ·
[data-action='sign-in'] · [data-action='browse-catalog'] ·
[data-panel='quick-links'] · [data-quick-link='playground'][data-locked='true'] ·
[data-panel='product-directory'] · [data-safety-notice='sandbox-only'].
Tokens only — no raw hex, spacing or type outside tokens.css / frame.css.