> ## Documentation Index > Fetch the complete documentation index at: https://docs.nextlevelmca.com/llms.txt > Use this file to discover all available pages before exploring further. # Overview > What you can build on NextLevel MCA: keep your CRM and deal desk in sync, match and submit to lenders, get told the moment something happens, and let AI assistants work in your pipeline. NextLevel MCA is the deal platform your team works in every day. Everything the team does in the app, from opening a deal and matching lenders to submitting, logging offers, collecting documents and starting renewals, can also be done from your own systems, and anything that happens on a deal can be pushed to you as it happens. Whatever you build behaves like a member of your team: the same permissions, the same pipeline rules, the same protection of sensitive data. ## What you can build * **Keep your CRM and the deal desk in sync.** Create businesses, contacts and deals from your website, your dialer or your CRM, update them as they move, and read everything back: stage, offers, documents, activity. * **Match lenders automatically, with reasons.** Ask which lenders fit a deal. Each one comes back with a score, a pass or fail on every one of its criteria, and a plain-English explanation you can show a rep or a merchant. Once bank statements have been analysed, matching uses the bank-verified revenue instead of the stated figure. * **Submit to lenders.** Send a deal to any number of lenders in one go, as the same email package the app sends or, for lenders that accept applications through their API, straight into the lender's system with status and offers flowing back. * **Get told the moment something happens.** A deal was created, a lender replied, an offer came in, statements finished analysing, an advance is ready to renew: fifteen kinds of notification, delivered to your systems as they happen. * **Put AI assistants to work.** Claude, ChatGPT and other assistants can look things up, explain lender fit, chase documents, submit deals and log offers, acting as the signed-in team member with that person's permissions. * **Collect documents and run the merchant portal.** Request bank statements and other documents by email, text or link. The merchant uploads through a secure portal, the files land on the deal, and statement analysis tells you what the statements say. ## How the pieces fit ```mermaid theme={null} flowchart LR Business -->|owners and contacts| People Business -->|funding request| Deal Deal --> Documents Deal -->|sent to a lender| Submission Submission -->|lender responds| Offer Offer -->|primary offer funded| Advance Advance -.->|renewal starts a new deal| Deal ``` A **business** is the merchant. The **people** behind it are its owners and contacts, and a person can be linked to more than one business. A **deal** is one funding request for a business, and it sits in exactly one pipeline stage. Each **submission** is that deal sent to one lender, and **offers** are the terms lenders come back with; one offer is marked primary. Funding the primary offer creates an **advance**, the amount now being repaid. As the advance pays down it is flagged renewal-ready (at half paid, by default), and a **renewal** starts a new deal on the same business, linked to the one it renews. ## Workspaces Everything above belongs to one workspace: usually one brokerage or team, the same thing as a location in the app. Access is granted per workspace. An API key or an assistant connection can see and change the data of the workspace it was created in and nothing else. To connect two workspaces, create a credential in each. ## Next steps Create a key and decide what it may see and do. Create a merchant and a deal, match lenders, submit, read the offers. Get told when something happens instead of asking. Let Claude or ChatGPT work inside your pipeline. ## For developers Three surfaces share one contract, so what is true of one is true of the others: | Surface | Where | Use it for | | - | - | - | | REST API | `https://api.nextlevelmca.com/v1` | Reading and writing every object above. JSON in, JSON out, authenticated with an API key or an OAuth access token. | | Webhooks | An HTTPS endpoint you host | Signed event deliveries, subscribed to per workspace. | | MCP server | `https://mcp.nextlevelmca.com` | Tools for Claude, ChatGPT and other MCP clients, authenticated by the user signing in. | All three run the same service code with the same permission checks. Every endpoint, field and enum is in the **API reference** tab, generated from the OpenAPI spec; the guides link into it rather than repeating it. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.