Schema.org
Schema.org is a collaborative, community-driven project that creates and maintains a shared vocabulary for structured data on the web. Founded by Google, Microsoft, Yahoo, and Yandex in 2011, it provides types and properties that developers and webmasters use to annotate content in formats like JSON-LD, RDFa, and Microdata, enabling search engines and applications to better understand web content. The vocabulary currently consists of 800+ Types, 1500+ Properties, and covers domains including commerce, healthcare, organizations, events, creative works, and more. The Schema.org WebAPI type provides a standardized vocabulary for describing APIs in structured data.
Limited machine-readable signal and partial portal coverage — documentation a human can read, but little a machine or agent can consume without scraping.
API Evangelist profiles Schema.org the way a machine reads it — 93 machine-readable artifacts across 4 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 — Schema.org scores 40.7/100 (thin), with a separate agent-readiness read of 7/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.
How we profile Schema.org
Each block below is one kind of artifact we hold for Schema.org. 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 4
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.
Schema.org Vocabulary
Schema.org is a collaborative, community-driven vocabulary for structured data on the internet. It provides a collection of shared vocabularies that webmasters and developers ca...
Schema.org JSON-LD Context
The Schema.org JSON-LD Context provides the canonical JSON-LD context file for the Schema.org vocabulary. This context file maps Schema.org terms to their full IRIs, enabling JS...
Schema.org Markup Validator
The Schema.org Markup Validator tests and validates structured data markup against the Schema.org vocabulary. It supports JSON-LD, Microdata, and RDFa formats and helps ensure s...
Schema.org WebAPI Type
The Schema.org WebAPI type defines a Web API accessible over Web and Internet technologies. It provides standardized properties for describing APIs including documentation URL, ...
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.
Rate 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.
Schema Org 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.
Schema Org Finops
FINOPSSemantic 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.
Schema Org Context
JSON-LDSpectral Rules 2
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.
Schema.org API Rules
SPECTRALSchema.org API Rules
SPECTRALJSON Schema 40
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.
Schema.org Action
JSON SCHEMASchema.org AggregateRating
JSON SCHEMASchema.org Article
JSON SCHEMASchema.org BlogPosting
JSON SCHEMASchema.org Book
JSON SCHEMASchema.org BreadcrumbList
JSON SCHEMASchema.org ContactPoint
JSON SCHEMASchema.org Course
JSON SCHEMASchema.org CreativeWork
JSON SCHEMASchema.org Drug
JSON SCHEMASchema.org Event
JSON SCHEMASchema.org FAQPage
JSON SCHEMASchema.org GeoCoordinates
JSON SCHEMASchema.org HowTo
JSON SCHEMASchema.org ImageObject
JSON SCHEMASchema.org Invoice
JSON SCHEMASchema.org ItemList
JSON SCHEMASchema.org JobPosting
JSON SCHEMASchema.org LocalBusiness
JSON SCHEMASchema.org MediaObject
JSON SCHEMASchema.org MedicalCondition
JSON SCHEMASchema.org MedicalProcedure
JSON SCHEMASchema.org Offer
JSON SCHEMASchema.org Order
JSON SCHEMASchema.org Organization
JSON SCHEMASchema.org Person
JSON SCHEMASchema.org Place
JSON SCHEMASchema.org PostalAddress
JSON SCHEMASchema.org Product
JSON SCHEMASchema.org PropertyValue
JSON SCHEMASchema.org QuantitativeValue
JSON SCHEMASchema.org Review
JSON SCHEMASchema.org SearchAction
JSON SCHEMASchema.org Service
JSON SCHEMASchema.org SoftwareApplication
JSON SCHEMASchema.org Thing
JSON SCHEMASchema.org VideoObject
JSON SCHEMASchema.org WebAPI
JSON SCHEMASchema.org WebPage
JSON SCHEMASchema.org WebSite
JSON SCHEMAScroll within the panel for all 40 ·
JSON Structure 40
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.
Schema Org Action
JSON STRUCTURESchema Org Aggregate Rating
JSON STRUCTURESchema Org Article
JSON STRUCTURESchema Org Blog Posting
JSON STRUCTURESchema Org Book
JSON STRUCTURESchema Org Breadcrumb List
JSON STRUCTURESchema Org Contact Point
JSON STRUCTURESchema Org Course
JSON STRUCTURESchema Org Creative Work
JSON STRUCTURESchema Org Drug
JSON STRUCTURESchema Org Event
JSON STRUCTURESchema Org Faq Page
JSON STRUCTURESchema Org Geo Coordinates
JSON STRUCTURESchema Org How To
JSON STRUCTURESchema Org Image Object
JSON STRUCTURESchema Org Invoice
JSON STRUCTURESchema Org Item List
JSON STRUCTURESchema Org Job Posting
JSON STRUCTURESchema Org Local Business
JSON STRUCTURESchema Org Media Object
JSON STRUCTURESchema Org Medical Condition
JSON STRUCTURESchema Org Medical Procedure
JSON STRUCTURESchema Org Offer
JSON STRUCTURESchema Org Order
JSON STRUCTURESchema Org Organization
JSON STRUCTURESchema Org Person
JSON STRUCTURESchema Org Place
JSON STRUCTURESchema Org Postal Address
JSON STRUCTURESchema Org Product
JSON STRUCTURESchema Org Property Value
JSON STRUCTURESchema Org Quantitative Value
JSON STRUCTURESchema Org Review
JSON STRUCTURESchema Org Search Action
JSON STRUCTURESchema Org Service
JSON STRUCTURESchema Org Software Application
JSON STRUCTURESchema Org Thing
JSON STRUCTURESchema Org Video Object
JSON STRUCTURESchema Org Web Api
JSON STRUCTURESchema Org Web Page
JSON STRUCTURESchema Org Web Site
JSON STRUCTUREScroll within the panel for all 40 ·
Examples 2
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.
Schema Org Product Example
EXAMPLESchema Org Web Api Example
EXAMPLESecurity 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.
Resources
Every other property we hold for Schema.org — 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 1
Reference material describing how the API behaves
Design & Contract 3
Pagination, idempotency, versioning, errors, and events
Access & Security 1
Authentication, authorization, and security posture
Operate 1
Status, limits, changes, and where to get help
Company 2
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/schema-org · machine-readable index on apis.io