creditdecisionapi.com

What It Is

Credit Decision API is a credit scoring and loan approval REST API built for fintech teams. It lets developers submit applicant fields such as age, income, existing debt, requested amount, years of employment, and open credit accounts, and returns a 200–850 credit score, risk level, approval decision, approval/rejection reasons, recommended next actions, and factor breakdowns. The product is positioned as a way for teams to launch explainable loan scoring and instant approval workflows without building a decision engine from scratch.

Core Capabilities and Integration

Its core endpoints include POST /api/v1/decision, POST /api/v1/score, and GET /api/v1/usage. Authentication uses x-api-key, with support for demo key testing and real API key rotation. The documentation states rate limits of 1,000 requests per minute for the demo key and 10,000 requests per minute for production keys, with standard RateLimit headers returned. Outputs include factors such as incomeScore, debtScore, amountPressure, and debtRatio, and clearly define approval thresholds for low, medium, and high risk, making the results relatively explainable.

Pricing and Commercialization

Pricing is usage-based: the Production plan costs $0.05 per decision, with no upfront commitment. The page emphasizes that users can start for free without a credit card. One notable feature is its integration with Stripe metering: once billing is enabled, each API call can automatically record a Stripe meter event, with support for tenant-level usage tracking, a usage dashboard, and usage-based invoicing. This makes it suitable as a “first mile” solution for building credit decisioning SaaS products.

Pros and Cons

The strengths are a clear API design, a complete decision payload from a single request, and documentation covering fields, responses, rate limits, errors, and approval tiers, which lowers the integration barrier for developers. Usage-based billing is also well suited to MVPs. The limitations are also clear: there is no visible SDK, multi-language client, self-hosting option, SLA, security certification, or model validation material. The terms emphasize that outputs are estimates and should not be used as the sole basis for lending decisions; compliance responsibilities under ECOA, FCRA, GLBA, and similar regulations largely remain with the user.

Best Fit and Access from China

It is best suited for early-stage fintech products, loan pre-approval, risk-control prototypes, and credit SaaS products that need tenant-based metering and billing. For formal lending use cases, additional work is still needed around compliance review, adverse action notices, fairness controls, and data governance. The text does not disclose access conditions from China. Payments depend on Stripe, so teams in mainland China may need to further assess network access, payment feasibility, and local financial compliance requirements. Alternatives should be chosen based on local credit data, risk-control platforms, or in-house scoring models.