Business Banking Account for an LLC: Required Documents, and How an AI Agent Can Handle the Entire Onboarding

Every article about opening an LLC business bank account gives you the same five-item checklist and a paragraph about credit unions versus neobanks. That’s not useful if you’re building an AI-native company where the account opener might be an agent, or if you’re wiring banking directly into an automated formation workflow. The real gap is technical: what documents are actually required, what happens during KYC/KYB at the protocol level, and how an AI agent executes the onboarding.

This article covers all of it. The non-negotiable documents, the manual process with its friction points clearly labeled, and the specific setup steps that let an agent handle it instead.

What Documents an LLC Needs to Open a Business Bank Account

Six things. Every bank needs all of them, and the reasons aren’t arbitrary.

1. EIN letter from the IRS. Your Employer Identification Number is the LLC’s federal tax identity, the business equivalent of an SSN. Apply at IRS.gov through the EIN Assistant; it takes about 15 minutes, and the confirmation letter arrives as a PDF immediately. The bank needs this to associate your account with a federal tax ID that belongs to the entity, not just you personally.
2. Articles of Organization. The state-approved document that legally creates your LLC. Download the stamped copy from the portal where you filed: Delaware Division of Corporations, California Secretary of State, Wyoming SOS, and so on. Delaware and Texas call it a Certificate of Formation; California calls it Articles of Organization. Whatever the name, it’s the same document that proves that the state recognizes your entity’s existence.
3. Operating Agreement. This internal document specifies ownership percentages, management structure, and, critically for the bank, who has signatory authority. Some states don’t legally require one for single-member LLCs; California explicitly doesn’t mandate it. That said, Meow requires it as a mandatory upload because it’s the document that establishes who is authorized to open accounts on the entity’s behalf. If you used a formation service like Stripe Atlas, Northwest Registered Agent, or LegalZoom, they generated one automatically. If you filed directly on a state portal, you’ll need to create one.
4. Government-issued photo ID for each authorized signer. Passport or driver’s license. This feeds into the KYC process. The bank needs to verify that the humans controlling the account are who they say they are.
5. Business email address. The address used to complete account verification. In an agentic flow, this is the email the agent controls.
6. Beneficial owner information. Under the Bank Secrecy Act’s Customer Due Diligence rule, covered financial institutions are required to identify and verify anyone who owns or controls 25% or more of a legal entity customer. For each beneficial owner, you need the full name, email address, title or role, and ownership percentage. For a solo LLC, that’s you and only you. For a three-founder company at 40/35/25, all three founders cross the threshold, and all three need separate declarations.

Two edge cases worth knowing before you start:

1. Single-member LLCs are disregarded entities for federal tax purposes by default, meaning income flows through to your personal return unless you’ve elected S-corp or C-corp taxation, in which case your EIN is even more essential. The LLC still gets its own EIN for banking, payroll, and business purposes. Don’t skip the EIN application because you think your personal SSN covers it.
2. If your LLC is owned by another LLC, the bank will ask you to trace beneficial ownership up through the chain to natural persons. Layered holding structures add a step; plan accordingly.

The Manual Onboarding Flow

Here’s the realistic sequence, including where it actually takes time.

1. Step one: get your EIN. IRS.gov, EIN Assistant, roughly 15 minutes. One note: the IRS expects you to form your entity with your state before applying for an EIN. Apply immediately after formation, and you’ll likely be fine, but don’t reverse the sequence.
2. Step two: download your Articles of Organization from the state portal. Most portals provide a free download; some charge $5-10 for a certified copy. Either usually works for banking purposes.
3. Step three: locate or draft your Operating Agreement. Formation services generate these automatically. If you filed DIY on a state portal, you’ll need to create one — free templates are widely available, but make sure yours lists ownership percentages explicitly.
4. Step four: collect photo ID for each authorized signer.
5. Step five: fill out the application. You’ll enter business name, EIN, registered address, business type, and expected monthly transaction volume, upload your documents, and then complete the beneficial ownership declaration separately for each qualifying owner.

