Quiltt

@Quiltt search for financial institutions using routing number 021000021 and show me what connection options are available

Found 3 institutions matching routing number 021000021: 1. JPMorgan Chase Bank, N.A. (ID: ins_chase) - Supports OAuth, credentials 2. Chase Bank USA, N.A. (ID: ins_chase_cc) - Supports credentials only 3. Chase Manhattan Bank (ID: ins_chase_legacy) - Deprecated The primary institution (JPMorgan Chase Bank, N.A.) offers both OAuth and credential-based authentication. OAuth is recommended for production use as it provides better security and user experience. Each institution ID can be used with Quiltt's connection flow to link user accounts.

This example shows Quiltt's institution search capability, which maps routing numbers to connection metadata. Useful during onboarding flows when you know a user's bank routing number but need the institution identifier for account linking. The search returns multiple matches because large banks often have separate institution records for different product lines.

@Quiltt create a new profile for user emma.chen@example.com with metadata tags for customer segment 'premium' and acquisition channel 'referral'

Created Profile successfully: Profile ID: prof_2nK8mP4xR7vQ1zLw UUID: 550e8400-e29b-41d4-a716-446655440000 Email: emma.chen@example.com Metadata: {"segment": "premium", "channel": "referral"} Created: 2024-01-15T18:32:41Z This Profile is now ready to connect financial accounts. Use the Profile ID in your Quiltt Connector session or API calls. The custom metadata fields are indexed and searchable, making it easy to segment users by acquisition channel or tier in analytics queries.

Profile creation is the entry point for every Quiltt integration—each end user needs one Profile to aggregate their financial data. The metadata field accepts arbitrary JSON, letting you store application-specific context (user tiers, cohorts, feature flags) alongside financial identity. Profiles persist across sessions and can be retrieved by ID or listed with filters.

@Quiltt list all active webhook subscriptions and check if we're already listening for profile.connection.updated events on our production endpoint

Found 4 active webhook subscriptions: 1. Sub ID: sub_9xK2mP - Events: profile.created, profile.updated → https://api.acme.com/webhooks/quiltt 2. Sub ID: sub_7nL4vQ - Events: profile.connection.updated, profile.connection.deleted → https://api.acme.com/webhooks/quiltt 3. Sub ID: sub_3pR8zM - Events: transaction.created → https://staging.acme.com/webhooks/quiltt (disabled) 4. Sub ID: sub_5tW1nK - Events: account.balance.updated → https://api.acme.com/webhooks/balance Yes, subscription sub_7nL4vQ is already configured to send profile.connection.updated events to your production endpoint. This webhook fires whenever a user's bank connection status changes (linked, error, reauth required).

Webhook management is critical for real-time financial data sync. This example demonstrates auditing your existing subscriptions to avoid duplicate registrations. Quiltt does not verify callback URLs at creation time—you must implement the endpoint and handle retries yourself. The disabled flag lets you pause subscriptions without deleting them, useful during maintenance windows.

When Quiltt wins for user-profile financial linking at scale

A 6-person fintech startup building a budgeting app needs to onboard users, link their bank accounts, and store profile metadata without building a full identity-and-connection pipeline. Quiltt is the right call here because the Create Profile and Search Institutions tools let you scaffold user records and route bank connections in one API surface, and the webhook subscription tools mean you can react to account-link events without polling. The API_KEY auth keeps setup under 20 minutes. The trade-off: if you need sub-second webhook delivery guarantees or want to own the raw Plaid/Finicity token exchange, Quiltt abstracts too much and you'll hit the ceiling fast. But for MVP-to-Series-A teams shipping a financial product in weeks, not quarters, this MCP collapses three vendor integrations into one.

When Quiltt speeds up support-ticket resolution for linked accounts

A 12-person neobank's support team fields 40 tickets a day about missing transactions or stale account balances. The Get Profile and List Finicity Remote Data tools let agents pull a customer's linked-account snapshot and Finicity sync status in one query, so they can confirm whether the issue is a sync lag or a real discrepancy. Quiltt works here because the MCP exposes read-only profile and remote-data lookups without requiring the agent to context-switch into a separate admin dashboard. The boundary: if your support flow needs to trigger a manual re-sync or edit account metadata, the current tool set stops short and you'll script those actions outside the MCP. For triage and diagnosis, though, this cuts average handle time by a third.

When Quiltt fits event-driven KYC and transaction monitoring

A 3-person compliance team at a crypto on-ramp monitors 2,000 user profiles for suspicious transaction patterns and identity-verification failures. The Create Webhook Subscription and List Webhook Subscriptions tools let them route Quiltt profile-update and account-change events into their internal case-management system without building a polling loop or maintaining a separate event bus. Quiltt is the right fit because the webhook model matches the compliance cadence—most events are low-frequency, high-stakes—and the Delete Webhook Subscription tool means they can rotate endpoints during incident response. The catch: if you need sub-minute event latency or want to replay historical events, Quiltt's webhook layer doesn't expose a replay API and delivery is best-effort. For daily-batch compliance checks and alert routing, this MCP keeps the integration under 100 lines.