Features
A summary of what an API can do — the consumer-facing capability list that bridges marketing claims and reference documentation. Features pages are how prospective consumers evaluate fit before they read the reference, and how internal teams confirm parity with competitors. A clear features pointer lets discovery tools surface capability summaries without crawling the entire docs site.
Also known as: Capabilities, Platform Features, Feature List, Product Features, What You Can Do
Example
Standards
- Schema.org schema.org Product
- Schema.org schema.org Service
- Schema.org schema.org PropertyValue
OpenAPI Expression
-
info.description(OpenAPI 3.x) — Frequently restates the top-level feature summary at the head of the spec. -
tags(OpenAPI 3.x) — Operation tags often map 1:1 to the feature areas advertised externally.
Risk & Compliance
Security: Features pages occasionally enumerate capabilities (admin actions, data exports, write operations) that the reference docs gate behind elevated scopes — making them an accidental scope-discovery surface for attackers. Keep the features list aligned with what is actually authorized at the default tier.
Suggested Metrics
features_to_signup_conversion— Share of features-page visits that convert to a signup or contact-sales event.features_parity_with_reference— Count of advertised features not yet covered by an operation in the OpenAPI description.features_freshness_days— Days since each feature entry was last reviewed against actual product behavior.
Example Implementations
- Stripe — Per-product features pages broken down by payment method and capability.
- Twilio — Channel-by-channel features grid for the Messaging API.
- GitHub — Platform-level features index linking into per-feature deep dives.
Related Properties
Tags
- Discovery
- Capabilities
- Marketing