Here’s where the friction lives: you’re re-entering information that already exists in your documents. The EIN is in the IRS letter. The ownership percentages are in the Operating Agreement. The signer’s name and address are in the Articles. You’re typing all of it into form fields by hand. If there’s any discrepancy, validation errors slow everything down. The beneficial ownership section trips up most first-time applicants because they often assume the primary account opener is the only person who needs to be declared.

This is where an agent-driven flow starts to matter, because it can extract the data from the source documents, sequence the form submissions, and complete the application without re-keying anything. Meow is built for this: a fintech platform where banking services are provided by Cross River Bank and Grasshopper Bank, N.A., both FDIC-insured, and where AI agents are first-class account operators, not a bolt-on integration.

Agentic Onboarding Architecture: How MCP Makes This Work

Model Context Protocol (MCP) is a client-server architecture where your AI host, such as Claude Code, ChatGPT, Cursor’s AI layer, VS Code with Copilot, etc., connects to an MCP server that exposes typed, callable tools over JSON-RPC. You give the agent a natural language instruction; the client translates it into a tool call; the server executes against the target system. The agent isn’t polling a webhook. It has its own session, its own credentials, and direct access to server-side functions.

Meow’s specific onboarding sequence works like this:

1. Step 1: Account creation. The agent signs up using a business email address. Meow sends a verification passcode to that email. Because the agent has access to the inbox — you’ve granted it that access as part of your setup — it retrieves the passcode and completes email verification without human input.
2. Step 2: KYC/KYB. This is the one step that requires a human, by design, not by limitation. The agent dispatches a Plaid identity verification link to the human beneficial owner via text or email. The human opens Plaid’s secure flow, enters their SSN, photographs their driver’s license, and takes a selfie. Plaid handles all identity verification. Plaid sends a confirmation back to Meow once identity verification clears; the agent can run a status check through Meow’s MCP once KYC is complete. The SSN, license image, and biometric data never touch the LLM provider. Plaid holds that data, and it stays there.
3. Step 3: API key issuance. Once KYC/KYB clears, Meow issues the agent a scoped API key with default permissions: read access and request-to-spend.

Setting Up Meow’s MCP Server

Prerequisites: a Meow account (new or existing), a supported MCP client, and if you’re on Claude Code in an enterprise environment, network egress enabled under “Allow network egress to All domains” in settings. Individual developers running Claude Code locally don’t need to touch that setting.

Claude Code

For a new Meow account:

1claude mcp add --transport http meow https://mcp.meow.com/cli

Then authenticate:

1claude /mcp

For an existing Meow account (OAuth):

1claude mcp add --transport http meow https://mcp.meow.com

Cursor

New account — add to ~/.cursor/mcp.json:

1{2  "mcpServers": {3    "meow": {4      "url": "https://mcp.meow.com/cli"5    }6  }7}

Existing account: use https://mcp.meow.com in place of the /cli URL and authenticate via OAuth when prompted.

VS Code

New account — add to .vscode/mcp.json in your workspace:

1{2  "servers": {3    "meow": {4      "type": "http",5      "url": "https://mcp.meow.com/cli"6    }7  }8}

Existing account: swap in https://mcp.meow.com with OAuth.

ChatGPT

Requires a Plus, Pro, Business, Enterprise, or Education account. Full MCP support, including write operations, is currently in beta for Business, Enterprise, and Education plans only, and requires an admin to enable Developer Mode. Plus and Pro users can connect to MCP servers, but with more limited action capabilities. Note also that ChatGPT cannot connect to localhost MCP servers; the Meow endpoint is remote, so this doesn’t affect this setup.

