IEEE Xplore
IEEE Xplore is the authoritative technical library operated by the Institute of Electrical and Electronics Engineers (IEEE), providing access to over 6 million documents spanning engineering, computer science, electronics, and technology. The IEEE Xplore API suite exposes a REST-based Metadata Search API for querying and retrieving abstracts and metadata across the full corpus, a DOI API for resolving up to 25 DOIs per request, an Open Access API for full-text retrieval of freely available articles, and a Full-Text Access API for institutional subscribers. API access requires key-based registration through the IEEE Developer Portal.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles IEEE Xplore the way a machine reads it — 37 machine-readable artifacts across 5 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 — IEEE Xplore scores 47.0/100 (developing), with a separate agent-readiness read of 48/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
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.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile IEEE Xplore
Each block below is one kind of artifact we hold for IEEE Xplore. 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 5
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.
IEEE Xplore Metadata Search API
REST endpoint for querying and retrieving metadata records and abstracts for more than 6 million documents in IEEE Xplore, including journals, conference proceedings, standards,...
IEEE Xplore DOI API
Batch metadata lookup endpoint that accepts up to 25 DOI (Digital Object Identifier) numbers per request and returns metadata records including abstracts for each resolved docum...
IEEE Xplore Open Access API
Full-text retrieval endpoint for articles designated as IEEE Open Access or chargeable open content. Returns complete article text for documents that are freely available under ...
IEEE Xplore Full-Text Access API
Full-text retrieval endpoint for chargeable IEEE articles accessible to institutional subscribers. Returns complete article content for documents covered under an organization's...
IEEE Xplore Metadata Search API
Query and retrieve metadata records and abstracts for IEEE documents
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 six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Ieee Plans Pricing
PLANSRate 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.
Ieee 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.
Ieee Finops
FINOPSFeatures 10
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.
Metadata Search
Query and retrieve metadata and abstracts for 6M+ IEEE documents including journals, conferences, standards, and books.
Boolean Search
Full AND, OR, NOT Boolean operator support with fielded search across title, author, abstract, affiliation, and more.
DOI Batch Lookup
Resolve up to 25 DOIs per request to retrieve metadata and abstracts in a single call.
Open Access Full Text
Retrieve full article text for openly licensed IEEE publications without institutional subscription.
Institutional Full Text
Full article retrieval for subscribing institutions via auth-token-gated full-text API.
JSON and XML Responses
Default JSON responses with optional XML output format for all API endpoints.
Pagination
Navigate large result sets using start_record parameter with up to 200 results per request.
Content Filtering
Filter results by content_type (Journals, Conferences, Standards, Books, Courses), date range, and other facets.
Dynamic Query Tool
Interactive web-based query builder at developer.ieee.org/io-docs for API exploration with pre-loaded credentials.
Multi-Language SDKs
Official SDKs available in Python 3 and Java for rapid integration.
Scroll within the panel for all 10 ·
Semantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Ieee Xplore Api Context
JSON-LDExamples 3
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
Security Posture 2
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.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Use Cases 7
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.
Academic Research Discovery
Build search interfaces and recommendation engines over IEEE's 6M+ technical documents.
Citation Management
Enrich reference lists and bibliographic databases with IEEE metadata via DOI batch lookup.
Institutional Repository Integration
Sync IEEE metadata into library catalogs, institutional repositories, and research management systems.
Standards Compliance Tooling
Query and surface relevant IEEE standards for compliance documentation and engineering workflows.
AI and RAG Applications
Build retrieval-augmented generation pipelines over IEEE abstracts and metadata for domain-specific AI assistants.
Publication Analytics
Aggregate metadata to analyze publication trends, author networks, and citation patterns across IEEE disciplines.
Content Licensing Platforms
Integrate full-text access APIs into reading platforms for institutional subscribers.
Scroll within the panel for all 7 ·
Integrations 5
Pre-built integrations with other platforms tell you where this provider already fits in a stack.
Pre-built integrations with other platforms and tools.
DOI Foundation / CrossRef
IEEE articles carry DOIs resolvable via the CrossRef and doi.org infrastructure.
Scopus and Web of Science
IEEE Xplore metadata is indexed by major abstract and citation databases.
Semantic Scholar
IEEE publications surfaced via Semantic Scholar's open research graph.
ORCID
Author identifiers linked to IEEE contributor profiles.
RIS / BibTeX Export
IEEE Xplore supports standard citation export formats compatible with reference managers.
Resources
Every other property we hold for IEEE Xplore — 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 2
Portal, sign-up, and the first successful call
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Build 2
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Operate 2
Status, limits, changes, and where to get help
Commercial 4
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/ieee · machine-readable index on apis.io