# Rong360 Open API MCP for AI Agents AI Agent Connect > Rong360 Open API brings high-level financial risk assessment and identity KYC directly to your agent. It lets your AI evaluate credit scores and verify names using China's massive financial big-data hub. You can check ID matches, carrier ownership, and generate credit profiles instantly. It's designed for fintech and security teams who need to automate background checks and fraud detection. ## Overview - **Category:** money-moves - **Price:** Free - **Endpoint:** https://edge.vinkius.com/vk_preview_WplurRFayKmGfrJZSYWVMmYubd4uO72rHs0OPRKm/ai-agent-connect - **Tags:** credit-scoring, kyc, identity-verification, risk-assessment, financial-data ## Description Connecting your AI to Rong360 means you get a direct line into a massive financial big-data hub in China. Instead of building out complex RSA algorithms or trying to scrape disparate data sources, you can let your agent handle the heavy lifting of background checks and risk profiles. When a new user signs up, your agent can pull a credit score or verify if a phone number actually belongs to the person claiming it. It handles the messy work of matching IDs to facial scans so you don't have to. This is one of the many specialized connectors available in the Vinkius catalog, making it easy to plug high-stakes financial data into your existing workflows. You get to move faster on loan approvals and fraud detection without the usual friction of manual verification. It's about giving your agent the same data that human underwriters use to make decisions, but at a speed that doesn't involve opening a dozen different browser tabs or manually typing in ID numbers from a photo. ## Tools ### check_credit_score Pull a big data credit score profile to see a user's lending history. This helps you identify defaulting behaviors before approving a loan. ### detect_face Perform a facial recognition match against a government ID. This ensures the person behind the screen is the actual owner of the account. ### validate_mobile_number Check if a mobile phone number is officially registered to a specific name. Use this to prevent scammers from using hijacked phone accounts. ### verify_identity Confirm that a national ID card matches the real name provided by the user. This automates the primary step of identity verification. ## Prompt Examples **Prompt:** ``` Check if this user is legit. Name: Zhang Wei, ID: 1101051990XXXXXXXX. ``` **Response:** ``` I've run the identity check. The name 'Zhang Wei' matches the national ID card perfectly. You're good to proceed with onboarding. ``` **Prompt:** ``` What's the credit risk for this phone number 13912345678 and ID 310115XXXX? ``` **Response:** ``` Here is the credit profile for that user: **Credit Score:** 620 **History:** No loan defaults found. **Recent Activity:** 4 micro-loan inquiries in the last 30 days. *Recommendation: Proceed with caution due to high inquiry volume.* ``` **Prompt:** ``` Can you verify the mobile number for a user named Li Na? ``` **Response:** ``` I checked the carrier registration. The number +86 138XXXXXXX888 is officially registered to 'Li Na'. This matches the user's provided information. ``` ## Capabilities ### Pull credit scores Get a detailed credit profile based on big data. ### Match faces to IDs Run facial recognition against government-issued IDs. ### Check phone ownership Confirm if a mobile number is registered to a specific person. ### Verify identities Cross-reference national ID cards with real names. ## Use Cases ### Loan Approval Bottleneck A loan officer asks the agent to check a credit score. The agent pulls the profile and flags a history of micro-loan inquiries. ### P2P Scammer Detection A user signs up for a marketplace. The agent runs validate_mobile_number and verify_identity to ensure they aren't using a fake name. ### Remote Account Verification A security team needs to verify a high-net-worth client. The agent uses detect_face to match their live photo to their ID. ### Bulk Identity Vetting A company needs to verify 500 new users. The agent processes the names and IDs through verify_identity in seconds. ## Benefits - Stop manual data entry by using verify_identity to instantly match names to national IDs. - Reduce loan defaults by pulling detailed profiles with check_credit_score to see real borrowing history. - Cut down on account fraud by using detect_face to ensure the person behind the screen matches their ID. - Verify user ownership of mobile accounts with validate_mobile_number to prevent hijacked identities. - Speed up onboarding for high-value accounts by automating the entire background check process. ## How It Works The bottom line is you get instant access to Chinese financial data for risk and identity checks. 1. Subscribe to the Rong360 Open API MCP on Vinkius. 2. Add your App ID and RSA Private Key from the Rong360 Open Platform. 3. Ask your AI client to run a check on a name, ID, or phone number. ## Frequently Asked Questions **Can the Rong360 Open API help with KYC?** Yes, it handles identity verification by matching names to national IDs and performing facial recognition against government documents. **How does Rong360 Open API handle credit scores?** It pulls big data credit profiles that show lending history, default behaviors, and recent inquiries to help you assess risk. **Can I use Rong360 Open API to verify phone numbers?** Yes, the Connector can confirm if a mobile number is officially registered to a specific person. **Is Rong360 Open API good for P2P marketplaces?** It's ideal for marketplaces because it can detect scammers by verifying carrier info and matching IDs to face scans. **Does Rong360 Open API work for fintech underwriting?** It's a core tool for underwriters to automatically process preliminary credit evaluations before a human even sees the file. **What kind of data does Rong360 Open API access?** It connects to a large financial big-data hub to provide risk assessments, credit scores, and identity verification. **How is the RSA signature handled?** Rong360 APIs typically require generating a strict base64 signature for each URL. This Connector entirely abstracts that operation. You just securely paste your pkcs8 Private Key once during setup, and the agentic execution environment automatically handles URL signing on each outgoing LLM request.