API Terms

1. Acceptance and Incorporation

By signing up for or using the ProcedureRadar B2B API, you agree to these API Terms in addition to the Terms of Service at procedureradar.com/terms, which are incorporated by reference. In the event of conflict, these API Terms control with respect to API use; the Terms of Service control otherwise.

What you're agreeing to is straightforward: access to underwriting-grade procedure pricing data at the tier you've subscribed to, with the severity and confidence-interval fields populated where a cohort has enough reporting hospitals to support them, governed by the rules in both documents. The Terms of Service covers the full legal framework; this document covers the specifics of the API relationship. Read both before you start building.

2. Tier Entitlements

Your subscription tier determines which data surfaces you can access. Starter ($799) includes severity distributions for shoppable procedures in the top 25 metros, with 30-day rounding applied to new accounts during onboarding. Growth ($2,499) adds confidence intervals and expands coverage to the top 100 metros. Scale ($4,999) adds time-series normalization, bulk export, and CPT code input once our AMA license is active. Enterprise ($7,499) adds covered-event mapping, frequency modeling, IP whitelisting, and real-time webhooks. Custom ($15K+) adds TiC payer-negotiated rates and white-label options.

A tier entitlement means the field is unlocked for your account, not that every row carries it. Derived fields (severity distributions, confidence intervals, and the other modeled outputs) are populated only where a procedure-and-metro cohort has enough reporting hospitals to support a statistically valid estimate, and are returned as null otherwise. Each row carries a confidence signal and a reporting-hospital count so you can see when a distribution is backed. Coverage of these fields is densest in the top metros and for high-volume shoppable procedures and continues to expand as we ingest more hospitals. See the methodology white-paper for the sample-size thresholds and known limitations.

Per-tier rate limits, endpoint scope, and full feature details are the canonical references at /developers/docs and /pricing. Those pages govern in the event of any inconsistency with this document.

3. Source-Data Attribution

If you surface ProcedureRadar data on any user-facing interface, you must display "Powered by ProcedureRadar" or an equivalent attribution with a link back to procedureradar.com. This applies to patient-facing tools, plan comparison surfaces, and any other interface your end users interact with.

Internal tools and underwriting workflows are exempt. If the data never leaves your internal systems, the attribution requirement does not apply. This is consistent with the Competing Product carve-out in Terms of Service section 5.

4. Key Confidentiality

Your API key is a bearer token. Whoever holds it has full access to your subscription. Treat it like a password: don't commit it to source control, don't share it across teams without access controls, and don't expose it in client-side code. If your key is compromised, every request made under it is your responsibility until the key is rotated.

Key rotation is available on request at [email protected]. Self-service rotation is not yet available. Attempts to circumvent per-key rate limits by distributing traffic across multiple keys or accounts constitute a material breach per Terms of Service section 6C.

5. Term and Termination

Subscriptions are month-to-month. Either party may terminate for convenience with 30 days' written notice. We may terminate immediately for material breach, including violations of Terms of Service sections 5, 6A, 6B, or 6C.

On termination for any reason, you must stop using the API and delete all cached derived underwriting fields (severity distributions, confidence intervals, time-series normalization values, covered-event mappings, frequency modeling outputs) within 24 hours, as required by Terms of Service section 6A. Raw pricing rows in your cache may be retained until your next scheduled refresh cycle, then must be deleted. No refunds are issued for the remainder of the billing period after termination.

6. Payment and Invoicing

Billing runs monthly via Stripe. There are no refunds for partial months. Tier changes are prorated: downgrades take effect at the next billing cycle, and upgrades can go into effect immediately with a prorated charge for the remainder of the current cycle.

If a payment fails, we'll retry automatically and give you a 7-day grace period before suspending API access. Suspension is not termination: your account stays active and access resumes as soon as payment clears. If you need to update your payment method or get an invoice for procurement, contact [email protected].

7. Service Level

We target 99.5% monthly uptime on a best-effort basis. There are no SLA credits in v1 of the API. We'll notify you by email at least 48 hours before any scheduled maintenance window that affects API availability.

Live status and incident history will be posted at procedureradar.com/status. That page is planned and will go live before the first paid API customer activates. If you experience an outage, reach us at [email protected].

8. Cross-References

Terms of Service sections 6A (caching), 6B (model training restrictions), 6C (rate limits as contract terms), and 11 (liquidated damages and injunctive relief) apply in full to API subscribers and are not restated here. Read them before you build.