canonical: https://jentic.com/apis/cloudprovenir.com/cloudprovenir # Cloudprovenir B2B The Provenir B2B Credit Decision API submits a business applicant to a hosted decisioning service and returns an automated credit decision in a single request. The applicant and business data travel as one payload to a tenant-specific host, and the response carries the decision produced by the configured Provenir rules. It is a focused decisioning endpoint rather than a full lending platform, so a workflow can call it at the point of application and branch on the outcome. ## For AI agents Submit a business applicant payload and receive an automated B2B credit decision from the configured Provenir rules in a single synchronous call. ## Scope Does not handle payment collection, invoicing, or consumer credit scoring. Use for submitting B2B credit applications to the Provenir decision service only. ## Capabilities - Submit a business credit application and receive an automated credit decision - Request a credit decision synchronously so a workflow can branch on the result immediately - Send applicant and business data as a single payload to the configured decision service ## Use cases ### Agent-Submitted Credit Decisions Through Jentic An AI agent handling B2B onboarding can request a credit decision through Jentic instead of integrating the decisioning host by hand. The agent assembles the applicant payload, calls the single decision operation, and reads the returned decision to gate the next onboarding step. Because there is one operation, the agent's reach is easy to bound. Example prompt: Assemble a business applicant payload, submit it to the credit decision operation, and read the returned decision ### Automated B2B Onboarding Credit Check During business onboarding, a service can submit the applicant's details and receive a credit decision without operating its own rules engine. The decision reflects the configured Provenir ruleset, so onboarding can approve, decline, or escalate an applicant based on a consistent policy. Example prompt: Submit a new business applicant during onboarding and route it to approval or manual review based on the decision ### Synchronous Decisioning in an Approval Workflow An approval workflow that needs a credit call inline can post the application and act on the decision in the same step. The synchronous response means the workflow does not poll or wait on a callback before continuing. Example prompt: Post a credit application inside an approval step and continue the workflow on the returned decision without polling ## Key resources - **B2B Credit Decision** — Submit a business applicant payload and receive an automated credit decision from the configured Provenir rules ## 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:** 0 / 100 - **Maturity:** Non-Ready - **Dimensions:** - Foundational Compliance: 100 / 100 - Developer Experience & Jentic Compatibility: 75 / 100 - AI-Readiness & Agent Experience: 34 / 100 - Agent Usability: 94 / 100 - Security: 10 / 100 - AI Discoverability: 0 / 100 - **View full report:** https://jentic.com/apis/cloudprovenir.com/cloudprovenir/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 this API by hand means supplying HTTP basic credentials and posting the full applicant payload to a tenant-specific host. Through Jentic you install once, import the Provenir B2B decision service from the API Directory, store the credentials once, and your agent calls it. - **Permission scoping:** This API exposes a single credit decision operation and carries the applicant data in the request body, so a rule bounds whether your agent may call that operation at all, not which applicant it decides on. Limit the agent to the decision operation and it cannot reach any other service through the same binding. - **Credential handling:** Your Provenir basic-auth credentials are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as get a B2B credit decision, and Jentic returns the Provenir decision operation with its input schema so the agent sends the applicant payload without reading the reference docs. ## Related APIs - **Experian** — A credit bureau API offering business and consumer credit data and risk scoring. - **Plaid** — Pulls an applicant's bank account and transaction data to feed a credit decision. - **TrueLayer** — Open banking data and payments that can supply applicant financials ahead of a decision. ## FAQ ### What authentication does the B2B credit decision API use? The API uses HTTP basic authentication, per its OpenAPI spec: you pass a username and password with each request. Through Jentic the credentials are stored encrypted by your own Jentic One instance and injected at call time, so they never reach the agent's context. ### Can I get an automated credit decision with this API? Yes. The decision operation accepts a business applicant payload and returns the decision produced by the configured Provenir rules, so a workflow can submit an application and branch on the result in one call. ### How do I get a credit decision with this API through Jentic? Install Jentic One, then import the Provenir B2B decision service from the API Directory and store your basic-auth credentials once. Your agent searches by intent such as get a B2B credit decision, and Jentic returns the decision operation with its input schema so the agent sends the applicant payload and reads the decision back. To run it on your own infrastructure, install Jentic One from its GitHub repo. ### Is there an MCP server for the B2B credit decision API? You don't need an MCP server to give your agent this API. Jentic connects it directly from the API Directory: import it, store your credentials once, and your agent calls the credit decision operation when it needs a decision. The operation is discovered on demand, so it does not sit in the agent's context until used. ### Can I limit what my agent is allowed to do with the B2B credit decision API? Yes. The API exposes a single credit decision operation, so a rule that allows that operation lets your agent request decisions and reach nothing else through the same credential. Every call it makes is logged.