n8n-nodes-apiosk

n8n-nodes-apiosk

Use any x402 API from one n8n node.

Describe what you want in plain language. Apiosk finds the best available x402 endpoint for the job, fills in the required parameters, pays the provider from your connected wallet, and returns the result.

Your job → Apiosk → Result

No provider selection. No separate integrations. No API key setup for every service.

How it works

Give Apiosk a job such as:

Find the latest news about Nvidia

Or:

Get the current ETH price in USD

Or pass input from another n8n node:

{{ $json.chatInput }}

Apiosk searches the live x402 marketplace at runtime and selects an endpoint that can handle that specific request.

New x402 APIs can become available to your workflow without changing the workflow itself.

Setup

Add the Apiosk node, leave Authentication on Connect My Account, and click Connect my account on the credential. That opens the Apiosk buyer portal, where you pick a wallet, fund it and set the spending limits — and n8n collects the credential itself when you're done.

The token never appears on your screen and never travels through the browser: the portal hands it to the Apiosk gateway, and n8n's server exchanges a one-time code for it (OAuth 2.0 authorization code with PKCE).

The limits you set in the portal are the ones the gateway enforces on every call. This node cannot spend past them.

Already have a token?

Switch Authentication to Connect Token and paste it into an Apiosk API credential. Same result — useful when your n8n can't reach the portal to do the round trip, or when the token came from somewhere else.

Run a job

When the node runs, Apiosk:

• Understands your job.
• Finds matching x402 APIs.
• Selects the best option.
• Fills in the required parameters.
• Pays the provider.
• Calls the API.
• Returns the result.

Payment comes from the wallet connected to your Apiosk account.

Outputs

✅ Done

The request succeeded.

The provider response is available at:

json.execution.body

The result can also include:

• Selected API
• Selection reason
• Request parameters
• Price
• Transaction hash
• Wallet used

🚫 Blocked

The request could not be completed.

For example:

• No suitable API was found.
• Required information was missing.
• Your spending limit was reached.
• The provider returned an error.

The response explains what happened so you can route it to a fallback, retry flow, alert, or AI agent.

More providers = more API supply

The more x402 APIs available, the more jobs the network can serve.

Want to become a managed Apiosk API provider?

Go to dashboard.apiosk.com and start adding your APIs.

Safety

💳 Spending limits

Your spending limits are enforced by the Apiosk gateway, not by the n8n node.

The node cannot spend more than the limits you configure.

🔁 Retry protection

Apiosk uses an idempotency key so n8n retries do not accidentally pay twice for the same request.

🎯 No guessed required parameters

If an API requires information that is missing from your job, Apiosk blocks the request before payment instead of inventing a value.

Install

In n8n, go to:

Settings → Community Nodes → Install

Enter:

n8n-nodes-apiosk

After installation, search for Apiosk in the node picker.

Development

npm install --ignore-scripts
npm run build
npm run lint
npm run verify

Publish

npm version patch
npm publish --access public

One node. One credential. Any x402 API Apiosk can discover.