Safety model / preview first
See the exact request before deciding to send it.
Understand Pontx credential storage, destination restrictions, preview flow, and mutation confirmation boundaries.
pontx-hub searchpontx-hub showpontx-hub previewpontx-hub sdkCredentials stay with the caller
Web and CLI use different local carriers, but neither persists provider credentials in Hub.
API keys, OAuth tokens, and passwords stay in the current browser session.
Read from catalog-declared environment variables, never command arguments.
Favorites and sanitized history exclude auth objects and provider responses.
Preview is a fixed step
Preview resolves the real request and exposes its complete scope before sending.
pontx-hub <api-product> preview [controller] <endpoint-name> --parameter value
# Review: method · host · path · query · redacted headers · bodyMutations require exact confirmation
Confirmation is bound to the normalized request; changing parameters, body, server, or Endpoint invalidates it.
Build redacted request
Approve the exact side effect
Send the unchanged request
Only catalog-approved destinations
Callers cannot hand an arbitrary URL to the Hub proxy.
- ✓The API, Endpoint, and server combination must come from the reviewed catalog.
- ✓Private, loopback, link-local, metadata hosts, and unsafe redirects are denied.
- ✓Headers, body, timeout, and captured response size are server-limited.
- ✓Non-proxied APIs remain readable, previewable, and available for SDK/CLI code generation.