Products · n8n

One node. Every API Apiosk can find.

Describe the job in plain words. Apiosk compares the APIs that can do it, picks one, pays the provider per call and returns the result — inside the workflow you already have.

n8n → Settings → Community Nodes → Install
n8n-nodes-apiosk
Three steps

What the node does when it runs

The same discover, compare and decide the rest of the site describes — collapsed into one step of a workflow.

01

Describe the job

Type what you want in plain words, or pass a field from an earlier node. No provider to pick, no endpoint to look up.

02

Apiosk decides

It searches the live catalogue at run time, compares the APIs that can do the work, and selects one — with the reason attached.

03

It pays and returns

The node fills in the parameters, pays the provider per call from your connected wallet, and hands the response back to the workflow.

Setup

Installed and connected in about five minutes

One node and one credential. Nothing per provider, ever.

01

Install the node

In n8n: Settings → Community Nodes → Install, and enter the package name. After that, Apiosk is in the node picker.

02

Connect your account

Leave Authentication on “Connect My Account” and click connect. The buyer portal opens, you pick a wallet, fund it and set spending limits; n8n collects the credential itself.

03

Or paste a token

Switch to “Connect Token” and paste an existing one into an Apiosk API credential. Same result, for an n8n that cannot reach the portal to do the round trip.

What comes back

Two outcomes, both as data

A run either paid and answered, or it did neither and said why. Both are branchable without parsing prose.

Done

The provider answered

The response body is at json.execution.body. Alongside it: which API was selected, why, the parameters used, the price, the transaction hash and the wallet it came from.

Blocked

Nothing was paid

No API matched, required information was missing, a spending limit was reached, or the provider errored. The reason comes back as data, so the workflow can branch to a retry, a fallback or an alert.

node outputJSON
{
  "status": "done",
  "decision": {
    "api": "meridian-quotes",
    "reason": "cheapest endpoint answering FX quotes at 99.4% success over 30d",
    "price_usd": 0.004,
    "measured_latency_ms": 210
  },
  "execution": {
    "body": { "pair": "ETH/USD", "price": 3412.55, "as_of": "2026-08-17T09:14:03Z" }
  },
  "payment": {
    "wallet": "0x…a91f",
    "tx": "0x…7c02"
  }
}
The difference

What another node can't do

An HTTP node calls the API you named, with the key you pasted, at whatever it costs that day.

Choose the API at run time

An HTTP node calls the endpoint you hardcoded. This one compares what is live when the workflow runs and picks, with the reason attached to the result.

Pay without an account

No key, plan or seat per provider. Each call settles per request from a wallet you fund, inside limits the gateway enforces — the node cannot spend past them.

Refuse rather than guess

If a required value is missing, the request is blocked before payment instead of invented. Retries carry an idempotency key, so the same job settles once.

FAQ

Frequently asked questions

Do I need an account with each API?
No. That is the point of the node. One Apiosk credential reaches every API in the catalogue, and each call is paid per request — no signup, seat or plan per provider.
What does a call cost?
The provider sets a price per call and it is quoted before anything is spent. The node returns the price it paid with the result, so the workflow can log or cap it.
Does my workflow change when new APIs appear?
No. Selection happens at run time against the live catalogue, so an API listed after you built the workflow can serve it without you touching a node.
Where does the money come from?
A wallet you connect and fund in the Apiosk buyer portal, with the limits you set there. The token never appears on screen: the portal hands it to the gateway and n8n's server exchanges a one-time code for it over OAuth 2.0 with PKCE.
Can I see why an API was chosen?
Yes. The selection reason ships with the result, next to the price and the measured performance the comparison used, so a run can be audited after the fact.
Elsewhere

The same decision, other stacks

Code

All integrations

fetch, axios, Python, the hosted MCP endpoint and the gateway itself.

npm

n8n-nodes-apiosk

The package itself: MIT, Node 18 or newer, built for the n8n nodes API.

Docs

Documentation

How discovery, comparison and settlement work under every integration.

Add one node. Reach every listed API.

Agents call the comparison. Providers get into it.

Get the nodePlan a call