SDKs & access methods

Zapinner is built for software and AI agents. All 79 capabilities live behind one HTTPS + JSON API, reachable four ways — every method shares the same auth, quotas, metering, and results.

The four access methods

• REST — plain HTTPS + JSON. No dependency required. API reference.
• JavaScript / TypeScript SDK — a typed client for Node and browsers. JavaScript SDK.
• Python SDK — an idiomatic client for scripts and backends. Python SDK.
• MCP — the Model Context Protocol, so AI agents can call Zapinner tools directly. MCP server.

One core, no drift

The SDKs and MCP are thin clients over the same endpoints the REST docs describe. They add ergonomics — typed methods, timeouts, and automatic retries on transient failures — but never change behavior, so a call made through any method meters and bills identically. Each method identifies itself with an X-Zapinner-Client header purely so your dashboard can show which access method drove usage.

Quickstart

JavaScript / TypeScript:

import { Zapinner } from "@zapinner/sdk"

const zap = new Zapinner({ apiKey: process.env.ZAPINNER_API_KEY })
const result = await zap.reconcile({ source_a, source_b, matching })

Python:

from zapinner import Zapinner

zap = Zapinner(api_key="zap_live_...")
result = zap.reconcile(source_a=..., source_b=..., matching=...)

Authentication

Every method uses your Zapinner API key. See Authentication for how keys work and where to create one.