Pluggy

Brazilian Open Finance + bank-data aggregator. B2B SaaS for fintechs needing multi-bank account aggregation, transaction feeds, and bill data via Bacen-regulated Open Finance + scraping for non-OF data.

Reviewed: 2026-05-10

When to use Pluggy

Choose if

You're building a B2B fintech / lending / credit-score / personal-finance product and need multi-bank account aggregation in Brazil — many connectors, one SDK, contract-grade SLAs. Pluggy is one of the established BR aggregators with a sandbox you can probe before signing.

Avoid if

You're a per-user AI agent that just needs one user's bank data accessible in-loop (not a B2B aggregator pattern) — for that, see /mcp/cumbuca-of-data-mcp/ which exposes Open Finance via MCP for one-click agent install. Or if your need is single-CNPJ business data (not bank transactions) — use /data/auxiliar-cnpj-fetch/ instead.

Risk Flags

  • MEDIUM Brazilian Open Finance regulation requires the consumer's bank to authorize the data share via biometric/PIN on the bank's own UI. Pluggy proxies the authorization flow; non-OF connectors (where present) use legacy auth patterns subject to changes by the upstream bank.
  • LOW Pluggy's connector library is proprietary — migrating away to a different aggregator means rewiring against a different SDK surface, not just changing API keys.

Pricing (Verified)

Hidden Costs

  • Pricing structure (per-connection / per-call / per-MAU) varies by contract; non-public list pricing.
  • Non-OF data sources (legacy scraping) bill separately from OF channels.

Use this data in your workflow

Claude Code / Cursor

claude mcp add auxiliar -- npx auxiliar-mcp

Get recommendations, pricing, and risks directly in your IDE.

Terminal

npx auxiliar

Chat with an AI agent that knows every service we review.

Was this review helpful?