# Serasa Experian PowerCurve Decision Engine AI Agent Connect > Serasa Experian PowerCurve is a decision engine that scores credit proposals against specific lender policies. It returns instant verdicts, scores, and policy outcomes. This MCP handles the heavy lifting of authentication by managing JWT tokens and refreshing them automatically, allowing your AI client to focus on reasoning through the results instead of parsing raw data blocks. ## Overview - **Category:** finance - **Price:** Free - **Endpoint:** https://edge.vinkius.com/vk_preview_muijGGoTR55LyKQmKEwTD7fRxxmKdpJqMwNxM8ex/ai-agent-connect - **Tags:** serasa, experian, powercurve, credit-decision, decision-engine, brazil, fintech ## Description You can use this MCP to bridge the gap between your AI agent and the Serasa Experian PowerCurve decisioning system. Instead of manually checking credit scores or interpreting complex data blocks, you let your agent submit proposals and read back the final verdict. It supports standard, Fintech, and Coad flows, meaning you can handle everything from real-time digital onboarding to consortium credit within a single interface. The connector manages its own authentication, creating and caching JWTs from your credentials so you don't have to worry about session timeouts. When a proposal is submitted, the response provides the verdict, scores, ratings, and Serasa enrichment data in a format your agent can actually use to make decisions. This turns a complex underwriting step into a simple conversation between your agent and the decision engine. ## Tools ### get_proposal_status Check the current status of a submitted proposal. Use this to poll asynchronous requests or resync after a timeout. ### reprocess_proposal Re-run a decision flow on an existing proposal. This is useful if you need to re-evaluate a 'refer' decision after updating data or changing policies. ### submit_coad_proposal Submit a credit proposal specifically for the Coad flow, such as co-advised or consortium credit. ### submit_fintech_proposal Submit a proposal through the Fintech flow, which is optimized for real-time digital onboarding. ### submit_proposal Submit a standard credit proposal to PowerCurve to receive an automated approve, deny, or refer verdict. ## Prompt Examples **Prompt:** ``` Decide this loan request: proposal P-1024, service SVC-EMP, applicant João Silva, CPF 12345678901, born 1985-03-10, requesting BRL 5000 over 12 months. ``` **Response:** ``` The agent calls submit_proposal with the provided applicant and product details. It returns the verdict, the credit score, and the Serasa enrichment data. ``` **Prompt:** ``` Check where application APP-7731 stands and re-run the decision if it is stale. ``` **Response:** ``` The agent uses get_proposal_status to check the current state of APP-7731, then calls reprocess_proposal to trigger a new decision flow. ``` **Prompt:** ``` Submit this to the Fintech flow and also capture the Bacen database the policy consumed. ``` **Response:** ``` The agent calls submit_fintech_proposal and includes the Bacen data within the extra_data JSON object to ensure the policy consumes it. ``` ## Capabilities ### Automated Decisioning Your agent submits proposals and receives instant approve, deny, or refer verdicts. ### Automated Authentication The MCP manages JWT creation and transparently refreshes tokens for you. ### Data Enrichment The agent receives scores, ratings, and Serasa enrichment data alongside the decision. ### Status Monitoring Your agent can poll the status of asynchronous proposals to check for updates. ### Decision Reprocessing You can trigger a re-evaluation of existing proposals when data or policies change. ## Use Cases ### Real-time Digital Onboarding Use the Fintech flow to get instant credit decisions during a customer's mobile signup process. ### Consortium Credit Management Submit co-advised credit requests using the Coad flow for specialized credit products. ### Policy Re-evaluation Reprocess a previously 'referred' application after updating the customer's income or credit data. ### Asynchronous Status Tracking Have your agent monitor the status of long-running credit applications until a final decision is reached. ## Benefits - Eliminates manual parsing of raw DV blocks by providing structured decision data. - Handles all JWT authentication and token refreshing in the background. - Supports multiple credit flows including Fintech and Coad through a single interface. - Reduces latency in the underwriting process by automating the submission and polling steps. ## How It Works Connecting to PowerCurve via this MCP is a direct process that moves from credentials to decisions. 1. Connect your AI client to the Vinkius-hosted MCP. 2. Provide your Serasa Experian credentials for authentication. 3. The MCP automatically generates and manages your JWT session. 4. Your agent calls the appropriate submission tool for your specific credit flow. 5. The agent receives a structured response containing the verdict and enrichment data. ## Frequently Asked Questions **How does the MCP handle authentication?** The MCP takes your username and password to mint its own JWT. It then caches this token and refreshes it automatically so your session stays active. **Can I use this for real-time digital onboarding?** Yes, you can use the submit_fintech_proposal tool, which is specifically optimized for real-time digital onboarding flows. **What happens if a decision is 'referred'?** If a proposal returns a refer verdict, you can use the reprocess_proposal tool to re-run the decision after you have corrected the input data or updated policies. **Does the agent have to parse raw data?** No. The MCP renders responses as verdicts, scores, ratings, and summaries, allowing your agent to reason about the outcome without reading raw data blocks. **Which credit flows are supported?** The MCP supports standard flows, Fintech flows for digital onboarding, and Coad flows for co-advised or consortium credit. **Which flow should I submit a proposal to?** submit_proposal is the standard screenless flow. submit_fintech_proposal is the Fintech variant and submit_coad_proposal adds the Coad-specific blocks. If you do not know which one applies, start with submit_proposal and check the returned service id with the provider of the flow. **Why are optional applicant fields sometimes ignored?** Each flow accepts a subset of the applicant and request fields. The connector only puts a field in the body when the flow's schema declares it, so sending produto or prazo to a flow that does not use them is a no-op rather than an error. Use extra_data to set any other DV-* block exactly as PowerCurve expects it. **What does a refer verdict mean?** The policy could not approve or decline automatically — a human analyst must review the case. The rendered output keeps the decision name, the recommendation codes and the Serasa enrichment so the analyst has the reasons in one place. Call reprocess_proposal after the review to re-run the decision.