> ## Documentation Index > Fetch the complete documentation index at: https://docs.rcintell.com/llms.txt > Use this file to discover all available pages before exploring further. # Validate a code pair for PTP bundling > Check whether two procedure codes are bundled under NCCI PTP edits. ## OpenAPI ````yaml /docs/openapi.client.json get /v1/ncci/validate openapi: 3.1.0 info: description: >- Client API for RCIntel. Admin ingest, catalog sync, and internal audit routes are omitted. See Guides → Which API to use. summary: Multi-tenant knowledge API for healthcare revenue cycle management. title: Healthcare Knowledge Layer version: 0.1.0 servers: [] security: [] tags: - description: >- Geographic payer policy lookup (national NCD vs MAC LCD vs state). Query payer, code, state, plan_type. Each row includes geo_scope and document_version. name: policies - description: >- Payer network directory — search payers, check prior auth requirements, view filing rules, denial patterns, and appeal levels. name: payers - description: >- Resolve healthcare billing knowledge across the L1-L6 layer stack. Includes payment calculation, billing guidance, and per-layer queries. name: knowledge - description: >- CMS Fee Schedule lookups — OPPS (Addendum B / APC), DMEPOS (state-level pricing), and Clinical Lab Fee Schedule (CLFS). name: fee-schedules - description: >- NCCI (National Correct Coding Initiative) — dedicated MUE limits, PTP bundling edits, add-on code edits, and code pair validation. name: ncci - description: >- Service code intelligence — CPT/HCPCS lookup, RVU data, NCCI edits, payment calculation, implant/GUDID search, and service group classification. name: codes - description: >- Submit asynchronous AI agent jobs for code research, medical necessity, and denial resolution. Poll for results and retrieve reasoning traces. name: agents - description: >- Register and manage healthcare facilities by CCN (Medicare Provider Number). Each facility is the root entity for knowledge resolution. name: facilities - description: >- NPI Registry — live search against CMS NPPES API for provider and organization National Provider Identifiers. name: npi - description: >- OpenFDA drug product lookup by NDC. Includes product-level fields with normalized ingredient and package detail. name: drugs - description: Health checks, service metadata, and Prometheus metrics. name: system paths: /v1/ncci/validate: get: tags: - ncci summary: Validate a code pair for PTP bundling description: Check whether two procedure codes are bundled under NCCI PTP edits. operationId: validate_pair_v1_ncci_validate_get parameters: - description: First procedure code in: query name: code1 required: true schema: description: First procedure code title: Code1 type: string - description: Second procedure code in: query name: code2 required: true schema: description: Second procedure code title: Code2 type: string - description: 'Filter by claim type: prac (professional) or hosp (institutional)' in: query name: claim_type required: false schema: anyOf: - type: string - type: 'null' description: 'Filter by claim type: prac (professional) or hosp (institutional)' title: Claim Type - description: >- Date of service (YYYY-MM-DD); selects the NCCI version active on that date. in: query name: date_of_service required: false schema: anyOf: - format: date type: string - type: 'null' description: >- Date of service (YYYY-MM-DD); selects the NCCI version active on that date. title: Date Of Service responses: '200': content: application/json: schema: $ref: '#/components/schemas/NCCIValidateResponse' description: Successful Response '422': content: application/json: schema: $ref: '#/components/schemas/HTTPValidationError' description: Validation Error security: - APIKeyHeader: [] components: schemas: NCCIValidateResponse: description: Result of PTP bundling validation between two codes. properties: additional_claim_types: anyOf: - items: $ref: '#/components/schemas/NCCIValidateClaimTypeResult' type: array - type: 'null' description: >- If multiple claim types have edits for this pair, additional results are listed here title: Additional Claim Types claim_type: anyOf: - type: string - type: 'null' description: Claim type for this result (professional/institutional) title: Claim Type code1: title: Code1 type: string code2: title: Code2 type: string col1_proc_cd: anyOf: - type: string - type: 'null' description: Column 1 (comprehensive) procedure code title: Col1 Proc Cd col2_proc_cd: anyOf: - type: string - type: 'null' description: Column 2 (component) procedure code title: Col2 Proc Cd effective_date: anyOf: - type: string - type: 'null' title: Effective Date is_bundled: description: Whether the pair has a PTP edit title: Is Bundled type: boolean modifier_allowed: anyOf: - type: boolean - type: 'null' description: Whether a modifier can bypass the bundle title: Modifier Allowed modifier_indicator: anyOf: - type: string - type: 'null' title: Modifier Indicator ptp_rationale: anyOf: - type: string - type: 'null' title: Ptp Rationale required: - code1 - code2 - is_bundled title: NCCIValidateResponse type: object HTTPValidationError: properties: detail: items: $ref: '#/components/schemas/ValidationError' title: Detail type: array title: HTTPValidationError type: object NCCIValidateClaimTypeResult: description: PTP edit result for a specific claim type. properties: claim_type: anyOf: - type: string - type: 'null' title: Claim Type modifier_allowed: anyOf: - type: boolean - type: 'null' title: Modifier Allowed modifier_indicator: anyOf: - type: string - type: 'null' title: Modifier Indicator ptp_rationale: anyOf: - type: string - type: 'null' title: Ptp Rationale title: NCCIValidateClaimTypeResult type: object ValidationError: properties: ctx: title: Context type: object input: title: Input loc: items: anyOf: - type: string - type: integer title: Location type: array msg: title: Message type: string type: title: Error Type type: string required: - loc - msg - type title: ValidationError type: object securitySchemes: APIKeyHeader: in: header name: X-API-Key type: apiKey ````