wxpusher · v1

WxPusher

WxPusher. No stable public request shape is recorded, so the call is refused and no network request is sent.

Run now REST API / MCP Manifest

Sample input

Paste text in the workbench and run.

API / MCP call

curl -X POST https://toolkit.fun/api/v1/t/wxpusher \
  -H "Authorization: Bearer tk_..." \
  -H "Content-Type: application/json" \
  -d '{"input":"...","params":{}}'

MCP server: https://toolkit.fun/api/mcp

Shortest path for an agent

Read the manifest first, then call the same run contract used by the web UI. The input, output, permissions, and receipt stay consistent across REST and MCP.

Manifest: https://toolkit.fun/api/v1/registry/tools/wxpusher/manifest
REST: POST https://toolkit.fun/api/v1/t/wxpusher
MCP: https://toolkit.fun/api/mcp

Who it is for

Use this tool directly when you need WxPusher, want to chain it into a workflow, or want to expose it to an agent over REST API or MCP. This page carries the sample, call syntax, manifest, and version so search engines and generative retrieval can describe the tool accurately.

Notes

WxPusher. No stable public request shape is recorded, so the call is refused and no network request is sent.

Frequently asked questions

What does WxPusher do?

WxPusher. No stable public request shape is recorded, so the call is refused and no network request is sent.

How do I use WxPusher online?

Click “Open workbench” to open WxPusher, provide your input, and run the tool.

What input and output does WxPusher use?

Declared input type: text. Declared output type: json.