n8n
Two ways to use Parel from n8n with one API key: an MCP Client Tool node for an AI Agent, or an HTTP Request node for one fixed tool.
<!-- Generated from packages/core/src/clients.ts by npm run docs:quickstarts. Edit the client there, not this file. -->
Before you start
Create an account at app.parel.si/signup. ₹100 of welcome credit is on the balance at once; no card is asked for.
Set up n8n
Step 1. Create an API key: in the dashboard open Getting started, pick n8n, choose Use an API key and create the key there, so it is filled into these steps (or create one under API keys). It is shown once. Keep the default permissions and set a daily cap in rupees.
Step 2. Add an MCP Client Tool node to your AI Agent. Endpoint: the URL below. Server Transport: HTTP Streamable. Authentication: Bearer Auth, with a new credential whose token is the key.
https://api.parel.si/mcp
Step 3. The agent now sees every Parel tool with today's price in its description. Run the workflow once with the balance question below; a balance in rupees means the key works.
Give it the operating guide
Put this in the agent's system prompt so it reads the operating guide: the rules about money (quote first above ₹200, retry with the same idempotency key, stop on insufficient_balance) live in skill.md, and tool descriptions carry today's price.
Set up Parel: https://parel.si/skill.md
Check it works
Ask for the balance first: it is a free call, and a balance in rupees means you are connected.
Check my Parel balance.
Then try a paid call:
Using Parel, what are the latest 10 news articles about D2C brands in India? Title, source, date and link.
That runs search_news for ₹0.20; an empty result list is ₹0. Every call shows up in the dashboard's Usage page with its price.
Good to know
- One key per workflow is a good habit: revoking it stops that workflow and nothing else. Set a daily cap on it.
- An older n8n whose node shows only an SSE Endpoint cannot connect: update n8n, or use the HTTP Request route below.
For one fixed tool: HTTP Request
Add an HTTP Request node:
| Setting | Value |
|---|---|
| Method | POST |
| URL | https://api.parel.si/v1/run |
| Header | Authorization: Bearer sk_… |
| Body (JSON) | {"tool": "search_news", "input": {"q": "Infosys", "gl": "in", "hl": "en", "num": 10}} |
The response's data is the result; cost_paise is what it cost (₹0.20 for this call); class says whether it was charged. Branch on ok: false means a failed call, always ₹0, with an error code from the error table.
Add an idempotency_key to the body (for example the item id the workflow is processing) so a re-run of the workflow gets the stored answer back instead of paying twice (₹0 for an answer it already received; one that never arrived the first time is charged once). Conventions.
To check the key from an HTTP Request node, point it at https://api.parel.si/v1/balance (GET) with the same header. A JSON body with balance_paise means the key works.
Next
- Examples: a prompt for each tool and what it costs.
- Playbooks: six ready-made jobs with the tools they use and a typical run's cost.
- MCP reference: every tool n8n now sees, with inputs and results.
- Errors: every code, what you pay (₹0 in every row but one), whether to retry.
This page as Markdown: /docs/quickstart-n8n.md. Something wrong or missing: hello@parel.si.