AmerisourceBergen
AmerisourceBergen (now Cencora) fosters a positive impact on healthcare around the world by advancing the development and delivery of pharmaceuticals and healthcare products. The company provides pharmaceutical distribution, manufacturer solutions, provider solutions, and animal health solutions across 50+ countries through 1,300+ facilities.
Limited machine-readable signal and partial portal coverage — documentation a human can read, but little a machine or agent can consume without scraping.
API Evangelist profiles AmerisourceBergen the way a machine reads it — 26 machine-readable artifacts across 2 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — AmerisourceBergen scores 28.4/100 (thin), with a separate agent-readiness read of 12/100 (agent aware). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Why this profile is thin
Cencora runs a real SAP API Business Hub Enterprise developer portal at api.cencora.com, but every path on that host — including /openapi.json, /.well-known/* and a control path that cannot exist — returns the same 858-byte HTML shim redirecting to SAP XSUAA OAuth (client_id sb-dev-portal-xsuaa!b33), so no catalogue, reference or contract is readable without portal credentials Cencora publishes no way to request.
An API exists — we simply could not reach the contract without credentials or a sales conversation. This one is AmerisourceBergen's to change: publishing the reference and a machine-readable spec at a public URL, while keeping key issuance behind whatever gate they like, would let an integrator evaluate the API before committing to a call.
What we probed
https://api.cencora.com/→ HTTP 200https://api.cencora.com/openapi.json→ HTTP 200https://developer.cencora.com/→ HTTP 403https://www.cencora.com/llms.txt→ HTTP 200
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance. Every facet and dimension name is a link: it opens that measurement's page on APIs.io, where the rating runs across the whole catalog — the exact checks that feed it, how every profiled provider distributes on it, and who is at the top of it.
Put this on your own site. The badge is drawn live from AmerisourceBergen's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/amerisourcebergen/"
title="AmerisourceBergen on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/amerisourcebergen.svg"
alt="AmerisourceBergen Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>
[](https://providers.apievangelist.com/providers/amerisourcebergen/)
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/amerisourcebergen/"
title="AmerisourceBergen on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/amerisourcebergen/card.svg"
alt="AmerisourceBergen Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>
More shapes, themes and sizes → · Score as JSON · How badges work
How we profile AmerisourceBergen
Each block below is one kind of artifact we hold for AmerisourceBergen. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 2
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
AmerisourceBergen Website
AmerisourceBergen (now Cencora) is one of the largest global pharmaceutical distributors, serving pharmaceutical manufacturers, healthcare providers, and patients worldwide. The...
Cencora API Developer Portal
Cencora operates an SAP API Business Hub Enterprise developer portal at api.cencora.com — DNS resolves to ab-cloud-foundry-prd.apibhubenterprise.cfapps.us21.hana.ondemand.com, a...
Pricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the things the Kin Score reads for access clarity — renamed from commercial clarity in rubric 0.12, because a free statutory interface has access terms and no commercial ones.
Published pricing tiers and plan structures.
Rate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Amerisourcebergen Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Amerisourcebergen Finops
FINOPSFeatures 8
The notable capabilities this provider advertises, captured as structured features so they can be searched and compared instead of read one landing page at a time.
Notable capabilities this provider offers.
Pharmaceutical Distribution
U.S. and global distribution network supplying pharmaceutical products from manufacturers to healthcare providers including pharmacies, hospitals, and physician practices.
Manufacturer Solutions
End-to-end support for pharmaceutical manufacturers from drug research and clinical development through commercialization, patient access, and specialty logistics.
Provider Solutions
Solutions for healthcare providers including pharmacies, hospitals, health systems, long-term care facilities, and specialty physician practices to optimize operations and patie...
Animal Health Solutions
Distribution and solutions for veterinary and livestock pharmaceutical products through the MWI Animal Health business.
Patient Access and Adherence
Programs addressing barriers to medication access and improving speed-to-therapy through pharmaceutical patient support services.
Specialty Logistics and Warehousing
Global distribution with specialized packaging, temperature-controlled storage, and customs expertise for specialty and rare disease therapies.
Cell and Gene Therapy Access
Commercialization capabilities connecting manufacturers to health systems and patients for advanced cell and gene therapy products.
Biosimilar Support
Education and support programs for accessing and building confidence in biosimilar therapies across the healthcare ecosystem.
Scroll within the panel for all 8 ·
Security Posture 3
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Scopes 1
OAuth scopes are the vocabulary of least-privilege access. Profiling them shows exactly what an integration — or an agent acting on a user's behalf — is allowed to do.
OAuth scopes governing access to this provider's APIs.
Use Cases 6
What developers actually build with this provider — captured so the catalogue answers 'what is this for', not just 'what does this expose'.
What developers build with this provider.
Drug Commercialization
Support pharmaceutical manufacturers in launching new drugs to market with distribution, patient support, and market access services.
Pharmacy Operations
Enable independent, retail, and specialty pharmacies to efficiently source products and optimize business performance.
Hospital and Health System Supply
Supply hospitals and health systems with pharmaceutical products, specialty drugs, and biosimilars reliably and efficiently.
Rare Disease and Orphan Drug Distribution
Specialized distribution and patient support programs for rare and orphan disease therapies requiring complex handling.
Global Pharmaceutical Logistics
Manage international pharmaceutical supply chains with local presence in 50+ countries and expertise in regulatory compliance.
Clinical Trial Supply
Streamline drug development processes and minimize risk by providing clinical trial supply chain and distribution support.
Integrations 3
Pre-built integrations with other platforms tell you where this provider already fits in a stack.
Pre-built integrations with other platforms and tools.
Good Neighbor Pharmacy Network
Independent pharmacy network providing purchasing programs, business solutions, and marketing support to community pharmacies.
MWI Animal Health
Animal health distribution subsidiary providing veterinary products and solutions to veterinary practices and livestock operations.
Xcenda
Consulting and market access affiliate providing healthcare analytics, reimbursement support, and market access strategies for manufacturers.
Resources
Every other property we hold for AmerisourceBergen — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 1
Portal, sign-up, and the first successful call
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 1
Pagination, idempotency, versioning, errors, and events
Access & Security 5
Authentication, authorization, and security posture
Operate 1
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/amerisourcebergen · machine-readable index on apis.io
This is an independent, third-party profile of AmerisourceBergen, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.