Pontx Hub
Use pontx-hub as the authoritative interface to the curated API catalog. Keep
API metadata out of long-lived context by searching and loading only the
product, endpoint, or schema needed for the current task.
This universal Skill owns catalog-wide discovery and request safety. A
pontx-<apiSlug> product Skill adds only provider-specific integration flows,
best practices, and caveats; it does not replace the current PontxSpec.
Workflow
Search before choosing an API. Natural-language capability, request, and
response questions are supported:
pontx-hub search "<capability>" --json
pontx-hub search "创建任务的入参" --locale zh --json
pontx-hub search "返回 dueDate 的接口" --locale zh --json
Narrow the result type when useful:
pontx-hub search "<field-or-model>" --type schema --json
Inspect the selected stable resource ID:
pontx-hub show endpoint:<api>/<endpoint>
pontx-hub show schema:<api>/<schema>
When provider-specific guidance would help, check the available product
Skills. Explain the benefit and install one only when the user requests or
approves the installation:
pontx-hub skill list
pontx-hub skill install <apiSlug>
Use that product Skill for provider-specific sequencing and caveats, then
return to pontx-hub show for current Endpoint, Schema, and auth details.
For an Endpoint, build and review the exact request without sending it:
pontx-hub <api-collection> preview <api-name> --parameter value --body '<json>'
pontx-hub <api-collection> preview <controller> <api-name> --parameter value --body '<json>'
For GET or HEAD, call only when the user requested execution:
pontx-hub <api-collection> call <api-name> --parameter value
pontx-hub <api-collection> call <controller> <api-name> --parameter value
For POST, PUT, PATCH, or DELETE, show the dry-run result and obtain explicit
user confirmation. Then pass --yes without changing parameters:
pontx-hub <api-collection> call <controller> <api-name> --parameter value --body '<json>' --yes
Generate application code after the request shape is verified. Use the
package and exports reported by the Hub instead of inventing a package or
pinning a stale version:
pontx-hub sdk <api>
pnpm add @pontx/<apiSlug>
Safety
- Never infer approval for a write from a request to inspect, explain, or
preview an API.
- Never print, echo, log, or place credentials directly in command arguments.
- Read credentials from the environment variables named by
show.
- Never call an arbitrary URL or an Endpoint outside the Hub catalog.
- Never treat a product Skill as the source for Endpoint, parameter, Schema,
authentication, package-version, or server metadata; inspect the current
PontxSpec through the Hub.
- Never bypass the separate
preview step for a mutation.
- Treat a changed parameter, body, server, or Endpoint as a new request that
requires another dry-run and confirmation.
- Read references/auth-and-safety.md when
configuring credentials, diagnosing authentication, or executing a mutation.
Output
Prefer --json when consuming CLI output programmatically. Preserve the CLI
exit code and machine-readable error code when reporting failures. Use the
result's match.mode and match.fields to explain whether product, parameter,
request, response, schema, or property metadata produced the match. Use the
Endpoint's published @pontx/<apiSlug> package when generating application
code.
1---2name: pontx-hub3description: Discover, compare, inspect, preview, call, and integrate curated public APIs with Pontx Hub. Use whenever a user asks to find a public API for a task, identify which Endpoint or Schema returns a field, inspect PontxSpec or OpenAPI documentation, install provider-specific Skills, preview a request safely, confirm a mutation, or generate code with a published Pontx SDK.4---56# Pontx Hub78Use `pontx-hub` as the authoritative interface to the curated API catalog. Keep9API metadata out of long-lived context by searching and loading only the10product, endpoint, or schema needed for the current task.1112This universal Skill owns catalog-wide discovery and request safety. A13`pontx-<apiSlug>` product Skill adds only provider-specific integration flows,14best practices, and caveats; it does not replace the current PontxSpec.1516## Workflow17181. Search before choosing an API. Natural-language capability, request, and19 response questions are supported:2021 ```bash22 pontx-hub search "<capability>" --json23 pontx-hub search "创建任务的入参" --locale zh --json24 pontx-hub search "返回 dueDate 的接口" --locale zh --json25 ```2627 Narrow the result type when useful:2829 ```bash30 pontx-hub search "<field-or-model>" --type schema --json31 ```32332. Inspect the selected stable resource ID:3435 ```bash36 pontx-hub show endpoint:<api>/<endpoint>37 pontx-hub show schema:<api>/<schema>38 ```39403. When provider-specific guidance would help, check the available product41 Skills. Explain the benefit and install one only when the user requests or42 approves the installation:4344 ```bash45 pontx-hub skill list46 pontx-hub skill install <apiSlug>47 ```4849 Use that product Skill for provider-specific sequencing and caveats, then50 return to `pontx-hub show` for current Endpoint, Schema, and auth details.51524. For an Endpoint, build and review the exact request without sending it:5354 ```bash55 pontx-hub <api-collection> preview <api-name> --parameter value --body '<json>'56 pontx-hub <api-collection> preview <controller> <api-name> --parameter value --body '<json>'57 ```58595. For GET or HEAD, call only when the user requested execution:6061 ```bash62 pontx-hub <api-collection> call <api-name> --parameter value63 pontx-hub <api-collection> call <controller> <api-name> --parameter value64 ```65666. For POST, PUT, PATCH, or DELETE, show the dry-run result and obtain explicit67 user confirmation. Then pass `--yes` without changing parameters:6869 ```bash70 pontx-hub <api-collection> call <controller> <api-name> --parameter value --body '<json>' --yes71 ```72737. Generate application code after the request shape is verified. Use the74 package and exports reported by the Hub instead of inventing a package or75 pinning a stale version:7677 ```bash78 pontx-hub sdk <api>79 pnpm add @pontx/<apiSlug>80 ```8182## Safety8384- Never infer approval for a write from a request to inspect, explain, or85 preview an API.86- Never print, echo, log, or place credentials directly in command arguments.87- Read credentials from the environment variables named by `show`.88- Never call an arbitrary URL or an Endpoint outside the Hub catalog.89- Never treat a product Skill as the source for Endpoint, parameter, Schema,90 authentication, package-version, or server metadata; inspect the current91 PontxSpec through the Hub.92- Never bypass the separate `preview` step for a mutation.93- Treat a changed parameter, body, server, or Endpoint as a new request that94 requires another dry-run and confirmation.95- Read [references/auth-and-safety.md](references/auth-and-safety.md) when96 configuring credentials, diagnosing authentication, or executing a mutation.9798## Output99100Prefer `--json` when consuming CLI output programmatically. Preserve the CLI101exit code and machine-readable error code when reporting failures. Use the102result's `match.mode` and `match.fields` to explain whether product, parameter,103request, response, schema, or property metadata produced the match. Use the104Endpoint's published `@pontx/<apiSlug>` package when generating application105code.
pontjs