prudential.com valid

Prudential Developers

Prudential developer API documentation

For agents: Prudential developer portal documenting its APIs, including an Agent Validation API for determining the distribution selling chain for a producer.

prudential apiagent validationproducer distributionapi accessdeveloper documentation

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-24T12:20:43.664Z. Cached copy · Source on prudential.com

# Prudential Developers

Prudential developer API documentation

## Documentation
- [Home](/home.md)
- [Getting Started](/getting-started.md)
- [Get Access](/get-access.md)
- [API Environments](/api-environments.md)
- [API Access](/api-access.md)
- [API Access with KONG](/api-access-with-kong.md)
- [API Design Standards](/api-design-standards.md)
- [Versioning](/versioning.md)
- [Changelog](/changelog.md)
- [Agent Validation](/can-i-sell-validation-api/agent-validation.md) - Agent Validation. <p>This API will determine the appropriate distribution selling chain for a producer looking to sell a specific product to a client.  The API request body provides various fields that can be used to identify the advisor and various fields to identify the General Agency that they are selling through and the Firm if one is involved.  It also includes request data that identifies the information key to performing the validation such as the product being sold, the state it is being sold in and the resident state of the person being insured.  Based on the distribution selling chain determined, all of the validations that need to be performed will occur and any requirements that are not in good order will be provided in the API response.</p>
- [Get product rules](/product-rules-api/get-product-rules.md) - Get product rules. <p>Get product rules based on customer information and/or productId</p>
- [Get maximum face amount for applicant](/product-rules-api/get-max-face-amount.md) - Get maximum face amount for applicant. <p>Calculate the maximum allowable coverage amount based on the applicant's age and optional household income, SSN, and policy exclusions.</p> <p><strong>Usage Scenarios:</strong></p> <ol> <li> <p><strong>Check before application is created</strong> - Call this endpoint to determine the maximum coverage amount available for an applicant:</p> <ul> <li>Required: applicant age</li> <li>Optional: annual household income, SSN (at least one must be provided)</li> <li>Do NOT include <code>excludePolicyNumber</code> for pre-application checks</li> </ul> </li> <li> <p><strong>Check before displaying requote options</strong> - Call this endpoint to validate coverage amounts during requote operations:</p> <ul> <li>Required: applicant age</li> <li>Optional: annual household income, SSN (at least one must be provided)</li> <li>Optional: <code>excludePolicyNumber</code> - should be the policy number of the current application to exclude it from the calculation</li> </ul> </li> </ol> <p><strong>Note:</strong> This endpoint applies to SILT and SIDT products.</p> 
- [Generates quotes for a given product](/quotes-api/generate-quotes.md) - Generates quotes for a given product. <p>Generate quotes for a product based on certain customer information</p>
- [Create an Application](/new-business-applications-api/create-application.md) - Create an Application. <p>Starts new business application creation process by performing product eligibity, license and validation if agent
…

Related sites

Explore similar publishers →

Similar publisher descriptions and documentation. Similarity does not imply affiliation or equivalent capabilities.

Machine-readable: GET /v1/resolve?q=prudential.com · GET /v1/domain/prudential.com · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for prudential.com:
1. POST https://agentwebmap.com/v1/sites/prudential.com/claims and keep claim_id and claim_secret private.
2. Publish the proof: add the line "AgentWebMap ownership: <token>" (token from step 1) to https://prudential.com/llms.txt, or use the DNS, meta-tag or well-known method the response describes.
3. POST https://agentwebmap.com/v1/sites/prudential.com/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/prudential.com).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.