Quanto

Brazilian Open Finance + payment-data aggregator. B2B SaaS focused on Brazilian fintechs needing Open Finance account aggregation + payment-initiation (Pix automático). Bacen-regulated ITP-licensed.

Reviewed: 2026-05-10

When to use Quanto

Choose if

Your B2B fintech needs both Open Finance data aggregation AND payment-initiation (Pix automático) in one ITP-licensed vendor. Quanto's combined-license positioning is the differentiator vs data-only aggregators.

Avoid if

You only need account aggregation (no payment-initiation) — a data-focused aggregator (Pluggy, Belvo, Klavi) may have richer connector coverage. Or if you're a per-user AI agent in Brazil — see /mcp/cumbuca-of-data-mcp/ for the MCP-shaped option for consumer agents.

Risk Flags

  • MEDIUM ITP licensing is Bacen-regulated; payment-initiation flows require the consumer's bank to authorize each Pix via biometric/PIN. Compliance requirements grow vs data-only aggregation (Conta de Pagamento Iniciador reporting obligations).

Pricing (Verified)

Hidden Costs

  • Payment-initiation surface (when used) bills by transaction volume — separate metering from data-aggregation.

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?