---
layout: service
section: Services
title: Standards
summary: Identify and develop the standards required to ensure the interoperability of any aspect of business operations.
nav: Services
sub: Discovery
---

<div class="row gx-xl-9">
  <div class="col-12">
    <section>

      <!-- Breadcrumb -->
      <p class="small text-muted mb-2"><a href="/services/" class="text-decoration-none">&larr; All Services</a> &middot; <a href="/services/discovery/" class="text-decoration-none">Discovery</a></p>

      <!-- Header -->
      <div class="d-flex align-items-center mb-3">
        <img src="/images/services/standards.png" alt="" width="64" height="64" class="me-3 flex-shrink-0">
        <h1 class="fs-3 mb-0">{{ page.title }}</h1>
      </div>
      <p class="lead text-muted mb-4">{{ page.summary }}</p>

      <!-- Story -->
      <div class="mb-2" style="max-width: 46rem;">
        <p class="mb-3">I have watched more interoperability die from a lack of boring agreements than from any hard technical problem. Two teams, two formats, two ways of saying the same date &mdash; and suddenly integration is a project instead of a given. Standards are the boring agreements that make the interesting work possible.</p>
        <p class="mb-3">I help you identify which standards actually apply to your operations &mdash; OpenAPI, AsyncAPI, JSON Schema, Arazzo, and the domain-specific ones your industry already leans on &mdash; and where you may need to establish your own. Then I help you adopt them in a way that sticks, so they show up in your interfaces and your pipelines rather than living in a slide deck.</p>
        <p class="mb-3">Standards are how you buy interoperability once instead of renegotiating it on every project. I have been tracking the API standards landscape since before most of these specifications had version numbers, and I bring that history to bear on what is worth your attention and what is noise.</p>

        <h2 class="fs-6 fw-semibold mt-4 mb-2">What you walk away with</h2>
        <ul class="text-muted">
          <li>A shortlist of the standards that matter for your specific operations</li>
          <li>A plan for adopting them consistently across teams and interfaces</li>
          <li>Interoperability treated as a default, not a per-project negotiation</li>
        </ul>
      </div>

      <!-- Related reading -->
      <div class="mb-4" style="max-width: 46rem;">
        <h2 class="fs-6 fw-semibold mb-2">Related reading</h2>
        <ul class="text-muted mb-0">
          <li><a href="/2026/02/25/the-promise-of-a-new-specification/">The Promise of a New Specification</a></li>
          <li><a href="/2025/01/14/what-is-openapi/">What is OpenAPI?</a></li>
        </ul>
      </div>

      <!-- CTA -->
      <div class="card border-0 shadow-sm mt-4" style="max-width: 46rem;">
        <div class="card-body">
          <h2 class="fs-5 mb-2">Let's work together</h2>
          <p class="text-muted mb-3">If you are tired of renegotiating interoperability on every project, standards are how you stop. Let's talk.</p>
          <p class="mb-0"><a href="mailto:info@apievangelist.com?subject=Standards%20services" class="btn btn-outline-secondary btn-sm">Get in touch — info@apievangelist.com</a></p>
        </div>
      </div>

    </section>
  </div>
</div>