Health · head-to-head

CMS.gov vs Makeup

CMS.gov

CMS Provider Data Catalog exposes hundreds of Medicare quality, cost, and comparison datasets (hospitals, nursing homes, dialysis facilities, and more) through a DKAN-based metastore and datastore API that returns JSON by default and CSV on request, with no signup required. A live GET against the dataset-listing and datastore query endpoints succeeds with no credentials. A live Origin-header probe against the datastore query endpoint returns no Access-Control-Allow-Origin header on either a GET or an OPTIONS preflight, and since access needed no key at all, the stored 'API Key' auth was corrected to 'None'.

Makeup

Makeup API is a free, keyless single-endpoint REST service serving a static catalogue of cosmetics products — lipsticks, foundations, eyeshadows, and more — searchable by brand, product type, category, tag, price, and rating, with per-product image and retailer links. Still live on Heroku with no auth, no published rate limit, and no formal SLA; it's a hobby open-data project rather than a maintained commercial API. A live GET against makeup-api.herokuapp.com/api/v1/products.json succeeds over both http and https with no key, and returns Access-Control-Allow-Origin: * — resolving the stored 'unknown' cors to 'yes' and the stored 'https: false' to 'true'.

CMS.govMakeup
AuthenticationNoneNone
Pricingfreefree
FormatsJSON, CSVJSON
CORSnoyes
HTTPSYesYes

Makeup supports CORS, while CMS.gov doesn't — pick Makeup for direct browser calls.

More comparisons