canonical: https://jentic.com/apis/fleximize.com/fleximize # Fleximize Applications API The Fleximize Applications API submits and tracks business loan applications to the Fleximize SME lender. It creates an application, returns its current status by application id, and accepts supporting documents once the allowed document types are retrieved. It can link a customer's open banking data to an application to support underwriting. Calls use a JWT bearer token obtained from the token endpoint, and an is_test flag lets partners onboard without triggering credit checks. ## For AI agents Submit business loan applications, track their status, link open banking data, and upload supporting documents to the Fleximize SME lender. Authenticated with a JWT bearer token. ## Scope Does not handle loan servicing, repayments, or disbursement. Use for Fleximize business loan application submission and tracking only. ## Capabilities - Submit business loan applications with applicant and company details - Check the current status of a submitted application by its id - Link a customer's open banking data to an application for underwriting - Upload supporting documents against an application - Retrieve the allowed document types before uploading ## Use cases ### Agent-Driven Loan Submission An AI agent connected through Jentic can submit a business loan application to Fleximize without a developer wiring the token exchange and the is_test onboarding flag. The agent submits the application, reads back its status by id, and uploads the documents the lender needs. Jentic injects the bearer token at call time so the credential never reaches the agent. Example prompt: Submit a business loan application, read its status by application id, then upload the requested documents ### Open Banking Underwriting Lenders assessing an applicant can attach the applicant's open banking data to the application rather than waiting for manual statements. The agent links the open banking data to an existing application so Fleximize can run its checks. This shortens the path from application to underwriting decision. Example prompt: Link a customer's open banking data to an existing application and confirm the application status updated ### Document Collection An application often needs supporting paperwork before a decision. The agent first retrieves the allowed document types, then uploads each required document against the application id. This keeps uploads valid and the application complete. Example prompt: Fetch the allowed document types, then upload a bank statement and an ID document against the application ## Key endpoints | Method | Path | Description | | --- | --- | --- | | POST | `/application` | Submit a loan application | | GET | `/application/{application_id}` | Get an application's current status | | POST | `/application/{application_id}` | Link customer open banking data | | POST | `/application/{application_id}/upload` | Upload a supporting document | | GET | `/application/document-types` | List allowed document types | ## Key resources - **Application** — Submit a loan application and read its current status by id - **Open Banking** — Link a customer's open banking data to an application - **Documents** — Retrieve allowed document types and upload documents against an application - **Authentication** — Obtain a JWT bearer token from the token endpoint ## AI readiness This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use. - **Score:** 69 / 100 - **Maturity:** AI-Aware - **Dimensions:** - Foundational Compliance: 65 / 100 - Developer Experience & Jentic Compatibility: 70 / 100 - AI-Readiness & Agent Experience: 55 / 100 - Agent Usability: 94 / 100 - Security: 75 / 100 - AI Discoverability: 71 / 100 - **View full report:** https://jentic.com/apis/fleximize.com/fleximize/scorecard - **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/ - **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview ### Score it yourself Every API in the directory is allowlisted, so you can re-score it with no key required. - **Score your own API:** https://jentic.com/scorecard.md - **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md ```sh npx @jentic/api-scorecard-cli score ``` ## Why Jentic - **Setup:** Wiring Fleximize by hand means posting your credentials to the token endpoint for a JWT bearer token, sending it on each call, and remembering the is_test flag so onboarding leads do not trigger credit checks. Through Jentic you install once, import Fleximize from the API Directory, store the credential once, and your agent calls it. - **Permission scoping:** Fleximize puts the application id in the URL path, for example `/application/{application_id}`, so a rule can pin your agent to one application: it can read status and upload documents for that application and nothing else. You choose which operations it may call, so submitting new applications is not included unless you add it. - **Credential handling:** Your Fleximize bearer token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'submit a loan application' or 'link open banking data', and Jentic returns the matching Fleximize operation with its input schema so the agent calls the right endpoint without browsing the reference docs. ## Related APIs - **LoanPro** — Loan origination and servicing platform - **Creditas** — European lender offering consumer and business finance - **TrueLayer** — Open banking data and payment initiation across Europe - **Plaid** — Account linking and financial data for underwriting ## FAQ ### What authentication does the Fleximize Applications API use? Per its OpenAPI spec, the Fleximize Applications API uses a JWT bearer token obtained from the token endpoint, which is itself public. Through Jentic the token is stored encrypted by your own instance and injected at call time, so it never reaches the agent. ### Is there a Fleximize MCP server? You don't need an MCP server to give your agent Fleximize. Jentic connects it directly from the API Directory: import it, store your credential once, and your agent calls operations like submitting an application or uploading a document on demand, without loading another server's tool definitions into its context. ### Can I limit what my agent is allowed to do with Fleximize? Yes. Fleximize puts the application id in the URL path, so a rule can pin your agent to one application and allow only status reads and document uploads, so it cannot submit a brand-new application unless you add that operation, and every call it makes is logged. This matches a bot that chases paperwork on an existing application without opening new ones. ### Can I check an application's status with the Fleximize Applications API? Yes. Call the status operation with the application id returned when you submitted it, and the API returns the application's current status. You can poll it as the application moves through review. ### What are the rate limits for the Fleximize Applications API? The API documentation states that calls are rate-limited to 60 calls per minute. Keep bulk submissions within that ceiling, and use the is_test flag during onboarding so test applications do not trigger credit checks. ### How do I submit a loan application with the Fleximize Applications API through Jentic? Search Jentic for 'submit a loan application', which returns the application submission and status operations with their input schemas. The agent submits the application, reads its status by id, and uploads the required documents, with your stored token injected at call time. To run it on your own infrastructure, install Jentic One from its GitHub repo.