DOCSPontx Hub
Public docsv1
On this pageCredentials and safety

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.

01Discoverpontx-hub search
02Inspectpontx-hub show
03Previewpontx-hub preview
04Integratepontx-hub sdk
01

Credentials stay with the caller

Web and CLI use different local carriers, but neither persists provider credentials in Hub.

WebsitesessionStorage

API keys, OAuth tokens, and passwords stay in the current browser session.

CLI / Skillenvironment

Read from catalog-declared environment variables, never command arguments.

Account datanever

Favorites and sanitized history exclude auth objects and provider responses.

02

Preview is a fixed step

Preview resolves the real request and exposes its complete scope before sending.

Preview a request
pontx-hub <api-product> preview [controller] <endpoint-name> --parameter value

# Review: method · host · path · query · redacted headers · body
HTTP methodapproved hostresolved pathqueryredacted headersbody
03

Mutations require exact confirmation

Confirmation is bound to the normalized request; changing parameters, body, server, or Endpoint invalidates it.

1preview

Build redacted request

2user confirms

Approve the exact side effect

3call --yes

Send the unchanged request

04

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.
See how agents follow these boundaries