One more step that matters: Open meow.com/skills.md and paste its contents into your agent’s system prompt — or add it to CLAUDE.md if you’re using Claude Code. Meow publishes this structured instructions file to teach LLMs how to interact with its MCP server. It’s the difference between the agent knowing the tools exist and knowing how to sequence them correctly across the onboarding flow.

The Permission Model

The default-scoped API key gives the agent two capabilities: read and request-to-spend. The distinction is not cosmetic.

1. Read-only means the agent can check balances, pull transaction history, and view statements. Nothing moves.
2. Request-to-spend means the agent can prepare transactions (ACH transfers, wires, card spend requests), but each one enters a pending state. You receive a notification and approve or reject in the Meow dashboard. The transaction executes only after your approval. This isn’t a prompt-level guardrail a crafted instruction could override; it’s enforced at the API key permission layer. The agent cannot execute a wire; it doesn’t have the permission level to execute, regardless of what it’s told.
3. Full autonomy is available but strictly opt-in; only for users who explicitly accept the associated risks. Under this scope, the agent executes transactions without the approval step.

Prompt injection deserves a direct mention here. Financial transactions are high-value targets. If an agent is parsing invoice emails or receipts to prepare payment requests, a maliciously crafted document could attempt to redirect a transaction. The permission model is the primary mitigation: the enforced boundary at the API layer caps the blast radius of a successful injection at what the key can do. Read-only keys can’t move money, period. Request-to-spend keys require your explicit approval before anything executes. Meow is also SOC 2 compliant, so audit logs are available, and every transaction is traceable.

On the data side: PII from the Plaid KYC flow (SSN, driver’s license image, biometric selfie) is stored with Plaid and never exposed to the LLM provider. That eliminates a separate class of data exfiltration risk that would otherwise require careful handling in your agent’s context window.

For multi-agent architectures, each agent gets its own independently scoped API key on the same account. Your contractor-payment agent and your invoicing agent carry different permission levels and operate independently. Revoke a key from the Meow dashboard, and access cuts off immediately — no waiting period, no graceful shutdown cycle to manage.

What the Agent Can Operate After Onboarding

Here is the full post-setup capability set, split by permission scope.

Default (read + request-to-spend) — pending human approval for spend:

• Check balances and pull transaction history
• Prepare fee-free domestic ACH transfers
• Prepare domestic and international wire transfers
• Submit corporate card spend requests
• Send invoices and track payment status
• Handle FX payments (stablecoin and traditional FX)
• Reconcile books and flag discrepancies
• Issue virtual or physical cards with custom spend controls
• Create scheduled and recurring payments
• Manage treasury accounts

Full autonomy (opt-in only) — all of the above without the approval step.

The “one-prompt business” sequence looks like this in practice: LLC formation → Meow account opening → fund the account → issue a card → start operating. An agent handles every step except the Plaid KYC verification, which requires the human beneficial owner to open a link, enter their SSN, and complete the selfie capture. That step takes roughly five minutes. Everything else runs unattended.

Do It Now: Run the Command

If you already have a Meow account:

1claude mcp add --transport http meow https://mcp.meow.com2claude /mcp

You’re then connected, and the agent has the context and tools it needs to sequence operations correctly.

If you don’t have a Meow account yet: go to meow.com, sign up with a business email, and have your EIN letter and Articles of Organization ready. The onboarding flow walks through the rest. Or, hand it to your agent once the MCP connection is live using the /cli endpoint.

Final Thoughts

The document checklist is the easy part. EIN, Articles of Organization, Operating Agreement, photo ID, beneficial owner declarations — you can gather all of that in an afternoon. The harder question is architectural: how do you wire banking into an automated formation flow without rebuilding the compliance layer from scratch?

Meow’s MCP server answers that with a specific protocol, three clearly defined permission levels, and a Plaid integration that keeps human identity verification entirely out of the LLM’s hands. The agent does the work. The human confirms their identity once. The account is open.

Open your LLC’s business bank account on Meow and connect your AI agent in minutes. Get started → meow.com