Quiltt for AI agents
Quiltt provides financial data aggregation for managing connected accounts, transactions, and statements. Fintech product teams use it to build features on top of users' linked bank data. Connect it once through Arc0, and your agent, or Claude, ChatGPT and Cursor, can use it through one MCP endpoint, limited to what each user approved.
What agents do in Quiltt.
Check a profile's connections read-only
Look up a user's connected financial accounts before triggering a data sync.
Search supported institutions
Search for a bank in the supported institutions list before starting a new connection.
Delete a webhook subscription with approval
Remove a webhook subscription only after confirming it is no longer needed.
10 Quiltt actions, graded by risk.
Every Quiltt action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.
read
5Look things up. Allowed by default.
- quiltt.get_profileGet Profile
- quiltt.list_profilesList Profiles
- quiltt.search_institutionsSearch Institutions
- quiltt.list_finicity_remote_dataList Finicity Remote Data
- quiltt.list_webhook_subscriptionsList Webhook Subscriptions
write
4Create and change things. Allow, or ask the user first.
- quiltt.create_profileCreate Profile
- quiltt.update_profileUpdate Profile
- quiltt.create_webhook_subscriptionCreate Webhook Subscription
- quiltt.update_webhook_subscriptionUpdate Webhook Subscription
destructive
1Delete, cancel or archive. Ask first, or deny outright.
- quiltt.delete_webhook_subscriptionDelete Webhook Subscription
Quiltt in three steps.
- 01Your users connect QuilttThey add their Quiltt api key on Arc0 Connect, under your brand. It goes straight into the vault.
- 02You set the rulesReads run, writes like “create Profile” can wait for the user, and “delete Webhook Subscription” can be denied outright.
- 03Any agent can actYour agent calls Quiltt through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('quiltt', { read: 'allow', write: 'ask', // create_profile destructive: 'deny', // delete_webhook_subscription }) # Claude Code: the same connection, one URL $ claude mcp add --transport http arc0 \ https://mcp.arc0.ai/u/u_8f2
How Quiltt connects.
Users add their Quiltt api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.
The same Quiltt connection serves your agent over MCP and your own backend over REST and the proxy, so a user connects once. How Arc0 handles credentials →
- AUTH
- API key
- CREDENTIALS
- Per-tenant encrypted vault
- MODEL SEES
- Results only, never credentials
- AUDIT LOG
- Every call, on every plan
Use Quiltt from any agent.
Quiltt and Arc0, answered.
Can I use Quiltt with Claude, ChatGPT or Cursor?
Yes. Connect Quiltt to Arc0 once, then add your Arc0 MCP URL to Claude, ChatGPT, Cursor, Claude Code or any other remote-MCP client. Each assistant only gets the Quiltt actions you allow.
How do users connect Quiltt?
Users add their Quiltt api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.
Which Quiltt actions can my agent take?
10 in total: 5 read, 4 write and 1 destructive, such as “create Profile”. Your policies decide which of them each agent may call.
Can I stop my agent from deleting things in Quiltt?
Yes. Actions like “delete Webhook Subscription” are graded destructive. Set destructive actions to deny, or to ask so the user approves each one, and blocked calls still show up on the audit log.
Can my own backend call Quiltt too?
Yes. The same Quiltt connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug Quiltt into your agent.
Your users connect Quiltt once, under your brand. Your agent gets 10 actions behind your policies, with every call on the record.
Free to build · MCP + REST · Audit log on every plan