specification: API Commons Rate Limits
specificationVersion: '0.1'
schema: https://raw.githubusercontent.com/api-evangelist/interface-research/main/schema/api-commons.yml#/$defs/RateLimits
provider: CareFusion (BD)
providerId: carefusion
created: '2026-05-04'
modified: '2026-09-06'
generated: '2026-09-06'
method: searched
source: >-
  https://www.bd.com/en-us/products-and-solutions/products/product-families/bd-alaris-emr-interoperability
  and the 1,382-URL bd.com/en-us sitemap
description: >-
  CareFusion (BD) documents NO rate limits, because it publishes no callable API. There is no
  baseURL, no OpenAPI, no developer portal and no runtime surface on which a limit could be
  signalled — no X-RateLimit-*, no RateLimit-*, no Retry-After, no 429. Alaris and Pyxis
  integrate over HL7 v2 interfaces configured per hospital by BD interface-engineering teams,
  where throughput is an engagement parameter rather than a published quota. limit_count is 0
  and that is the measurement.
  REPLACES a 2026-05-04 bulk-sweep scaffold that asserted 10/100/1,000 requests-per-minute
  tiers, 1,000 and 100,000 monthly quotas, and a full X-RateLimit-*/429 header contract. None
  of it came from BD. See roadmap#35.
limit_count: 0
limits: []
headers: {}
responseCodes: {}
observed: false
evidence:
  - url: https://www.bd.com/en-us/products-and-solutions/products/product-families/bd-alaris-emr-interoperability
    status: 200
    note: The interoperability product page; no limits, no headers, no endpoint.
  - url: https://www.bd.com/en-us/sitemap.xml
    status: 200
    note: No developer, API reference or rate-limit page in the 1,382-URL US sitemap.
  - url: https://api.bd.com/
    status: 502
    note: >-
      The one API-shaped BD hostname that answers at all returns a Microsoft Azure
      Application Gateway 502 — no live endpoint to observe a limit on.
maintainers:
  - FN: Kin Lane
    email: kin@apievangelist.com