WSDL
WSDL (Web Services Description Language) is a W3C standard XML format for describing web service interfaces. It defines services as collections of network endpoints (ports) that exchange messages, specifying the abstract operations, message formats, and protocol bindings needed to interact with a web service. WSDL 2.0 became a W3C Recommendation on June 26, 2007, and adds support for all HTTP request methods, making it more suitable for RESTful web services than its predecessor WSDL 1.1.
More than an index entry, but the surface is still mostly links rather than artifacts — the cohort most likely to move a full band from modest, well-targeted work.
API Evangelist profiles WSDL the way a machine reads it — 41 machine-readable artifacts, 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 — WSDL scores 25.7/100 (emerging), with a separate agent-readiness read of 0/100 (human only). 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 WSDL
Each block below is one kind of artifact we hold for WSDL. 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.
Features 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.
Abstract Service Interface
Defines abstract interfaces separating service contract from protocol binding.
Message Exchange Patterns
Supports In-Only, Robust In-Only, and In-Out message exchange patterns.
SOAP Binding
Native SOAP 1.2 binding for web service interoperability.
HTTP Binding
HTTP binding supporting all HTTP methods including GET, POST, PUT, DELETE.
RPC Style Operations
RPC-style operation dispatch with input and output message wrappers.
Type System Integration
Integrates with XML Schema for defining message types.
Multiple Endpoints
Supports multiple endpoints per service with different protocol bindings.
Namespace and Modularity
Uses XML namespaces to enable modular and reusable service descriptions.
Operation Safety Declaration
Allows marking safe read-only operations per web architecture principles.
RDF Mapping
Normative mapping to RDF for linked data and semantic web 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.
Wsdl Context
JSON-LDSpectral Rules 1
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
WSDL API Rules
SPECTRALJSON Schema 8
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
WSDL Binding
JSON SCHEMAWSDL Description
JSON SCHEMAWSDL Endpoint
JSON SCHEMAWSDL Interface Fault
JSON SCHEMAWSDL Interface
JSON SCHEMAWSDL Operation
JSON SCHEMAWSDL Service
JSON SCHEMAWSDL Types
JSON SCHEMAScroll within the panel for all 8 ·
JSON Structure 8
JSON Structure captures the data shapes in a form built for tooling — a complement to JSON Schema that keeps the model machine-legible.
JSON Structure definitions describing this provider's data shapes.
Wsdl Binding Structure
JSON STRUCTUREWsdl Description Structure
JSON STRUCTUREWsdl Endpoint Structure
JSON STRUCTUREWsdl Interface Fault Structure
JSON STRUCTUREWsdl Interface Structure
JSON STRUCTUREWsdl Operation Structure
JSON STRUCTUREWsdl Service Structure
JSON STRUCTUREWsdl Types Structure
JSON STRUCTUREScroll within the panel for all 8 ·
Security Posture 1
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.
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.
SOAP Web Service Description
Describing enterprise SOAP web services for automated client generation.
Service Contract Definition
Defining service contracts between service providers and consumers.
Code Generation
Generating client proxy code and server stubs from WSDL documents.
Service Discovery
Enabling automated discovery and invocation of web services.
Interoperability Testing
Validating interoperability between different SOAP implementations.
REST Service Description
Describing RESTful services using WSDL 2.0 HTTP binding support.
Integrations 6
Pre-built integrations with other platforms tell you where this provider already fits in a stack.
Pre-built integrations with other platforms and tools.
XML Schema
WSDL 2.0 uses XML Schema for type definitions.
SOAP 1.2
Native SOAP 1.2 binding defined in WSDL 2.0 Part 2.
HTTP 1.1
HTTP binding supporting REST-style services.
UDDI
WSDL documents are referenced in UDDI service registries.
WS-Policy
Web services policy framework that annotates WSDL descriptions.
WS-Addressing
Endpoint reference standards used with WSDL service endpoints.
Resources
Every other property we hold for WSDL — 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.
Documentation 13
Reference material describing how the API behaves
Scroll within the panel for all 13 ·
Design & Contract 10
Pagination, idempotency, versioning, errors, and events
Scroll within the panel for all 10 ·
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 1
Authentication, authorization, and security posture
Operate 1
Status, limits, changes, and where to get help
Company 1
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/wsdl · machine-readable index on apis.io