How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

2s Medical API

The medical API from 2s — 14 operation(s) for medical.

2s Medical API is one of 114 APIs that 2s publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Medical. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

This API exposes 14 operations across 14 paths, and defines 3 schemas. It is described by OpenAPI 3.2.0, at version 1.

Requests are made against a single base URL, https://2s.io.

14 operations 14 paths 3 schemas 14 GET

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1
Base URL
https://2s.io/mcp
Authentication
API Key
Contact
Resource Areas
1

Authentication & Security 1

2s Medical API declares 1 security scheme for authenticating requests. An API key is passed in the header as PAYMENT-SIGNATURE (x402Payment).

  • x402Payment — x402 protocol v2: base64-encoded PaymentPayload. Call any paid endpoint without auth to receive a 402 with a multi-network PaymentRequirements envelope. Sign f…

Paths & Operations 14

Across 14 paths, the API surfaces 14 operations — 14 GET. Each is listed below with its method, path, parameters, and response codes.

medical 14
GET
/api/medical/device-510k
FDA 510(k) premarket clearances - the record of medical
medical_device-510k 5 params → 200400402405500502
GET
/api/medical/device-classification
FDA medical device classification - the regulatory class
medical_device-classification 4 params → 200400402405500502
GET
/api/medical/device-recall
FDA medical-device recalls - the enforcement record of
medical_device-recall 7 params → 200400402405500502
GET
/api/medical/device-udi
FDA GUDID (Global Unique Device Identification Database)
medical_device-udi 5 params → 200400402405500502
GET
/api/medical/drug-approval
FDA drug approval history from Drugs@FDA - the official
medical_drug-approval 5 params → 200400402405500502
GET
/api/medical/drug-label
Authoritative FDA drug label (Structured Product Labeling)
medical_drug-label 6 params → 200400402405500502
GET
/api/medical/drug-price
Look up US drug pricing from CMS NADAC (National Average
medical_drug-price 4 params → 200400402405500502
GET
/api/medical/drug-status
One-call drug situational awareness
medical_drug-status 5 params → 200400402405500502
GET
/api/medical/genetics
MedlinePlus Genetics (US National Library of Medicine)
medical_genetics 2 params → 200400402405500502
GET
/api/medical/icd10
Verify and search ICD-10-CM diagnosis codes against the
medical_icd10 5 params → 200400402405500502
GET
/api/medical/npi
Look up US healthcare providers in the CMS NPPES registry
medical_npi 8 params → 200400402405500502
GET
/api/medical/provider-id-resolve
Resolve a 10-digit NPI to the provider identity plus a
medical_provider-id-resolve 2 params → 200400402405500502
GET
/api/medical/rxnorm
Normalize and verify drug names against RxNorm, the
medical_rxnorm 4 params → 200400402405500502
GET
/api/medical/taxonomy-specialty
Resolve a NUCC Health Care Provider Taxonomy code -- the
medical_taxonomy-specialty 2 params → 200400402405500502

Schemas 3

The contract defines 3 schemas that model the data the API accepts and returns. The most detailed are X402PaymentRequiredV2 (5 properties), Source (3 properties). Each schema is shown below with its type and property counts.

X402PaymentRequiredV2
object
x402 v2 PaymentRequired envelope. Pick any entry from accepts[], sign for that rail, retry with the PAYMENT-SIGNATURE header.
5 properties 2 required
Source
object
Provenance of the data: upstream provider, source URL, and license.
3 properties
CallMeta
object
Per-call meta envelope — endpoint id, cost, caller kind, settlement details.

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

2s-io-medical-api-openapi.yml Raw ↑

Other APIs 2s publishes across the network.

2s MCP Server
2s A2A Agent
2s Agent API
2s Agriculture API
2s AI API
2s Airport API
2s Aviation API
2s Bank API
2s Barcode API
2s Batch API
2s Bio API
2s Bls API
Where this information came from

This is an independent, third-party profile of 2s Medical API, 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.